Privacy Policy
Last updated October 12, 2026
1. What this policy covers
This policy describes how Ophanimus Inc. ("Ophanimus", "we") handles information in Ophanimus: the site at ophanimus.com, the web app, the hosted service that agents connect to, billing, and the Ophanimus installer.
Ophanimus is organized into Organizations. A Personal Organization belongs to one person. A Team Organization is shared, controls the work in it, and we process that work on its behalf. For account, billing, and operational records, we are the controller. We do not have a Data Protection Officer or a representative in the EU or the UK; privacy questions and requests go to privacy@ophanimus.com. The Terms are the contract for using Ophanimus. This policy is about information.
2. Information we collect
Account. Email address, display name, and a salted hash of your password, or, if you sign in with Google, your Google account identifier and email address (we keep no other Google profile data). Organization and project membership, roles, invitations, sessions, API keys and agent connections, an administrative record of account and Organization changes, and your progress through setup.
Work content. What you and your agents write into an Organization: tasks and their fields, claims, progress reports and the notes agents keep while holding a task, chat, attachments, change proposals and directives, activity, and items imported from another tracker. Your own agent submits imported items; Ophanimus does not connect to the other tracker. Ophanimus keeps a full change history of each project, so earlier versions of a task's text remain in that history after the task is edited or deleted.
Ranking signals. What you claimed and what you passed over, skip and unclaim counts, completions, and the per-person ranking weights derived from them. We store the weights; your personal scores are recomputed each time you load the queue.
Billing. Plan, member count, subscription state, and Stripe identifiers. Stripe holds cards and billing addresses; we never see card numbers.
Feedback. What you send through the feedback path, or what your agent relays for you or reports on its own, with the page it was sent from, the app build, and any screenshots. Staff read it; it is not shown back to you.
Waitlist and call requests. If you join the waitlist or ask for a call on this site, the name and email address you enter, anything optional you add (company and role, team size, a note), whether you asked for a call, and which button or campaign link you came from. We keep these requests in our database at Cloudflare, copy each one to a spreadsheet in our Google Workspace, email you a confirmation, and email ourselves a copy of each request so we can follow up. If you book a call on our Google Calendar appointment page, the booking is written into our Google Calendar (your name, email address, the time you chose, and a Google Meet link), and Google processes it under its own privacy policy.
Operations. To rate-limit the waitlist and call form, the connecting IP address (for IPv6, its /64 prefix) is hashed with a fixed prefix; we keep the hash, not the address, and entries older than two minutes are removed by the next submission. The address itself is not stored with your request. In the app, IP addresses, held briefly to rate-limit endpoints that do not require sign-in; short-lived sign-in attempt records; and server logs of events, identifiers, and errors, not task content. Our edge provider sees the IP address and browser of every request. We also keep a record of the account, security, work, and billing email we send you.
Where it comes from. Most of it comes from you. Some comes from Google when you sign in, from teammates who invite you or write about you, from connected agents, and from imported trackers, which can name people who do not use Ophanimus; telling them is the Organization's job.
Sensitive information. Your sign-in credentials are the only sensitive personal information we hold, and we use them solely to sign you in. Ophanimus is not a HIPAA or PCI service. Do not put card numbers, government identifiers, or health records in tasks.
3. How we use it
To provide and secure the service, run the execution graph and ranking, bill Team Organizations, send the email above, debug and prevent abuse, respond to support, privacy, and legal requests, follow up on waitlist and call requests, understand whether the product works from usage events that carry no name or task content, though they can be linked to your account, and keep the records the law requires. We do not sell personal information. We do not use it for advertising. We do not train a shared Ophanimus model on ticket bodies.
Where European or UK law applies, we rely on our contract with you for the service, on our legitimate interests for security, ranking, and product measurement (you can object; see section 8), on legal obligation for tax records and lawful requests, and on consent only where the law requires it, which you can withdraw by email. An email address and a password or Google sign-in are needed to have an account; nothing else is required.
4. Agents, embeddings, and ranking
Ophanimus is not the agent. A connected agent acts through your identity, and whatever it reads may also go to its own vendor under that vendor's terms. The installer's hook scripts run only on your computer: they print guidance into the agent's context and, on harnesses that support it, block the harness's built-in task tools so that task state goes to Ophanimus. They never read your conversation or your prompts and make no network calls. Information reaches Ophanimus when your agent calls Ophanimus's tools, which the installed rules ask it to do as it works, including relaying feedback to us. The connector also fetches the rules and your inbox summary when it starts and identifies the harness on each request.
To rank your queue, task titles and descriptions are sent to OpenAI to compute embeddings, without account identifiers, and the results are stored in the Organization. Titles and descriptions are your words and can contain personal information you typed. Under OpenAI's API terms, what we send is not used to train its models, though OpenAI may keep it for up to 30 days for abuse monitoring. Notes, chat, and attachments are not sent.
Ranking is profiling in the legal sense: we use your past choices to suggest what to do next. No decision about you is automated. Within a Team Organization, project members can see the scores Ophanimus computes for a teammate, and any member can export every member's ranking evidence and weights, each attributed to the person it came from; you can reset your own weights.
5. How we share it
Inside the Organization, according to roles and grants; Organization owners and admins can read every project. With service providers: Amazon Web Services (hosting and encrypted backups, in the United States), Cloudflare (edge delivery, DNS, email, and storage of waitlist and call requests), Stripe (payments), Google (sign-in; Google Workspace, where the Google Sheets copy and our own email copy of each waitlist and call request are kept; Google Calendar and Meet, if you book a call), OpenAI (embeddings, as above), and, if we enable usage credits, a credits provider that receives only a pseudonymous identifier and usage events. Our public pages load fonts from third-party hosts, and the app checks the installer's latest version against the npm registry; those hosts see your IP address and browser. When an application connects through OAuth, we fetch its public metadata from the address it publishes. We may also disclose information to comply with law, to protect Ophanimus or others, to investigate abuse, or in a merger, financing, or sale of the company.
We process and store information in the United States. No adequacy decision covers us. For EU and UK data, transfers rely on our providers' data processing terms, which include the European Commission's standard contractual clauses and the UK Addendum where required. Email us for a copy of the safeguards we rely on.
6. Cookies, browser storage, and your computer
The app sets a session cookie, q_sid (HttpOnly, SameSite=Lax, Secure on HTTPS), and a short-lived cookie during Google sign-in, and keeps preferences in your browser's storage, including task identifiers and the order you arranged them in, but never task text. The public pages set no cookies. They use cookieless Cloudflare Web Analytics, which counts page views without cookies or cross-site tracking.
On your computer, the installer keeps your credential and its caches under ~/.Ophanimus, with the credential restricted to your user account; writes hook scripts and rules into your harness configuration; and writes receipt files into a repository when you run its verify step there. Ophanimus uninstall --purge removes the harness configuration it installed, deletes the stored credential, and revokes the connection; the caches under ~/.Ophanimus and any receipt files it left in a repository stay until you delete them.
7. How long we keep it
Account, Organization, and work records for as long as the account or Organization exists; billing records for as long as tax law requires; security and audit records for as long as we need them; waitlist and call requests, including the spreadsheet and email copies in our Google Workspace and any calendar booking, until you ask us to delete them or we no longer need them to follow up. The waitlist form's IP hashes are removed by the next submission more than two minutes after they were recorded. One-time links, unfinished uploads and drafts, and the app's rate-limit counters are removed on fixed schedules of between an hour and a week; a session record is removed a week after the session ends, and a session ends after 30 days idle or 90 days at the latest; read notifications and activity entries are removed within about three months. Backups of the product database are kept for seven days. Cloudflare keeps a rolling point-in-time history of the database that holds waitlist and call requests for 30 days, so a deleted request or an expired hash can be restored for that long. Where we keep encrypted off-site copies, they cannot be deleted for at least 35 days and are then removed by a retention rule set to one year. The project change history, ranking evidence, and audit log are append-only while the Organization exists, and records of revoked agent connections and sent email are kept.
Deleting a task removes it and its attachments but not its earlier text from the project history. Chat is hidden rather than erased. Deleting a project hides it. Revoking an agent connection stops it at once and keeps the record. A Team Organization owner can delete the Organization in the product, which deletes its data, subject to backups and tax records; it cancels the subscription with no refund, as the Terms state. Personal Organizations cannot be deleted in the product. To delete one, close an account, or export work, email privacy@ophanimus.com. If you ask us to erase specific personal data from a project's history, we will assess the request and erase what the law requires, which may mean deleting the Organization.
8. Your choices and rights
In the app you can request a password-reset email, sign out all your sessions, revoke API keys and agent connections, and leave a Team Organization unless you are an owner or its last member.
If you are in the EU, the UK, or California, you can ask to access, correct, delete, export, restrict, or object to processing of your personal information, and you can complain to us or to your data protection authority. Email privacy@ophanimus.com; no account is needed. We respond within the time the law allows, verify requests through the email address on the account, accept authorized agents with your signed permission, and never treat you differently for asking. For Team work content, the Organization is the controller, and we may route the request there.
We do not sell personal information, and we do not share it for cross-context behavioral advertising, including the personal information of anyone under 16; because of that, we do not treat opt-out preference signals as requests. In the terms California law uses, the categories we collect are identifiers; customer records; commercial information; internet or other electronic network activity information; professional or employment-related information; audio, electronic, visual, or similar information (screenshots and attachments); inferences; and, as sensitive personal information, account log-in credentials. We collect them from the sources in section 2, use them for the purposes in section 3, disclose them to the service providers in section 5 for those purposes, and keep them as section 7 describes.
9. Security
Organizations are isolated in the database, product access requires sign-in or a grant, connections use HTTPS, passwords and stored tokens are hashed, the database and backups are encrypted at rest, and changes to work are recorded in an append-only history. Staff access is limited to operating the service and reading feedback; there is no staff tool for browsing an Organization's work. The running app must read ticket content to rank it, and no hosted tracker can promise that a fully compromised server would see nothing. If a breach puts your information at real risk, we will notify you and the regulators as the law requires. Report security issues to privacy@ophanimus.com.
10. Age
You must be at least 18 to create an Ophanimus account. We do not knowingly collect personal information from children.
11. Changes
If we change this policy, we will update the date above and, for material changes, email the address on the account. If we start using Google sign-in data in a way this policy does not describe, or enable an integration this policy does not cover, we will update this page first and ask for any consent the law requires.
12. Contact
Ophanimus Inc. provides Ophanimus. Privacy and legal requests: privacy@ophanimus.com. Everything else: hello@ophanimus.com.