Privacy policy

Last updated November 4, 2026

Third Shift ("we") is an AI team that runs parts of a business, from turning a team's plans, tickets and error reports into tested changes to its own code, to running its ads. This policy covers this website (thirdshift.run), the Third Shift console (factory.thirdshift.run), the Third Shift mobile app ("Third Shift: Agent Crew" on the App Store) and the service behind them. Questions go to privacy@thirdshift.run.

The short version

• We collect what we need to sign you in and to run the work your team asks for, and nothing for advertising.
• We don't sell personal data, and we don't use your data to train AI models.
• Your source code is never stored by our control plane: it is checked out only while a job runs.
• Every outside company that handles your data is listed below.
• Delete your account yourself in the app's Settings or the console's Profile, or write to us and we will export or delete your data.

What we collect

On this website. No cookies and no outside scripts. Our host keeps standard request logs (IP address, browser, pages asked for). We count visits and early-access requests with our own counter: a total per day, per page and per site or ad you came from, never anything about you. Your IP address is used only to stop floods, as a one-way hash we delete within a day. If you came from one of our ads, your browser keeps which one until you close the tab. If you email us, or ask for early access with the form, we keep what you sent (your email address, and your name, company and note if you give them) to reply to you, and delete a request 90 days after our conversation about it ends.

Your account. Your name and email address, the workspaces you belong to and your role in each. If you sign in with a password, only a one-way hash of it is stored. If you sign in with Google, Google tells us your name, email address and that you signed in; we ask Google for nothing else. Your browser keeps your sign-in session in its local storage. We record the actions you take in the console (for example approving a change or inviting someone) in an audit log your workspace's admins can see.

The mobile app. The app signs in to the same account and shows your workspace's conversations; it keeps your sign-in session in your phone's keychain. If you turn notifications on, we keep your device's push token to send them, and a notification carries only a title, never the text of a message. Photos and files you attach to a message are kept with that conversation, in your workspace, and are seen only by its members and by the workers in that conversation. The app records which of its screens you use (for example opening a conversation or a notification) to improve it; that record stays in our own database, with no outside analytics service. The app has no advertising, and it does not read your location, contacts or microphone.

Your workspace. What your team connects Third Shift to sends us work to do, and we keep what we need to track it:

• tickets' titles and descriptions, and the text of tickets linked to a plan;
• plans, briefs, specs, questions, answers and comments written in the console or the mobile app;
• the state of each piece of work: its history, the decisions taken on it, links to its pull requests and short summaries of test results;
• summaries of error reports and customer feedback your team chooses to send;
• for your workspace's own apps, whether you allowed each one on the phone and when, and any report you send us about one (your words and your sign-in, so we can answer you). What an app reads and writes stays in your business's own database: it passes through our servers and is not kept by us.

We do not keep your source code, your secrets or the rows of your own databases. When an agent works on your code, it does so in a checkout that exists only while the job runs, either on your own machine or on a short-lived server we run for you.

Your store and your ads. If your workspace turns Marketing on, Third Shift connects to your Shopify store and your Meta ad account, each with your approval.

• From your Shopify store we read paid orders and refunds: each order's id, day, value, currency, landing page and the campaign it came from, its line items' product titles, quantities and prices, and whether it is the customer's first order or a later one. These are added to your daily totals and then dropped. We never read your customers' names, email addresses, phone numbers or addresses.
• We also read your store's active products (title, price and a short description), so your ads describe what you sell.
• We keep your daily totals (orders, refunds and revenue, overall, by campaign and by product), the ids of the orders we have counted so none is counted twice, and a short record of each update Shopify sends us. We never change anything in your store.
• From your Meta ad account we read your campaigns, ads and their daily results, and change them (pausing an ad, changing a budget, creating an ad) only after a person in your workspace approves. We keep your ads' results in aggregate, never records about individual people.

Uninstalling Third Shift's Shopify app ends the connection. When Shopify asks us to delete a customer's data, we remove the order ids and records that name that customer's orders. When it asks us to delete a store's data, we delete everything tied to that store except your daily totals and the short notes about your products, which describe your business, not any person. To have those deleted too, write to privacy@thirdshift.run.

How we use it

• to provide the service: to plan, build, test and report on the work your team asks for;
• to measure and run your ads, when your workspace uses Marketing;
• to sign you in and to send you the emails the service needs (sign-in links, password resets);
• to keep the service secure, to find and fix problems, and to answer you when you write to us.

Text from your tickets, feedback and code is treated as data, never as instructions to our systems.

Who else handles your data

These companies run parts of Third Shift for us and handle your data only to do so:

Third Shift also reads from and writes to the tools your team connects (for example GitHub, Linear, Slack, Shopify and Meta) on your team's behalf, as described above. Those services act under your team's own agreements with them.

We will tell customers before adding a company to this list. We share data otherwise only when the law requires it.

How long we keep it

We keep account and workspace data while your workspace is active. When a workspace is closed, we keep its data for 30 days in case it is reopened, then delete it. When you ask us to delete your data, we do so within 30 days. Either way we keep only what the law requires us to keep. Copies in backups are removed as those backups expire.

Your choices and rights

You can ask us to show you, correct, export or delete the personal data we hold about you by writing to privacy@thirdshift.run. You can also delete your account yourself, at the bottom of the app's Settings or the console's Profile page: your login, name, email, phone number, devices and settings go at once, and what you did in a company's workspace stays as its record, shown as "A former member". If your account belongs to a company's workspace, we may involve that company's admins, since the workspace's data is theirs. You can stop signing in with Google at any time by removing Third Shift's access in your Google account settings. In the mobile app, turn notifications off in the app's Settings or your phone's settings; signing out removes the session from your phone.

Security

Data travels encrypted. Each workspace's data is kept apart by row-level security in the database, agents get only short-lived credentials scoped to the job in hand, and access to production is limited and logged.

Google user data

If you sign in with Google, Third Shift receives only your name, email address and Google account id, and uses them only to sign you in and show who you are in your workspace.

If you connect your Google Calendar, Third Shift asks Google for:

• your busy and free times, to offer your customers times you are free and to keep bookings off times you are busy;
• a calendar of its own in your account ("Booked by Third Shift"), where it adds, moves and removes the jobs your customers book. It cannot change any of your other calendars or events;
• the list of your calendars and, read only, the events on the ones you have selected, so that your assistant can answer your questions about your schedule and your front desk can tell customers when you are busy.

Event details are read when you or your front desk need them and are not stored: not in our database, in logs or in backups. To answer you, the assistant sends the events it needs to the AI model through OpenRouter, as listed above, only for that answer. What it then writes in a reply to you is kept with that conversation for your workspace's retention. Your front desk sees only busy times, never what is in your events.

If you connect your own Google Drive, Third Shift asks Google only for access to the files you pick in Google's own file picker; it cannot see or open anything else in your Drive. Your browser fetches each file you pick (a Google Sheet as an Excel copy) and adds it to your workspace as if you had uploaded it from your computer: a picture or video as an ad for your review, a spreadsheet as a file attached to your message. That copy is kept in your workspace until you remove it, and is read for you as any file you add is, including by the AI model through OpenRouter, as listed above. Picking the file again brings in a new copy; Third Shift does not go back to your Drive for it.

If your business instead shares a Google Drive folder with your workspace's own Third Shift address, Third Shift reads only that folder, with view access, and brings in its pictures and videos as ads for your review. It never changes anything in the folder. Stop sharing the folder in Google Drive to end it.

Third Shift's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. We use Google user data only to provide the features above to you. We do not sell it, use it for advertising, or let people read it except with your permission, for security, or where the law requires. We do not use it to develop, improve or train generalized AI or machine learning models, and the AI model providers we use do not train on it. You can disconnect your calendar or your Google Drive on Third Shift's Connections page or by removing Third Shift's access in your Google account settings. When you disconnect in Third Shift, we revoke its access with Google and delete the stored token.

Children

Third Shift is a tool for businesses and is not meant for anyone under 16.

Changes

We will post any change here with a new date, and tell customers by email before a change that affects how their data is used.