Privacy Policy

1. Information We Collect

Information you provide or store locally

• Information you voluntarily include when you contact us
• Your email address and an internal account identifier if you request a passwordless account link
• Client requests, context, draft replies, and review activity you add to your personal workspace
• Ant profile settings, drafting instructions, signatures, per-request assignments, and per-Ant knowledge-note placements you save in My Ants, Ant Studio, or the local Knowledge Library
• Document or research questions, supplied source text and provenance, objectives, context, selected knowledge notes, structured brief drafts, evidence excerpts, exact run sources, and Ant snapshots you add to the Brief Workbench
• Local approval snapshots, clipboard handoff timestamps, handled or archived states, and content-free outcome labels you choose
• Next steps you explicitly track from an approved email or brief, including the editable title, owner, due date, lifecycle state, and a frozen label and copy of the approved source item

Information collected automatically

• Usage data — pages visited, time spent, referring origins when the browser provides them, and navigation patterns
• Device data — browser type, operating system, screen resolution, and language preference
• IP address — used for approximate geolocation and security purposes
• Product usage events — fixed workflow, milestone, origin, starter, workspace-mode, and brief-run-scope categories; never the work itself or a local record identifier
• Authentication and security data — essential session cookies, sign-in timestamps, and security logs processed when optional accounts are enabled

2. How We Use Your Information

We use the information we collect to:

• Improve our website, content, and user experience
• Understand how visitors use our Site so we can make it better
• Respond to your questions or requests
• Protect against fraud and ensure the security of our platform
• Keep a browser-local record of approved handoffs and the content-free outcome labels you choose
• Keep the local Next Steps working copies you explicitly create and their frozen approval provenance
• Authenticate you and keep the single cloud backup you explicitly create, replace, restore, or delete

We will never sell your personal information to third parties.

3. Browser Storage and Analytics

ANTS uses browser storage for the local product features you choose to use and cookie-free Vercel Analytics for aggregate website measurement. If optional accounts are configured and you sign in, ANTS also uses essential authentication cookies. These include:

• Local browser storage — keeps your opted-in personal workspace and the non-content coordination values described below on this device
• Cookie-free analytics — helps us understand aggregate visits and the fixed product events described below without setting an analytics cookie
• Essential authentication cookies — keep an optional Supabase account signed in and refresh its session; they are not analytics or advertising cookies

You can clear local browser storage through your browser settings; doing so removes the personal workspace saved in that browser but does not delete a separately created cloud backup. Signing out clears the account session but does not delete either copy.

4. Data Storage and Security

When you start or restore a personal workspace, ANTS stores requests you add, reply drafts, document- and research-brief tasks and runs, exact source and Ant snapshots, review decisions, immutable approval revisions, clipboard copy timestamps, handled or archived states, content-free feedback, activity, per-request Ant assignments, and saved Ant profile settings and knowledge notes in your browser's local storage. It also stores Next Steps you explicitly choose to track, their editable owner and due date, completion or archive state, and frozen source text and identifiers from the exact approval. Editing a tracked copy does not edit its approval, and its frozen provenance remains available if the source request or brief is later superseded or deleted. It also stores non-content coordination values such as a workspace identifier, activation state, and timestamps to prevent stale browser tabs from overwriting a replaced workspace. This data is not uploaded merely because you add or edit a request or brief, approve or copy an output, track or update a next step, record an outcome, or configure an Ant.

Optional cloud backup is a separate, manual action. When you are signed in and choose to back up this browser, ANTS sends the complete validated personal workspace snapshot to the cloud. That snapshot can include client and sender details, request messages, drafts, Ant settings and knowledge notes, supplied document or research text, evidence excerpts, run history, approvals, copied handoffs, outcomes, and tracked Next Steps. ANTS stores one snapshot for the signed-in account. It does not continuously sync local edits, upload temporary samples, or merge two workspaces. A revision check stops a stale device from silently replacing a newer cloud copy.

The Knowledge Library is a browser-local view of the notes placed with individual Ants. Copying a note to another Ant creates a new, independent local copy; the copies do not stay synchronized. The library does not retrieve content from URLs, independently upload files, continuously sync notes, or create a shared remote knowledge base. Notes are included only when you explicitly back up the complete personal workspace as described above. Editing or deleting a current note does not rewrite the exact knowledge and source snapshots already frozen in workbench runs or approval revisions.

If you submit the optional fixed-choice analytics feedback after a handled workflow, ANTS stores one opaque receipt token in local browser storage. The token is derived from local record identifiers only to avoid showing the same prompt again; the identifiers and token are never added to the analytics event or workspace backup. ANTS keeps at most 250 such tokens and attempts to remove them when you delete the local workspace.

The Workspace Overview reads these validated browser-local records to derive review priorities, handoffs, due Next Steps, configured Ant counts, and recent local activity. Opening the Overview does not create a new activity record or upload workspace content. Its activity list is limited to timestamps still present in the current workspace and is not represented as a complete audit log.

Task Paths also read the validated Workbench and Next Steps records already saved in the browser. They derive each stage from a real run, reviewable current draft, exact current approval, copy record, handled attestation, or exact tracked-source identifier. Opening a Task Path does not create a separate progress record, run work in the background, upload workspace content, or verify an outside action. Starting a path writes nothing until you save its first Workbench brief.

Ant Studio and the Knowledge Library can read a text or Markdown file you choose on your device. The file is decoded and validated in your browser. ANTS does not persist the original file bytes; only the normalized text chunks and a safe filename label are added to the chosen Ant's local knowledge after a successful import. Selecting a file does not upload it.

The temporary sample workspace runs only in memory for the current visit. Its sample requests, edits, approvals, and activity are not written to your personal workspace or included in its JSON backup.

Workspace controls let you download a versioned JSON backup containing personal workspace data only. A restore file is read, migrated if necessary, validated, and previewed entirely in your browser; selecting it does not upload it. Restoring replaces rather than merges the personal workspace, and nothing changes until you confirm.

The cloud-backup screen separately lets a signed-in user preview a cloud snapshot before replacing this browser's workspace, download the current local copy first, or delete the cloud snapshot. A cloud restore is replace-not-merge and requires confirmation. Deleting a cloud snapshot leaves the browser workspace untouched; deleting a browser workspace leaves the cloud snapshot untouched. A small local receipt contains only an opaque account key, revision, workspace lineage, timestamp, and one-way SHA-256 content digest so ANTS can explain whether local changes have been backed up. It does not contain the raw workspace fingerprint and is not part of an export.

After you delete a personal workspace, ANTS may retain a random, non-content clear marker in local storage. It contains no request or profile information and exists only to stop an older queued browser write from restoring deleted workspace data.

We take reasonable measures to protect your personal information from unauthorized access, alteration, or destruction. All data transmitted between your browser and our servers is encrypted using industry-standard SSL/TLS protocols. However, no method of transmission over the internet is 100% secure, and we cannot guarantee absolute security.

5. Third-Party Services

We may use third-party services for hosting, analytics, and email delivery. These providers may process your data on our behalf and are bound by their own privacy policies. We only work with providers that meet industry-standard security and privacy requirements.

If optional accounts and cloud backup are enabled, Supabase processes the account email, authentication session, security records, and the one user-owned workspace snapshot on our behalf. ANTS uses the signed-in user's session and database row-level security for access; it does not place a service-role credential in the browser. Requesting a magic link sends an authentication email.

If AI drafting is configured, it remains optional. Before an email request, the workspace asks you to confirm the sender details, subject, message, visible context, current draft, selected Ant settings, and knowledge notes that OpenAI will process. Before a brief request, the workbench separately lists the supplied source text, question or objective, context, selected Ant settings, any current draft, and only the knowledge notes you explicitly selected. Research source links and provenance are labels you provide; ANTS does not open, retrieve, or independently verify them. Both requests use the provider's store: false option. OpenAI may still process the submitted content under its applicable terms and policies. Merely placing or copying a note in the Knowledge Library does not submit it; knowledge is included only in the explicitly confirmed AI request described above. The response is only a proposal for review: no email is sent, no content is published, no file is changed, and no task is created by this action.

The Site uses Vercel Analytics for general website usage and a small, allowlisted set of product events. Before an analytics URL is sent, ANTS removes its query string and hash. A site-wide origin-only referrer policy also prevents page paths, queries, and hashes from appearing in browser referrers. Local deep-link values such as task, Ant, approval, or Next Step identifiers are therefore not added to analytics event data or referrer headers. Loading, reloading, or opening a workspace deep-link URL can still send its opaque query identifier to the hosting infrastructure as part of the ordinary page request. Custom events can contain only fixed categories: the workspace mode choice; Email, Document, or Research workflow; a predefined milestone; manual, AI, or not-applicable origin; personal or sample mode; first, repeat, or not-applicable brief-run scope; and the Document or Research starter selected. Milestone and feedback events encode those fixed categories into no more than two properties per event. Custom product events are collected only when the deployment's Vercel plan supports them. ANTS does not add client request text, titles, supplied source text or labels, draft or approved output, sender details, filenames, Ant settings or knowledge, timestamps, raw errors, local record identifiers, source snapshots, approval snapshots, search text, or local handoff outcome and attention labels to analytics events.

After a real workflow is marked handled, ANTS may show an optional fixed-choice product feedback prompt. Submitting it adds only the selected usefulness, an optional reason when chosen, workflow, and prompt-location categories to the analytics event. Vercel Analytics also processes the path-only route and its standard visit data. The prompt has no free-text field, and the choices are shown before you submit. This is separate from the Email handoff outcome and attention labels, which remain local. Choosing a copy action places the selected plain text on your device's operating-system clipboard; ANTS does not treat copying as sending or publishing and cannot verify what happens after that.

6. Your Rights

Depending on your location, you may have the following rights regarding your personal data:

• Access — request a copy of the personal data we hold about you
• Correction — request that we correct inaccurate data
• Deletion — request that we delete your personal data
• Portability — request your data in a portable format

To exercise any of these rights, contact us at the email address listed below.

7. Data Retention

A local workspace remains in that browser until you delete it or clear browser storage. A cloud snapshot remains until you delete it from the cloud-backup screen, the associated account is deleted, or it must be removed under an applicable legal obligation. Signing out alone does not delete local or cloud workspace data. Other personal information is retained only as long as necessary for the purposes described here or as required by law.

8. Children's Privacy

ANTS is not directed at individuals under the age of 16. We do not knowingly collect personal information from children. If you believe we have inadvertently collected such information, please contact us and we will promptly delete it.

9. Changes to This Policy

We may update this Privacy Policy from time to time. When we make changes, we will update the "Last updated" date at the top of this page. We encourage you to review this policy periodically. Continued use of the Site after changes constitutes acceptance of the updated policy.

10. Contact Us

If you have any questions about this Privacy Policy or how we handle your data, please contact us at: