Privacy policy
How Sentry AIOS handles your data, including data from Google. Last updated 12 November 2026.
Who this covers
This policy applies to Sentry AIOS, the private application at os.sentrysolutions.ai, operated by Sentry AI Solutions Limited (NZBN 9429053388131), Auckland, New Zealand. It is separate from the privacy policy covering our public website and our client work. Users of this application are members of our own team and named people at the organisations we set up on it.
What we collect
- Account details. Your name, email address and role, created by us when your account is set up.
- Data you connect. Content from third-party accounts you choose to connect, including Google, described below.
- Operational records. What the application did and when, so actions can be audited and errors diagnosed.
Google user data
Connecting a Google account is always initiated by you. We request only the scopes listed below, and we use the data they return solely to provide features inside this application.
| Scope | Why we request it |
|---|---|
| userinfo.email | Identify which account you connected. |
| userinfo.profile | Show your name and avatar in the app. |
| gmail.readonly | Read your mail so the app can summarise threads, find context for a client, and surface messages needing a reply. |
| gmail.compose | Create draft replies for you to review. Drafts are never sent without a person choosing to send them. |
| gmail.modify | Apply and remove labels, and mark messages read, so triaged mail stays organised. |
| gmail.settings.basic | Read and manage filters used to route inbound mail into the right place. |
| drive | Read documents for context and create or update files the app produces, such as reports and generated documents. |
| calendar | Read your calendar to prepare for meetings and check availability. |
| calendar.events | Create and update events, for example when scheduling a client call. |
| presentations | Build and edit Google Slides decks the app generates from a template. |
| analytics.readonly | Read Google Analytics for websites the company owns, to report on traffic. |
| webmasters.readonly | Read Google Search Console performance data for websites the company owns. |
| adwords | Read campaign and search-term performance for Google Ads accounts the company owns, and apply a limited set of campaign changes (pause or enable a campaign, adjust a daily budget, add negative keywords). Every change is approved by a person before it is sent to Google. |
| business.manage | Read and update the company's own Google Business Profile, including replying to reviews. |
| admin.directory.user | Create, update and suspend users in the company's own Google Workspace during onboarding and offboarding. |
| admin.directory.user.security | Review and revoke a user's active sessions and security settings when offboarding. |
| admin.directory.group | Manage Workspace group membership so access follows the team structure. |
| admin.directory.orgunit | Read the organisational units a user belongs to. |
| admin.directory.domain.readonly | Read the domains attached to the Workspace account. |
| admin.directory.rolemanagement.readonly | Read admin role assignments as part of a security review. |
| admin.reports.audit.readonly | Read Workspace audit logs to produce security and login reports. |
| admin.reports.usage.readonly | Read Workspace usage reports to understand adoption of tools the company pays for. |
Limited Use commitment
Sentry AIOS's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. Specifically:
- Google user data is used only to provide and improve the features described above.
- We do not sell Google user data, and we do not transfer it to third parties except as needed to provide those features, for security, or to comply with the law.
- We do not use Google user data for advertising of any kind.
- We do not use Google user data to train, retrain or improve generalised AI or machine-learning models. Where content is passed to an AI model to carry out a task you asked for, it is processed to produce that result and not retained for model training.
- No human reads your Google user data except you, and our own staff where strictly necessary for security, to resolve a fault, or where we have your consent or the law requires it.
TikTok data
Connecting a TikTok account is always initiated by you, through TikTok's own sign-in, and covers the TikTok account you sign in with. The connection is held here and used by this application and by our content calendar at content.sentrysolutions.ai, where our team plans and posts content. We request only the scopes below.
| Scope | Why we request it |
|---|---|
| user.info.basic | Show which TikTok account is connected: its display name and avatar. |
| user.info.profile | Show the account's username, bio and profile link. |
| user.info.stats | Report the account's follower, like and video counts to our team. |
| video.list | List the account's public videos with their views, likes, comments and shares, to measure each post. |
| video.upload | Send a video or photos to the account's TikTok inbox as a draft, which the creator finishes and posts in the TikTok app. |
| video.publish | Post a video or photos to the account when a person chooses to post them, with the settings they choose. |
- Nothing is posted to TikTok without a person choosing to post it, with the privacy level, interaction settings and content disclosure they select on the post screen.
- We do not sell TikTok data, use it for advertising, or use it to train AI models. It is used only to show the account's profile and results to our team and to publish what they post.
- You can disconnect at any time inside the application, or remove access from the TikTok app under Settings and privacy, Security and permissions, Apps and services permissions. Disconnecting deletes the stored tokens.
How it is stored and secured
- Data is held in a managed PostgreSQL database and on servers we control. Access requires an account we issue.
- Access and refresh tokens for connected accounts are encrypted at rest using AES-256-GCM. They are never displayed in the interface and never written to logs.
- All traffic is served over HTTPS.
- The application is not indexed by search engines and every page other than this one, the about page, the terms and the sign-in page requires authentication.
Retention and deletion
You can disconnect any Google account at any time from the integrations page inside the application, or by revoking access at myaccount.google.com/permissions. Disconnecting deletes the stored tokens immediately and stops all further access. To have data already retrieved deleted as well, email us and we will remove it.
Your rights
We handle personal information in accordance with the New Zealand Privacy Act 2020. You may ask what we hold about you, ask us to correct it, and ask us to delete it. Contact james@sentrysolutions.ai.
Changes
If the scopes this application requests change, this page is updated at the same time. The date at the top reflects the last change.