Last updated: 23 October 2026
This is the privacy policy of LoomShift, the service at loomshift.app. LoomShift is operated by Team MajTom, Dalgränd 6, 12130 Enskededalen, Sweden. Who we are and what we are for is on our About page, https://loomshift.app/about.
When you sign in, we store your GitHub account identity, or your name and email from Google or Microsoft (via Firebase Authentication) if you sign in that way.
When you install the LoomShift GitHub App, we store which repositories your installation grants access to — nothing outside that grant.
When you connect an integration such as Vercel or Jira, we store the OAuth access token and the account or team identifier needed to operate that connection.
This is only what LoomShift's own product needs to run: to know who you are, to open pull requests and read the repositories you've installed it on, and to act on your behalf on services you've explicitly connected. We don't collect anything beyond that.
Everything is stored per organization, isolated from every other organization's data, in our production database and Google Cloud Secret Manager.
Connected-integration tokens never reach your browser, a release package, or a log line.
In transit: everything you send to LoomShift travels over HTTPS, with a certificate that Google Cloud issues and renews for loomshift.app. Our connection to the database goes through Google Cloud's own connector, not over the open internet.
At rest: our database and Google Cloud Secret Manager are Google Cloud services, which encrypt stored data by default.
Credentials: the access tokens and refresh tokens for the services you connect (Vercel, Jira, and your Google account for Firebase) are kept in Google Cloud Secret Manager, not in ordinary database columns. We do not store the short-lived Google access token at all: we ask Google for a new one when we need it. Your GitHub sign-in token lives only in a secure, HttpOnly cookie in your own browser session, and the GitHub App's own key, which we use to act on the repositories you installed it on, is also kept in Secret Manager.
Who can reach them: LoomShift's own running service, through its Google Cloud service account. Our staff cannot read a token through the administration view, and no token is ever sent to your browser (apart from your own GitHub sign-in cookie above), written to a log, or included in a release package.
Your session: the cookie that keeps you signed in is signed so it cannot be altered, cannot be read by scripts on the page (HttpOnly), and is sent only over HTTPS.
Separation: every record is stored against your organization, and every read filters on it, so one organization cannot read another's runs, code, conversations or recordings. Browser-check recordings are stored in a private bucket under your organization's own path and are never served through a public or signed link.
Images you attach in a message to Sarah are deleted once she has analyzed them.
A small number of LoomShift staff (our "operators") can open an administration view of your account.
What they can see: your account and workspace details, such as your name, a masked version of your email address, how you sign in, which plan you are on and how much you have used, and the errors and failures your workspace has run into. An operator can choose to reveal your full email address, for example to reply to you.
Why: to support you, to find and fix failures, and to improve the service. We rely on our legitimate interest in running a reliable service for this, and we limit it to what those purposes need.
What they cannot see: your code, your conversations with the team, your documents, or any access token or credential. The administration view does not contain them.
Every time an operator opens your account in the administration view, and every time one reveals your email address, it is recorded in your workspace's audit trail with who did it and when.
We don't sell your data. We don't share it with third parties beyond the connected services you explicitly authorize. You own all the code and content LoomShift produces for you.
LoomShift's use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
Signing in with Google: we ask for your Google identity only: your account's name, email address and profile information (the openid, userinfo.email and userinfo.profile permissions). We use it to know who you are and to show which account is signed in.
Connecting Firebase: if you choose to connect your Google account so the team can set up and deploy to a Firebase project you own, we ask for your identity (openid, userinfo.email) and the Google Cloud permission cloud-platform. That permission is needed to create and configure Firebase, App Hosting, Firestore, security rules and storage in your own project, and to read what a failed deployment says. We use it only to do what you asked, in your project, when you ask.
What we do with it: we use Google user data only to provide and improve the features you asked for in LoomShift. We do not sell it. We do not use it for advertising, for credit decisions, or to build user profiles. We do not use it to develop, improve or train generalized AI or machine-learning models.
Who sees it: only the running service sees it, to make those requests. Our staff do not read it, except where you ask us for support and then only what you show us, where the law requires it, or to protect the service from abuse. When you ask the team to fix a failed deployment, the error message Google returned for it is given to the AI model that works on your request, only to answer that request.
Removing it: disconnecting Firebase deletes the stored refresh token. You can also remove LoomShift's access at any time in your Google Account's third-party access settings, and write to us to have the rest deleted.
Disconnecting a connected service, or uninstalling the GitHub App, deletes its stored credential. Signing out ends your session without deleting account data used by integrations you keep connected.
Questions about this policy: info@loomshift.app.