Privacy Policy
This Privacy Policy explains what personal data [Company legal name] ("Ora", "we", "us") collects when you use oramodel.com, the Ora console and the Ora API (the "Service"), how we use it, who we share it with and the choices you have. It does not cover third-party services you connect to the Service, such as Slack or your own webhooks, which have their own policies.
1. What we collect
| Category | What it contains |
|---|---|
| Account | Your email address, a hash of your password (Argon2id; we never store the password itself), an optional display name, your theme preference, your marketing email preference, and when you created the account and last signed in. |
| Organizations | Organization name, billing email, your role in each organization, invitations (the invitee's email and role) and organization settings such as model improvement and rate limits. |
| API keys | Key name, a short display prefix, a one-way hash of the key, and when it was created, last used or revoked. The full key is shown to you once and never stored. |
| Usage records | One record per request: time, the key or console feature used, model, number of questions, input and output token counts, status code and response time. Usage records do not contain the content of requests or answers. |
| Credits and billing | Credit grants, purchases, refunds and adjustments with their amounts and dates. |
| Security logs | Sign-ins, failed sign-ins, sign-outs, sign-ups, password changes and password reset requests, with the email address entered, IP address and browser user agent. Actions taken by our administrators are recorded in an audit log. |
| Password reset links | A one-way hash of each reset token, its expiry (one hour), when it was used, and the IP address that requested it. |
| Things you save | Saved queries (the full request: model, state, questions and actions), workflows (questions, actions, watchlist and schedule) and their run results (the answers for each symbol), and the delivery log of fired actions (the message that was sent, its destination and the delivery result). |
| Connections | Destinations for actions: a name, the destination host and, encrypted with AES-256-GCM, the webhook URL, headers and signing secret. |
| Communications | Messages you send us, for example to support, and our replies. |
2. Request content and model improvement
The state and questions you send to the API or run in the Playground are processed in memory to produce answers. We do not store request or answer content, except:
- when you choose to save it, as a saved query, workflow, workflow run or action delivery listed above; and
- when an owner or admin of your organization turns on Help improve the model. The setting is off by default. While it is on, your organization allows us to read and analyze its inputs and outputs to understand where the model is weak and to improve it. It applies to everyone in the organization, and turning it off stops this for future requests.
For the financial model, you can send only a symbol; the market data the server adds to answer is not personal data.
3. How we use personal data
- To provide the Service: create and secure your account, authenticate API keys, answer requests, deliver actions you configure, run your workflows and show your usage. (Legal basis where applicable: performance of our contract with you.)
- To bill: meter usage against your organization's credits. (Contract; legal obligation for tax and accounting records.)
- To keep the Service secure: rate limiting, throttling sign-in and password reset attempts, detecting abuse and investigating incidents. (Legitimate interests.)
- To support and communicate with you: service messages such as password resets, security notices and changes to these terms, and, unless you opt out in your profile settings, occasional product updates. (Contract; legitimate interests; consent where required.)
- To improve the Service: using aggregated usage records, and request content only when your organization has turned on model improvement. (Legitimate interests; your organization's choice.)
- To comply with law and enforce our Terms of Service.
We do not sell personal data, share it for cross-context behavioural advertising, or use it to show you ads.
4. Cookies and local storage
We use a single cookie, __Host-jev_sid, which keeps you signed in. It is strictly necessary, is sent only over HTTPS, cannot be read by scripts, and expires after two days. It also protects forms against cross-site request forgery.
The console stores some preferences and unsent drafts (for example Playground drafts and dismissed announcements) in your browser's local storage. That data stays in your browser and is not sent to us.
We do not use analytics, advertising or other third-party cookies, and our pages load no third-party scripts.
5. How we share personal data
We share personal data only as follows:
- Service providers (subprocessors) that host or operate the Service for us, under contracts that limit their use of the data:
| Provider | Purpose | Location |
|---|---|---|
| Akamai Technologies, Inc. (Linode) | Cloud hosting: servers and database for the website, console and API | United States |
If we add a subprocessor (for example an email delivery or payment provider), we will update this list before it processes your personal data.
- Destinations you configure. When an action or workflow fires, we send the configured message to the Slack workspace or webhook you chose. Those recipients are not our subprocessors; you decide what is sent to them.
- Within your organization. Members of an organization can see its members' emails and roles, its keys, usage, saved queries shared with the organization, workflows and delivery logs, according to their role.
- Legal and safety. When required by law or to protect the rights, property or safety of our users, the public or us.
- Business transfers. In a merger, acquisition or sale of assets, subject to this policy.
6. Retention
- Account, organization, API key, usage and saved data are kept while your account exists. When an account is deleted, its API keys, usage records, memberships, password reset records and the action deliveries it triggered are deleted with it. Organizations, and the saved queries, workflows and connections in them, are deleted when the organization is deleted.
- Security logs (sign-in and password events, administrator audit entries) may be kept after an account is deleted, for security and fraud prevention, for as long as reasonably necessary for those purposes.
- Credit and billing records are kept as long as tax and accounting law requires.
- Password reset links stop working after one hour or once used.
- Sessions end after two days, when you sign out, or when your password is changed or reset.
To delete your account, write to us at the address below. You can leave an organization from the console at any time.
7. Security
All traffic to the Service is encrypted with TLS. Passwords are hashed with Argon2id; API keys and password reset tokens are stored only as SHA-256 hashes; connection secrets are encrypted with AES-256-GCM using a key kept outside the database. Access to production systems is restricted to the people who operate the Service. No system is perfectly secure, so please use a strong, unique password and keep your API keys private.
8. International transfers
The Service is hosted in the United States. If you use it from elsewhere, your personal data is transferred to and processed in the United States. Where the law requires it, we rely on appropriate safeguards, such as standard contractual clauses, for these transfers.
9. Your rights and choices
Depending on where you live, you may have the right to access, correct, delete or receive a copy of your personal data, to object to or restrict certain processing, and to withdraw consent. You can update your profile, email preferences and organization settings in the console, and opt out of marketing emails in your profile. For anything else, contact us; we will respond within the time required by law and may need to verify your identity. You may also complain to your local data protection authority.
If your organization gave you access to the Service, it controls its organization's data; we may refer requests about that data to it.
10. Children
The Service is not intended for anyone under 18, and we do not knowingly collect their personal data. If you believe a child has given us personal data, contact us and we will delete it.
11. Changes to this policy
We will post any changes here with a new "Last updated" date. If a change materially affects how we use personal data, we will notify account owners by email or in the console before it takes effect.
12. Contact
[Company legal name]
[Address]
Email: [legal@oramodel.com]