Privacy Policy

Last updated October 31, 2026

Operator and scope

Orrerie LLC, trading as Orrerie
Limited Liability Company – Domestic
Registered in Wyoming, United States · Filing ID: 2026-002087422
Principal office: 30 N Gould St, #58667
Sheridan, Wyoming 82801
USA
hello@orrerie.com · +1 423 487 1746

Orrerie LLC operates the AI service at orrerie.com. This policy covers that service, including its account console, agent missions, public shares and publications, support, notifications and billing. It does not replace the privacy terms of Anthropic, OpenAI, Google, Apple, user-connected services or websites an agent visits at your direction.

Orrerie does not sell personal information or use third-party advertising pixels. Service providers and user-directed destinations receive information only for the purposes described below.

Information you provide

  • Account data: name, email address, profile image where provided, authentication method and account preferences.
  • Email authentication: a one-way password hash, verification and reset state, two-factor configuration and hashed backup codes. Orrerie does not retain your plain-text password.
  • Content: prompts, replies, images, PDFs, pasted text, generated files, publications, personas, workspace files and mission instructions.
  • Connections: connector definitions, encrypted OAuth tokens, encrypted API or vault secrets, and the account identifiers needed to show a connection.
  • Support: feedback text, category, optional screenshots or files, and correspondence.
  • Billing: plan, USD price, promotion, payment reference, status, timestamps and usage records, with the checkout and payment identifiers of the processor you paid through (Stripe or Dodo Payments), the currency and amount charged when you paid in another currency, the tax amount for a Dodo Payments purchase, and the payment, refund and dispute status. Orrerie never receives or stores card numbers or bank details.

Technical and activity information

Orrerie processes session identifiers, IP address, user agent, security and authentication events, request timing, error and delivery logs, model and token usage, plan consumption, notification state, and mission/tool events needed to operate and secure the service.

The service does not intentionally use advertising identifiers or create cross-site marketing profiles. Infrastructure providers may process ordinary network metadata when delivering traffic.

Why information is used

  • Provide accounts, AI responses, agent missions, files, publishing, connectors, billing, support and notifications.
  • Authenticate users, preserve session continuity, enforce ownership and prevent fraud, abuse and security incidents.
  • Calculate plan usage, reconcile payments, issue service messages and maintain financial records.
  • Debug failures, improve reliability and comply with law, provider rules and valid legal requests.

Where data-protection law requires a legal basis, processing is based as applicable on performance of the service contract, legitimate interests in operating and securing the service, consent for optional connections or notifications, and legal obligations.

Storage architecture

Private runtime data is stored in account-scoped files on Orrerie’s server. Selected JSON records may also use a narrowly scoped MySQL key-value store, with filesystem fallback. Sessions, uploads, mission workspaces, journals, publications and configuration remain filesystem-backed.

Private runtime directories are outside the public web root. Public shares and publications are available to anyone with their public URL until revoked; generated applications use a separate content origin. Do not publish information you intend to keep private.

AI model providers

Orrerie sends the input, conversation context, tool definitions and attachments needed for the selected feature to the model provider shown in the console. Anthropic processes ordinary Claude chat and Anthropic agent missions through its commercial API or Agent SDK. Anthropic currently states that, by default, it does not use inputs or outputs from its commercial products to train generative models unless the customer opts in; its own terms, Data Processing Addendum and policies govern that processing.

Review Anthropic’s Privacy Policy, Commercial Terms and Usage Policy. Orrerie is independent and is not affiliated with or endorsed by Anthropic.

OpenAI processes OpenAI chat through its Responses API and agent missions through Codex App Server, returning model output, tool events and usage information. OpenAI states that API data is not used to train or improve its models unless the customer explicitly opts in; default abuse-monitoring logs may be retained for up to 30 days. Review OpenAI’s Services Agreement, Data Processing Addendum, API data controls and Usage Policies. Orrerie is independent and is not affiliated with or endorsed by OpenAI.

Agent browsing and connected services

When you direct an agent to use a website or service, that destination receives the requests, account data, cookies, files and form values necessary to perform your instruction, just as it would in a browser you operate. Browser profiles and explicitly saved sessions can retain third-party cookies and web storage for later authorized use.

Optional Google connections can access Gmail, Calendar and Drive within the scopes shown during authorization. Apple Music, remote MCP servers and other services process data only when you connect or invoke them. Their privacy terms apply. External writes may require an in-product approval, but you remain responsible for the instruction and destination.

Payments

Plans are paid by card, UPI, bank payment or another local method shown at checkout for your country, through Stripe Checkout, provided by Stripe, or, where it is offered, through Dodo Payments’ checkout. When you pay through Stripe, you enter your card or other payment details, or approve the payment in your bank or UPI app, on or from Stripe’s own secure page; card numbers, security codes and bank details go straight to Stripe and never reach Orrerie’s servers. Orrerie sends Stripe the plan name, USD price and an order reference, not your name or email address. Stripe collects the card or other payment details, the email address and billing details its page asks for, and device and connection data, to process the payment, prevent fraud and meet its legal duties. Stripe handles this information under Stripe’s Privacy Policy, in part as an independent controller. To offer your local currency, Stripe’s page uses the location it detects for your connection. Orrerie receives back from Stripe only the payment’s identifiers, the amount and currency charged with Stripe’s USD conversion figures, and its payment, refund and dispute status, and keeps them with your plan record.

When you pay through Dodo Payments, you enter your card or other payment details, or approve the payment in your bank or UPI app, on or from Dodo Payments’ own secure page; they go straight to Dodo Payments and never reach Orrerie’s servers. Dodo Payments is the merchant of record for that purchase. Orrerie sends it the plan name and identifier, the USD price and an order reference, not your name or email address. Dodo Payments collects the card or other payment details, name, email address, billing address and device and connection data its page asks for, to sell and charge the purchase, calculate and remit tax, issue the receipt, prevent fraud and meet its legal duties, and handles this information as a controller under Dodo Payments’ Privacy Policy. When Orrerie reads the payment back to confirm it, Dodo Payments’ reply also contains the name, email address and billing country entered on its page; Dodo Payments chooses the local currency it offers from the billing country you enter. Orrerie uses that reply only to confirm the payment and keeps from it only the payment’s identifiers, the amount and currency charged, its USD settlement amount, tax and payment, refund and dispute status with your plan record. Dodo Payments’ link back to Orrerie can carry the payment identifier, its status and the email address entered on its page; Orrerie does not use them, and the console removes them from the address bar.

Orrerie does not collect bank-account credentials and makes no identity check of its own.

Service providers and disclosures

Information may be processed by infrastructure and content-delivery providers, Anthropic, OpenAI, Stripe and Dodo Payments for payments, authentication providers, configured mail delivery, browser push services and services you connect. The current categories and purposes are listed on the Subprocessor List.

We may disclose limited information when reasonably necessary to comply with law, respond to valid legal process, investigate fraud or abuse, protect rights and safety, or complete a business reorganization subject to appropriate safeguards. We do not disclose content to advertisers.

Cookies and browser storage

Orrerie uses essential session cookies to authenticate accounts and may use short-lived functional cookies on publication routes. The application uses local browser storage for interface preferences, live-task recovery markers and user-selected checklist state. Public generated applications can have separate storage on their isolated origin.

Stripe’s and Dodo Payments’ checkout pages run on their own domains and use their own cookies under their own policies. There are no Orrerie advertising cookies. Disabling essential cookies or storage can prevent sign-in, preferences, recovery or publication features from working.

Retention and deletion

Account content remains in active storage until you use an applicable deletion control or request account deletion. The console provides per-conversation and all-conversation deletion; generated workspace files can be downloaded. Account access, portability, deletion and privacy requests can be sent to hello@orrerie.com.

Deletion removes the active service copy, subject to technical completion, fraud prevention, payment reconciliation and legal recordkeeping. If protected backup copies are maintained, residual data can remain until the applicable backup rotation overwrites it. Payment, security, abuse and support records may be retained for the period reasonably required for disputes, accounting, safety or law.

Security

Controls include HTTPS in production, scoped server sessions, server-side ownership checks, optional two-factor authentication, hashed passwords and backup codes, encryption for stored connector secrets, restricted private storage, authenticated loopback services, sandboxed mission workspaces, outbound network guards and isolated publication content.

No system is perfectly secure. Keep credentials private, enable two-factor authentication where available, review agent approvals and report suspected incidents to hello@orrerie.com. More detail appears on the Security page.

International processing and your rights

Orrerie LLC is registered in Wyoming, United States. Providers and destinations you authorize may process information in countries other than yours. International processing is subject to applicable legal requirements and the safeguards relevant to each provider relationship.

Depending on your location, you may have rights to access, correct, export, delete, restrict or object to processing, withdraw consent, or complain to a supervisory authority. We may need to verify your identity before fulfilling a request. Contact hello@orrerie.com.

Changes and contact

Material changes will be reflected in the date above and, where appropriate, notified through the service. Questions about privacy, deletion, security or providers can be sent to hello@orrerie.com.