Legal
Privacy Policy
Last updated 11 August 2026. This policy explains what ORRJO.ai does with personal data, including the call recordings and transcripts that are central to the service.
The short version
- Your recordings, transcripts and scores belong to your organisation, not to us.
- We do not sell personal data, and we do not use your call content to train AI models.
- Delete a call in the product and it is gone: recording, transcript, score, chat and share links.
- You are responsible for having a lawful basis to record the calls you upload, including telling the other party where the law requires it.
1. Who we are
ORRJO.ai is a sales call coaching platform operated by ORRJO Limited, a company registered in the United Kingdom ("ORRJO", "we", "us"). Contact: privacy@orrjo.com.
Controller and processor roles. For our own website visitors and for the account holders who sign up, we act as a controller. For the call recordings, transcripts and prospect information that a customer puts into the platform, the customer is the controller and we act as their processor, handling that data only on their documented instructions under a data processing agreement. If you are a call participant and want your data removed, contact the organisation that recorded the call; we will support them in responding, and you may also contact us and we will route your request.
2. What we collect
Account data: name, work email, profile image, role, organisation and email domain, authentication identifiers.
Call data: audio recordings you upload or that your connected dialer sends us, the transcripts produced from them, speaker labels, timestamps, and the scores, coaching and summaries we generate. Transcripts contain whatever was said on the call, including personal data about the other participants.
Sales activity data: calls made, meetings booked, deals and their stages, client and prospect names you enter, and metrics synced from your CRM or dialer.
Usage data: pages viewed, features used, device and browser information, IP address, and error diagnostics.
Billing data: plan, seat counts and invoices. Card details go directly to Stripe; we never receive them.
Waitlist and enquiry data: if you join the waitlist or contact us, the name, company, work email and optional mobile number you give us, used to contact you about access and onboarding and delivered to our team by email.
Special category data: we do not ask for it and the service is not designed to process it. Conversations may nonetheless mention health, beliefs or similar. Do not use ORRJO.ai to record conversations where such data is central.
3. Why we process it, and our lawful basis
To provide the service (transcribe, score, coach, store, display): performance of a contract with the account holder, and for call participants, the customer's legitimate interests in training their team, balanced against participants' rights.
To secure the service (authentication, rate limiting, abuse prevention, logging): legitimate interests in keeping the platform safe.
To improve the service (aggregated, de-identified usage statistics): legitimate interests. We do not use customer call content to develop or train AI models.
To send service and digest emails: performance of a contract, with a one click unsubscribe in every digest and a preference switch in Settings.
Marketing emails to prospects: consent, or the soft opt-in where permitted, with opt-out in every message.
Analytics and visitor identification cookies: consent only, gathered through our cookie banner. Section 14 names the tools.
To meet legal obligations: compliance with law, including tax and accounting.
4. Call recording consent, which is your responsibility
This is the most important section for customers. ORRJO.ai processes recordings that you provide. You are the controller of those recordings and you are responsible for having a lawful basis to make them and to share them with us.
Recording laws differ. Several US states, including California, Florida, Illinois, Pennsylvania, Washington and others, require the consent of all parties. Others require only one party. In the UK and EU, recording a call for training purposes generally requires that participants are informed, and a lawful basis under UK/EU GDPR. Australia, Canada and many other jurisdictions have their own rules.
You must: tell participants that the call is being recorded and why, obtain consent where the law requires it, honour any objection, and stop uploading recordings of anyone who has asked not to be recorded. We provide the tooling; we cannot obtain consent on your behalf, and using ORRJO.ai does not make an unlawful recording lawful.
5. How AI is used
Transcription is performed by Deepgram. Scoring, coaching, deal synthesis and the practice-mode prospect are performed using Anthropic's Claude models through their API. Content sent to these providers is processed to return a result and is not used to train their models.
Outputs are generated automatically and can be wrong. Scores are coaching aids, not assessments of a person, and should not be the sole basis for any decision about someone's employment. We do not carry out automated decision making producing legal or similarly significant effects. If your organisation intends to use scores in performance management, tell your team that in advance and keep a human in the loop.
7. Subprocessors
| Provider | Purpose | Region |
|---|---|---|
| Anthropic PBC | AI analysis of call transcripts to produce scores and coachingZero data retention for training; API inputs are not used to train models | United States |
| Deepgram Inc. | Speech to text transcription of call recordingsAudio processed transiently to return a transcript | United States |
| Neon Inc. | Managed Postgres database hostingPrimary store for accounts, transcripts and scores | United States / EU |
| Vercel Inc. | Application hosting, edge delivery and blob storage for recordingsRecordings stored in Vercel Blob | United States / EU |
| Clerk Inc. | Authentication, session management and user profilesHolds email, name and profile image | United States |
| Stripe Inc. | Payment processing and subscription billingWe never see or store full card numbers | United States / EU |
| Resend Inc. | Transactional and digest email delivery | United States |
| Upstash Inc. | Rate limiting and cachingNo call content stored | United States / EU |
| Warmly Inc. | Website visitor identification on orrjo.aiLoads only after cookie consent; no call content | United States |
| Google LLC | Google Analytics website usage statistics on orrjo.aiLoads only after cookie consent; no call content | United States / EU |
We will give notice of new subprocessors so customers can object. Email privacy@orrjo.com to be added to the notification list.
8. International transfers
We are UK based and several subprocessors are in the United States, so personal data is transferred outside the UK and EEA. Those transfers rely on the UK International Data Transfer Addendum and the European Commission's Standard Contractual Clauses, together with additional safeguards such as encryption in transit and at rest. A copy of the relevant transfer mechanism is available on request.
9. How long we keep it
Call recordings, transcripts and scores: kept while your account is active, because playback and coaching history are the product. Delete any call in-product and it is removed immediately, along with its recording, transcript, score, chat and share links.
After account closure: customer content is deleted within 30 days, except where we must keep records to comply with law.
Orphaned recordings (uploads that never produced a scored call): deleted automatically after 7 days.
Public share links: expire after 30 days and can be revoked at any time.
Billing records: retained for 7 years to meet UK tax requirements.
Operational logs: retained for up to 30 days. We deliberately exclude call content from logs.
10. Security
Data is encrypted in transit (TLS) and at rest. Integration credentials are encrypted with AES-256-GCM using a key we hold separately from the database. Access is scoped per workspace and enforced on every request; API keys are stored only as hashes. We apply rate limiting, signed webhooks and least privilege access internally. No system is perfectly secure, and we will notify affected customers and, where required, regulators without undue delay and within 72 hours of becoming aware of a personal data breach.
11. Your rights
Subject to local law, you have the following rights. We respond within one month (UK/EU) or 45 days (US states), and we do not charge or discriminate for exercising them.
- Access. Get a copy of the personal data we hold about you.
- Rectification. Correct data that is inaccurate or incomplete.
- Erasure. Ask us to delete your data. Any call can be deleted in-product, which removes its recording, transcript, score, chat and share links.
- Restriction. Ask us to pause processing while a dispute is resolved.
- Portability. Receive your data in a structured, machine readable format, or have it sent to another provider.
- Objection. Object to processing carried out on the basis of legitimate interests, including any profiling.
- Withdraw consent. Where processing relies on consent, withdraw it at any time without affecting prior lawful processing.
- Automated decisions. Ask for human review of any decision made solely by automated means that has a legal or similarly significant effect. We do not make such decisions.
- Complain. Lodge a complaint with your supervisory authority. In the UK that is the ICO (ico.org.uk); in the EU it is your national authority.
To exercise any right, email privacy@orrjo.com. We may need to verify your identity. An authorised agent may act for you with written permission.
12. United States privacy notices
California (CCPA/CPRA). In the past twelve months we have collected the categories of personal information described in section 2: identifiers, commercial information, internet activity, audio recordings and professional information. We collect it for the business purposes in section 3, from you, your organisation and your connected tools. We do not sell or share personal information, and we do not knowingly process the personal information of anyone under 16. You have rights to know, delete, correct, opt out of sale or sharing, and limit the use of sensitive personal information, plus a right not to be discriminated against. We honour Global Privacy Control signals automatically.
Virginia, Colorado, Connecticut, Utah, Texas, Oregon, Montana and other state laws. Residents of these states have comparable rights of access, deletion, correction, portability and opt-out, and may appeal a refused request by replying to our decision email. We do not process personal data for targeted advertising or profiling with legal effects.
Nevada. We do not sell covered information as defined by Nevada law.
13. Other regions
Canada (PIPEDA): we obtain consent appropriate to the sensitivity of the data and provide access and correction rights.
Brazil (LGPD): you have rights of confirmation, access, correction, anonymisation, portability, deletion and information about sharing.
Australia (Privacy Act, APPs): we handle personal information in line with the Australian Privacy Principles and will notify eligible data breaches.
South Africa (POPIA), Switzerland (revFADP), Japan (APPI) and other regimes: where these apply to your use, we honour the equivalent rights described above.
15. Children
ORRJO.ai is a workplace tool and is not directed at anyone under 16. We do not knowingly collect their data, and will delete it if we learn we have.
16. Changes to this policy
We will post any changes here and update the date at the top. For material changes affecting how we use personal data, we will notify account holders by email before the change takes effect.
17. Contact
Privacy questions, requests and complaints: privacy@orrjo.com. If you are unhappy with our response you may complain to the UK Information Commissioner's Office at ico.org.uk, or to your local supervisory authority.
Note: this policy is a working draft prepared for review. It should be checked by a qualified privacy lawyer, and the company registration details, DPO or representative appointments (UK and EU representatives may be required under Article 27), and the data processing agreement should be confirmed before it is relied on commercially.