Orient← Back to site
Legal

Privacy Policy

Effective date: July 20, 2026
Operator / data controller: Orient AI (“Orient”, “we”, “us”)
Contact: privacy@orient-ai.services

1. What Orient is

Orient is a private, multi-tenant client-operations platform used by our operations team to manage the marketing and analytics connections of the clients we serve. It is an internal business tool, not a consumer product. An authorized operator connects a client's Google data sources (with that client's permission) so their performance data appears, read-only, inside a governed internal dashboard.

2. Google user data we access

When you authorize Orient through Google's OAuth consent screen, you grant these read-only scopes:

  • https://www.googleapis.com/auth/analytics.readonly — to read Google Analytics 4 account and property structure (Analytics Admin API) and to pull aggregate reports and metrics (Analytics Data API): e.g. sessions, active users, key events, traffic sources, and topline reports.
  • https://www.googleapis.com/auth/webmasters.readonly — to read Google Search Console property structure and aggregate search-performance data: clicks, impressions, CTR, and average position by query, page, country, and device.

We request only read-only scopes. We never request write, delete, or management scopes. We do not access Gmail, Drive, Calendar, Contacts, files, or message content, and we do not access individual end-users' personal profiles. The data we read is aggregate/property-level analytics, not personal data about your site's visitors.

3. How we use the data

Google user data is used solelyto render the operator's internal client dashboard — the organization graph, per-client health indicators, and connection “evidence” records (which property is connected, when it was last synced, topline figures). Data is pulled on a manual, operator-initiated sync; the dashboard displays how stale each connection is (“synced N hours ago”) so nothing is silently out of date.

4. How we store and protect the data

  • OAuth tokens are encrypted at rest. Access and refresh tokens are stored as encrypted bytes using PostgreSQL pgcrypto (pgp_sym_encrypt), in a table reachable only by the server's service role. The encryption key lives in the server environment, never in the database. Tokens are decrypted only in-memory, only by a privileged server-side routine, only to call Google's APIs.
  • OAuth flow integrity. The authorization handshake is protected by single-use, HMAC-signed state values (replay-counted) to prevent CSRF/replay.
  • Access control.Token storage is not exposed to browser clients or to other tenants; each client's data is isolated, and only authorized operators can view it.
  • Pulled records. Aggregate figures retrieved for the dashboard (property identifiers, key-event and topline summaries) are stored alongside the connection record for display.

5. Revoking access and deleting data

  • Disconnect inside Orient. When an operator disconnects a data source, Orient revokes the token at Google(calling Google's token-revocation endpoint on a best-effort basis) and then destroys the stored tokens— the tokens are deleted regardless of the revocation call's outcome, so none are ever left behind. The connection is then marked disconnected in the audit trail.
  • Revoke from your Google Account.You may also remove Orient's access at any time at myaccount.google.com/permissions. Revocation is honored — once revoked, Orient can no longer access your Google data.
  • Deletion. Stored tokens are deleted on disconnect. Aggregate records pulled for the dashboard are retained until the connection or the client account is removed, and are deleted on request to privacy@orient-ai.services.

6. What we do NOT do

  • We do not sell, rent, or share Google user data with any third party.
  • We do not use it for advertising, and we do not use it to train, develop, or improve any generalized machine-learning or AI models.
  • We do not transfer it except as needed to provide the dashboard to the operating team, or where required by law.

7. Compliance

Orient's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

8. Subprocessors

Google user data is processed on our behalf by our infrastructure providers:

  • Supabase (managed PostgreSQL — encrypted token storage and application database).
  • Vercel (application hosting).

9. This website

This marketing website (orient-ai.services) uses Google Analytics and Vercel Analytics to measure aggregate visitor traffic (pages viewed, approximate location, device). This is standard website analytics about visitors to this site and is separate from the client Google-data handling described above; it does not use the OAuth scopes in section 2.

10. Changes

We may update this policy; material changes will be reflected by the effective date above.

11. Contact

Questions or data-deletion requests: privacy@orient-ai.services.