Abby OS
Privacy policy
Last updated 2 November 2026
Who this covers
Abby OS is a private business tool used by one creator, Abby, to run her brand deals, locum work and content. It is not open to the public. Only approved accounts can sign in. Questions go to upskillwithabz@gmail.com.
Google data we use
- Sign-in: your email address, to check you are an approved user.
- Gmail (read): messages in the connected inboxes, to sort them and pull out brand deal and shift details.
- Gmail (send): to send a reply or invoice, only after Abby approves it. Nothing is sent automatically.
- Google Calendar: to add booked shifts and film days to her calendar.
- Google Drive: to save backups in a folder the app creates. It cannot see her other files.
Other information in the app
Abby OS also keeps what Abby adds or generates in it: deals, rates, invoices, shifts, expenses and receipt photos, CPD records, renewal dates, scripts, videos and post statistics. Emails from brands and agencies can include the sender's name and contact details.
Who processes the data
The app relies on these services to work. We do not sell data or use it for advertising.
- Supabase: database and file storage.
- Vercel: hosting.
- Anthropic (Claude API): reads email content and photos to sort them and write drafts.
- Metricool: scheduling posts and fetching their statistics.
- postcodes.io: postcodes, to estimate mileage.
Google API Services
Abby OS's use and transfer of information received from Google APIs follows the Google API Services User Data Policy, including the Limited Use requirements. Google user data is only used to provide the features described above. It is not used for advertising, sold, or used to train general AI models.
Keeping and deleting data
Data stays in the app while Abby uses it. To remove the app's access to a Google account at any time, use Disconnect inbox in Settings or Google account permissions. To have your data deleted, or to ask what is held about you, email upskillwithabz@gmail.com.
Security
Data is sent over HTTPS. The database is not reachable from the browser, and Google access tokens are only used on the server.