Privacy Policy

Autom8x is a service operated by Snoopy LLC, 14355 Francis Lane, Frisco, Texas 75035, United States ("Autom8x", "we", "us"). For account, billing, and usage information, Snoopy LLC is the data controller. For workspace content and data processed by the automations a business enables, that business is the controller and Autom8x processes the data on its documented instructions; business customers can request our data processing terms at singh@autom8x.ai.

The service is offered from the United States and is not currently directed to persons in the European Economic Area or the United Kingdom.

Account information. You sign in with a Google, Microsoft, or Apple account — Autom8x has no passwords. From your sign-in provider we receive your name, email address, and profile picture, and we use them to create and identify your Autom8x account. We do not receive your provider password, and signing in does not give Autom8x access to your files, mail, or any other content in that provider account.

Workspace content. What you and your team put into the platform: workspaces, team membership, automation subscriptions and their configuration, runs with their results and the files you give them, and approval decisions.

Connected accounts for automations. If you connect a provider account so an automation can use it, you approve that access on the provider's own consent page — it is always a separate, explicit grant, never something sign-in creates silently. The access tokens the provider issues are stored encrypted (AES-256-GCM envelope encryption). Automations never hold your credentials; the platform makes each provider call on their behalf and records what was done.

The Autom8x iPhone app. The app signs in to the same account and keeps its session in your iPhone's Keychain rather than in cookies. If you turn on notifications, we store your device's push token so we can tell you when a run needs your approval or has failed; signing out removes it. A file you give a run is uploaded and stored for that run. If you turn on Face ID, your iPhone checks it; we never receive it.

Usage and log data. Standard operational logs (request metadata, IP addresses, timestamps, errors) used to run, secure, and debug the service.

Autom8x uses only strictly necessary cookies: HttpOnly, Secure session cookies that keep you signed in to the web app, and short-lived values that protect the sign-in flow (such as OAuth state). We set no advertising, social media, or third-party analytics cookies. Because we do not track you across other sites, our sites do not respond differently to "Do Not Track" signals; because we do not sell or share personal information, a Global Privacy Control signal does not change how we already treat your data.

For sign-in, Autom8x requests only basic profile information from Google (name, email address, profile picture) and uses it solely to create and operate your account. When an automation you enable needs access to additional Google data, such as sending mail from your account, that access is requested separately on Google's consent screen and used only to provide the feature you enabled.

Autom8x's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. We do not sell Google user data, do not transfer it for advertising, and do not permit humans to read it except with your affirmative agreement, for security purposes such as investigating abuse, to comply with applicable law, or where the data has been aggregated and anonymized and is used for internal operations.

An automation can have an AI model read the file given to its run, and no other file. Invoice Processing does, to read a bill, receipt, credit note or statement before saving its details, recording it in QuickBooks Online, or comparing it with what QuickBooks holds. The platform sends the document, with Autom8x's fixed instructions for reading it, to OpenRouter, which passes the request to the provider of an AI model. For Invoice Processing, nothing else from your workspace goes with it: not your name, email address or other account details, not the flow's settings, and nothing read from QuickBooks; even the file's own name is left out. The document itself goes as uploaded, including anything stored inside the file, such as a PDF's title or author. Only when the first reading looks wrong (totals that don't add up, unclear details, or an amount over the flow's approval limit) does a second model, from a different maker, read it again. A model that gives no usable answer is replaced by the next one on its list, each request under the rules below. What the run makes of the document is kept with the run's results, and the details it saved are shown to the members of your workspace.

Every request tells OpenRouter to use only endpoints in the United States that it lists as zero data retention and that collect no data. Zero data retention means, in the words of OpenRouter's zero data retention guide, that the provider "will not store your data for any period of time"; OpenRouter does not count an in-memory cache of repeated prompts as storing it. A request that no such endpoint can serve is refused, never sent elsewhere. Under these rules a request can reach Amazon Bedrock, Microsoft Azure, DeepInfra, Fireworks, Google Vertex AI, Mistral, Sail Research, Wafer or xAI; which one serves it depends on the model and on OpenRouter's routing. A PDF is sent through OpenRouter's PDF plugin, set on each request to its "native" engine. The zero data retention guide says its enforcement "does not apply to plugins and tools you choose to enable", and OpenRouter's PDF guide says a PDF sent this way is passed directly to the model, not through its optional PDF-conversion services. OpenRouter handles each request before the provider does, and its privacy policy says it may process data in the United States or in other countries.

Autom8x trains no models. Under these rules, the policies OpenRouter publishes, for itself and for each provider above, say your documents are not used to train AI models: OpenRouter's privacy policy says it does not use inputs or outputs for model training, and OpenRouter lists none of the providers above as training on prompts, which a provider that keeps no data cannot do. OpenRouter's data collection guide says it stores no prompts or answers unless an account opts in to logging or to OpenRouter's own use of them, both off by default; Autom8x keeps both off for its OpenRouter account, and that account's settings turn on no OpenRouter plugin by default and no broadcast of requests to other services. OpenRouter keeps metadata such as token counts and timing, and may tag a request with an anonymous topic category for its reports and rankings. Its terms say it may store a request temporarily where it is too large to process in memory, and may screen, remove, edit or block any request it judges to break them or to be objectionable or illegal, including by screening with automated tools for known child sexual abuse material and malware. Its data processing agreement says it deletes a request and its answer promptly once the answer is made, except where the law requires otherwise or where needed to address malicious use of its service, and that it may first classify them automatically to detect violations. Its privacy policy says it may keep an image longer than routing it takes where abuse detection, security, billing or legal compliance requires. See OpenRouter's privacy policy.

A workspace's owners and admins can connect its QuickBooks Online company so that an automation, such as Invoice Processing, can work in it. The connection is approved on Intuit's own consent page, and Autom8x asks only for access to QuickBooks Online accounting (the com.intuit.quickbooks.accounting scope). Through it the platform can read the company's records and settings and create vendors, bills, expenses, vendor credits, journal entries and invoices; it cannot change or delete a record that already exists. Invoice Processing reads the company's information and settings, looks up its accounts, vendors, customers, employees, bills, expenses, vendor credits and journal entries, and creates vendors, bills, expenses and vendor credits: a bill is recorded as a bill and a receipt as an expense; a credit note as a vendor credit, or as a card refund when it was refunded to a card; and a statement is compared, not recorded. When you choose None instead of QuickBooks, it saves the details it read and calls QuickBooks for nothing.

Intuit's tokens for the connection are stored encrypted (AES-256-GCM envelope encryption) and renewed automatically before they expire, and they are never given to an automation: the platform makes each call to QuickBooks for it. QuickBooks' answers are kept for 30 days, so that a step that is retried gets the same answer instead of creating a record twice, and are then deleted. What a run records and finds is kept with the run's results in your workspace, as described in Retention and deletion. QuickBooks data is used only to run your workspace's own automations and show you what they did; none of it is sent to an AI model, and it is never sold or used for advertising. Autom8x does not process QuickBooks data on Intuit's behalf. If you give Invoice Processing an address in its "Also email" setting, such as your bookkeeper's, a short summary of each document it saves, records or compares is emailed there, built from the details read from the document and, when it records the document in QuickBooks or compares it with what QuickBooks holds, from QuickBooks' answer.

An owner or admin can disconnect QuickBooks at any time on the Connections page, on the website or in the app. The platform then deletes the stored tokens at once and asks Intuit to revoke the access, and no automation can reach the company until it is connected again. If you disconnect Autom8x from within QuickBooks instead, Intuit says this invalidates the tokens it gave Autom8x, so no automation can reach the company until it is connected again; disconnecting on the Connections page as well deletes the stored tokens. What earlier runs recorded stays, in QuickBooks and in your workspace; in your workspace, Autom8x uses it only for those runs, to show them to you or to end one still waiting for approval, until you ask us to delete it. An owner or admin can ask us at singh@autom8x.ai to delete what runs kept from QuickBooks, and we will delete it, apart from records the law requires us to keep; a database backup made before then can still hold it, as described in Retention and deletion.

To provide the service: run the automations you subscribe to, enforce your workspace's roles and approvals, show you what happened, and bill for what you use. To secure it: authentication, abuse prevention, and audit. To improve it: aggregate, de-identified usage analysis. We do not sell personal information, we do not share it for cross-context behavioral advertising, and we do not use your data for advertising of any kind.

Only service providers that host and operate the platform for us. Each of these processes data in the United States under an agreement with us: Supabase (authentication and database), DigitalOcean (application hosting), Vercel (website hosting), Backblaze (file storage and off-site backups), Datadog (operational logs and monitoring), Stripe (billing and payments), Resend (email delivery), and Expo (delivering notifications to your iPhone through Apple's push service). When an automation has an AI model read a document, OpenRouter processes it too, and so does the model provider OpenRouter routes the request to, as described in Documents read by AI. We will update this policy before adding or replacing a subprocessor category.

Your sign-in provider (Google, Microsoft, or Apple) and the providers you choose to connect for automations, such as Intuit for QuickBooks Online, are independent services governed by their own privacy policies — they are not our service providers.

We disclose information if required by law, and in a merger or acquisition we would require the successor to honor this policy.

Your data is retained while your account is active, except where this policy says otherwise. A file given to a run becomes eligible for deletion 90 days after the run ends, and is deleted at the next maintenance pass, or at a later one if many files are due at once. A run's step-by-step timeline becomes eligible for deletion about three months after it is recorded, and is deleted at the next maintenance pass. A run's results stay while your account is active.

You can delete your account from Settings. Deletion promptly removes your account, your personal workspace and every organization you alone own, with their workspace content, within the limits below; an organization that has another owner is kept, and you leave it. Operational logs are kept for a limited period for security and debugging. Billing records are kept as long as tax and accounting law requires. Disconnecting a connected provider account deletes its stored tokens immediately and asks the provider to revoke the access.

Deletion, wherever this policy describes it, has four limits. Each night a backup of our database is made: the copy kept on our server is deleted after 14 days, and a copy stored off-site with Backblaze is not deleted on that schedule. A backup can still hold data deleted after it was made, such as the tokens of a provider account since disconnected, which stay encrypted in it. The files given to runs, which are not in these backups, are stored with Backblaze, which can keep an earlier version of a file after it is deleted. Deleting a file does not delete our record of it, which keeps the file's name, type and size, its page count or image dimensions, and a fingerprint of its contents (its SHA-256 hash), but not the file itself. And deleting an account does not delete its sign-in record with Supabase, which handles our sign-in: your email address and the sign-in accounts linked to it, with the profile details their providers sent.

All traffic is encrypted in transit (TLS). Provider tokens are envelope-encrypted at rest under keys held separately from the database. Access is workspace-scoped and fails closed: an unconfigured or unauthorized path refuses rather than degrades. If we learn of a breach of security affecting your personal information, we will notify affected account holders and, where required, regulators without undue delay and in accordance with applicable law; where we process workspace content on a business customer's behalf, we will notify that customer without undue delay after becoming aware of the breach.

You can access, correct, export, or delete your personal information. Account deletion and workspace export are available directly in Settings, and you can make any request at singh@autom8x.ai. We respond to verifiable requests within the time applicable law requires and will never discriminate against you for exercising a right.

In the preceding 12 months we collected these categories of personal information: identifiers (name, email address, account IDs, IP address, and the app's push token if you turn on notifications); commercial information (subscriptions and billing records); internet or network activity (log and usage data); professional information (your workspace and role); audio/visual information (your profile picture); and sensitive personal information limited to credentials for the provider accounts you choose to connect, stored encrypted. We collect them directly from you, from your sign-in provider, from providers you connect, and automatically from your use of the service; we disclose them for business purposes only to the service providers listed above; we retain them as described in Retention and deletion.

We do not sell personal information and we do not share it for cross-context behavioral advertising, as those terms are defined by the California Consumer Privacy Act, and we have not done either in the preceding 12 months. We have no actual knowledge of selling or sharing the personal information of consumers under 16. Because we do not sell or share personal information, we do not provide a "Do Not Sell or Share My Personal Information" link, and we use sensitive personal information only to provide the service you request. Submit requests at singh@autom8x.ai or in Settings; an authorized agent may act for you with signed permission. If you live in a state whose privacy law grants an appeal right and we decline your request, you may appeal by replying to our decision, and if we deny the appeal we will tell you how to contact your state attorney general.

The service is a business tool and is not directed to children. We do not knowingly collect personal information from anyone under 13. If you believe a child has provided us personal information, contact singh@autom8x.ai and we will delete it.

The date at the top is the date this policy was last updated. We review this policy at least once every 12 months. Material changes are announced by email or in the product before they take effect; non-material clarifications take effect when posted. Prior versions are available on request.

singh@autom8x.ai · Snoopy LLC, 14355 Francis Lane, Frisco, Texas 75035, United States.