# Privacy Policy — OneDroid > How OneDroid collects, uses, and protects your data — including data accessed through Google APIs and other connected services. Canonical: https://onedroid.ai/privacy OneDroid Legal # Privacy Policy Effective date: 19 July 2026 · Last updated: 19 July 2026 ## Who we are OneDroid (onedroid.ai) is AI agent infrastructure built and operated by Providentia Worldwide ("OneDroid", "we", "us"). This policy covers the OneDroid website (onedroid.ai), OneDroid Synapse (synapse.onedroid.ai), and OneDroid Engram (engram.onedroid.ai) — together, "the Service". Questions or requests: michal@onedroid.ai. ## The short version - We collect the minimum needed to run a governed gateway: your account details, the credentials you choose to connect, and a metadata log of tool calls. - We do not sell your data. We do not use your data for advertising. We do not train AI models on your data. - Data accessed through connected services (including Google) is used only to execute the tool calls you or your agents explicitly make. - With bring-your-own-database, your data lives in infrastructure you control. ## What we collect Account information. When you sign up we collect your name, email address, and authentication identifiers. Sign-in is handled by our authentication provider, Clerk. Connected credentials. When you connect a third-party service (for example Google Workspace, Atlassian, or Slack), we store the resulting OAuth grants or API tokens, encrypted at rest. These credentials exist for one purpose: executing the tool calls that you, or agents acting under your account, explicitly invoke. OneDroid Synapse is designed so that agents receive tool results, not the underlying tokens — raw credentials are held by the gateway and are not exposed to connected agents. The audit log. OneDroid Synapse's audit log (called the event log in the product) is designed to record metadata about every tool invocation — which account and agent made the call, which tool was called, timestamps, latency, the outcome, and cryptographic hashes of arguments and results — rather than storing your documents, messages, or files as retrievable content. Tool-call arguments can themselves contain content you or your agents supply; we hash rather than store them in the audit log, and we work to keep content out of operational logs, though we cannot promise that no fragment ever appears in error telemetry. Content you store. Documents and knowledge you deliberately write to OneDroid Engram are stored so they can be searched and versioned, in the platform database or in your own database if you use bring-your-own-database. Website and operational data. Our website sets no advertising or analytics cookies. The applications set strictly necessary cookies for sign-in and session security (via Clerk) — nothing else. Walkthrough videos on the quickstart page are embedded from YouTube in its privacy-enhanced mode (youtube-nocookie.com): nothing is set until you press play, and from then on YouTube's own policy applies. Our hosting providers keep standard server logs (IP address, request path, user agent). Fonts are loaded from Google Fonts, which receives standard request data when the page loads. The applications keep operational telemetry (errors, performance) needed to run the Service. ## Access to your content Humans at OneDroid do not read the content that passes through the gateway or that you store in the Service — whether it comes from Google, another connected service, or OneDroid Engram — except with your explicit permission, where necessary for security or abuse investigation, or where required by law. ## Google user data If you connect a Google account, OneDroid Synapse requests only the scopes you approve on the Google consent screen (for example Gmail, Drive, Calendar, Docs, Sheets, or Slides access). - How it is used. Google user data is accessed solely to execute the specific tool calls you or your authorized agents invoke — for example reading a message you asked an agent to summarize, or creating a document you asked an agent to write. Content passes through the gateway to your agent; the audit log retains call metadata and hashes, not the content itself. - What we do not do. We do not use Google user data for advertising. We do not sell it. We do not use it to train AI or machine-learning models. Humans at OneDroid do not read it except with your explicit permission, where necessary for security or abuse investigation, or where required by law. - Storage. Google OAuth tokens are stored encrypted at rest. Google user content is not retained by the Service beyond serving your request, except where you explicitly store it (for example, saving a document into OneDroid Engram). If you save Google-sourced content into OneDroid Engram, search embeddings for it are computed by our embedding provider (OpenAI) under terms that prohibit training on your data. - Revocation and deletion. You can disconnect Google at any time in OneDroid Synapse, or from your Google Account security settings. On disconnection or account deletion, stored Google tokens are deleted. OneDroid's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. ## Bring your own database OneDroid Synapse and OneDroid Engram support storing your governance state, credential grants, audit log entries, and documents in a database you provide and control. In that configuration, the data resides in your infrastructure and under your policies; we access it only as needed to operate the Service for you. We do not inspect, validate, or take responsibility for the contents of your database — what is stored there, its accuracy, lawfulness, security, and retention are yours to govern. ## How we share data We do not sell personal data, and we do not share it with third parties for their marketing. We share data only with: - Subprocessors that host and operate the Service: Amazon Web Services and Microsoft Azure (application hosting), Supabase (platform database hosting), Clerk (authentication), Vercel (website hosting), OpenAI (computing search embeddings for content you store in OneDroid Engram, under terms that prohibit training on your data), and Google Workspace (support email). Each processes data only to provide their service to us. - Connected services you choose — when a tool call you invoke sends data to a service you connected, that transfer happens at your direction and is governed by that service's own terms and privacy policy. - Legal requirements — if required by law, or to protect the rights, safety, or security of OneDroid, our users, or the public. ## Retention and deletion Account data and stored credentials are kept while your account is active. When you delete your account or disconnect a service, the associated credentials are deleted and grants revoked. Audit log entries on the free hosted tier are retained for 12 months and then deleted, and are deleted within 30 days of account deletion — except entries we must keep for security investigations or legal obligations. Data in your own database is retained entirely under your control. To request access, correction, export, or deletion of your data, email michal@onedroid.ai — a human reads it, and we aim to reply within a few business days, always within the timelines applicable law requires. ## Where GDPR or CCPA applies Where the GDPR applies, we process your data to perform our contract with you (running the Service), in our legitimate interest in keeping the Service secure and reliable, and otherwise on your instruction or consent. Our subprocessors operate in the United States; if you need documentation covering international transfers, or a data processing agreement for your team, email michal@onedroid.ai. You can also lodge a complaint with your local data protection authority. We do not sell or share personal data as those terms are defined in the CCPA. ## Security All traffic is encrypted in transit (TLS). Stored credentials are encrypted at rest. Tool access is scoped by hub, role, and policy, and every invocation is written to the append-only audit log. No method of transmission or storage is perfectly secure; we publish what the gateway can and cannot see rather than promising absolutes. ## Children The Service is not directed to children under 16, and we do not knowingly collect their data. ## Changes to this policy If this policy changes, we will post the new version here and update the effective date. Material changes will be flagged on the website. ## Contact Providentia Worldwide — OneDroid michal@onedroid.ai providentiaworldwide.com