Last updated 16 November 2026
The short version
- Companies use Otter to hire. The candidate data in a workspace belongs to that company; we look after it for them.
- We don't sell personal data and we don't use it for advertising.
- Each company's data is kept separate from every other company's at the database level.
- Otter uses cookies to keep you signed in and to remember how you found us. On our website and careers pages we use Google Analytics to count visits; in the EU, UK and Switzerland only if you accept. No advertising cookies.
- Questions or requests: hey@otter.diy.
Who this covers
Customers and their teams — people who sign up for Otter or are invited to a workspace. For their account data, Otter is the controller.
Candidates — people who apply through a careers page, email a job address, or are added by a recruiter. The hiring company is the controller of candidate data and Otter processes it on its behalf. If you applied to a company, contact that company first about your data; we'll help them respond, and you can also write to us at hey@otter.diy.
What we collect
- Account details: name, work email, password (stored hashed by our auth provider) or Google sign-in, workspace name and role.
- Candidate data that a workspace adds or receives: name, contact details, resume and its parsed contents, application answers, emails, notes, interview details and scorecards.
- Sign-in and security data: when you sign up, sign in (including failed attempts), sign out, reset your password or change your email, we record the time, method, IP address, approximate location derived from that IP address (country, region, city and rough coordinates — never GPS), and your browser, operating system and device type. We use it to protect accounts and stop abuse, and you can see your own history under Login activity in the app. Workspace owners and admins can see this for their workspace's members.
- Product usage data: a short list of milestones in a workspace (for example, a job was created, a candidate was added, an interview was scheduled, an email was sent) and which days the app was used. These records hold workspace and user IDs, not candidate names, email addresses or message contents, and we use them to understand and improve Otter.
- How you found us: the page you first landed on, the referring website and any campaign tags in the link (such as utm_source or a click ID), saved with your account when you sign up.
- An audit log of sensitive actions (exports, deletions, role changes, support access).
- Messages you send us, such as support emails.
How we use it
- To run the service: show your pipeline, deliver and receive emails, parse resumes, schedule interviews and build reports.
- To keep it secure: detect suspicious sign-ins, prevent spam and other abuse of outbound email, investigate problems, and enforce our Terms.
- To improve Otter: understand which features are used and where new customers come from, in aggregate.
- To support you: answer questions and, only when you ask for help, view your workspace as a support session (always recorded in the audit log).
- To tell you about important changes to the service or these policies.
We rely on our contract with customers, our legitimate interest in running a secure service, and legal obligations as our legal bases.
AI features
When a workspace uses AI-assisted features (resume parsing, match-to-role badges, the in-app Assistant, Ask AI in the docs and the AI Job Writer), the text needed for that feature is sent to our AI provider, currently OpenAI, to produce a result. We use OpenAI through its API under its business terms, and under those terms OpenAI doesn't use API data to train its models. AI output is a suggestion; people make every hiring decision.
AI Job Writer. When you draft or rewrite a job description, we send the details you typed (title, level, location, workplace, employment type, team, must-haves, nice-to-haves and notes), your workspace's Job Writer settings (About Us text of up to 1,500 characters, tone and style notes) and, for a rewrite, the current description. No candidate information is sent. Pay and benefits in a draft come only from what you typed. A draft isn't saved until you save the job.
Limits and logs. Each workspace has a daily cap on AI Job Writer requests (60 a day by default, reset at midnight UTC); when it's reached or AI is unavailable, Otter fills in a template instead. The public demo never calls the AI provider. Otter doesn't store Job Writer prompts or responses: it keeps a daily request count per workspace and, if a request fails, a short error line without your text.
Otter for LinkedIn (browser extension)
The optional Otter extension for Chrome and Edge adds the LinkedIn profile you're viewing to your Otter workspace.
- When it reads: only when you click the Otter button, and only the page open in that tab. It doesn't run in the background, visit other pages, scroll or click for you, or use LinkedIn's API.
- What it reads: what's visible to you on that page: name, headline, current role, location, experience, education, the profile link, and an email address only if one is shown.
- What it sends: when the popup opens, the profile link and any shown email go to Otter to check whether this person is already in your workspace. Everything else is sent only when you click Add to Otter, with the job or talent pool you chose and your optional note.
- What Otter stores: a candidate record with those details (source “LinkedIn (extension)”), a note with the experience and education, the application or pool you chose, and an activity entry showing who added them. It's protected like any other candidate in your workspace, and you can edit or delete it there.
- On your computer: only your Otter connection token, in the browser's extension storage. Disconnecting removes it.
- Connection tokens: each is personal to one person in one workspace and limited to what their role allows. Otter stores only a one-way hash, plus when it was created and last used. You can disconnect a browser in Settings → Integrations → LinkedIn Extension, admins can disconnect anyone's, each person can have up to 5, and a connection unused for 90 days is disconnected automatically.
- No tracking: the extension has no analytics, ads or third-party code, and sends data only to app.otter.diy.
A standalone summary for the browser store is at otter.diy/privacy/extension.
Google and Microsoft calendar connections
Each interviewer can choose to connect their own Google Calendar or Microsoft Outlook calendar from My Calendar. It is optional, personal to that person in that workspace, and can be disconnected at any time.
- What Otter accesses: when you are busy (start and end times only, through Google's free/busy service or Microsoft's calendar view), never the titles, descriptions or attendees of your other events; and the interview events Otter itself creates, updates or deletes on your primary calendar. Otter adds those events without inviting anyone, so Google and Microsoft send no emails on its behalf.
- Permissions requested: Google — openid, email, calendar.events and calendar.freebusy. Microsoft — openid, email, offline_access, User.Read and Calendars.ReadWrite.
- How it is used: only to put interviews you are on onto your calendar, keep them in step when they move or are cancelled, and offer candidates booking-link times when you are free. It is not used for advertising, not sold, not used to train AI models, and not read by people at Otter except with your permission to fix a problem, for security, or where the law requires it.
- Storage: access and refresh tokens are encrypted (AES-256-GCM) before they are stored, along with your calendar account's email address and the ids of the events Otter created. Busy times are read when needed and not stored.
- Disconnecting: removes the stored tokens and Otter's record of the events it created (the events themselves stay on your calendar), and for Google also asks Google to revoke Otter's access. You can also remove Otter's access in your Google Account (myaccount.google.com/permissions) or Microsoft account. Deleting a workspace deletes its connections.
Otter's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
Who helps us run Otter
We use a small set of service providers (sub-processors), each only for the purpose listed:
- Supabase (on Amazon Web Services, Asia-Pacific region): database and sign-in.
- Vercel: application hosting, plus cookieless page-speed measurements and website visit counts (no cookies, no cross-site tracking).
- Cloudflare: storage of resumes and email attachments (R2), DNS and inbound email routing.
- Resend and Zoho (ZeptoMail / Zoho CPaaS): sending emails such as invites, sign-in links and recruiter messages.
- OpenAI: AI-assisted features described above.
- Google: optional “Continue with Google” sign-in, optional Google Calendar connections (see above), and Google Analytics for website and careers-page visit statistics (see Cookies).
- Microsoft: optional Outlook calendar connections (see above).
Data may be processed in countries other than yours. Where the law requires it, we use appropriate safeguards for those transfers.
How long we keep it
Customer data is kept while the workspace exists. Owners and admins can export a candidate's data or permanently delete it at any time from the candidate's profile; deleting also removes their resume and email files from storage. When a workspace is deleted, its data is removed from our live systems within 30 days. Sign-in and security records are deleted after 180 days, product usage records after about 13 months, and other security logs are kept for up to 12 months. Email addresses that bounce, report spam or unsubscribe are kept on a do-not-email list so we don't email them again.
Security
Data is encrypted in transit (HTTPS). Every workspace is isolated with row-level security in the database, files are stored in private buckets and only downloaded through signed-in, permission-checked links, and roles control what each teammate can see and do. No system is perfectly secure; if we learn of a breach affecting your data, we'll tell affected customers without undue delay.
Cookies
Otter sets first-party cookies on otter.diy. The signed-in app and the live demo use no analytics cookies. We don't use advertising cookies.
- Sign-in cookies: keep you signed in, and remember a support session or the live-demo session.
- otter_attr (90 days): remembers the first and most recent way you arrived at Otter — campaign tags, referring site and landing page — so that, if you sign up, we know which channel brought you. It holds no name or email address and is never shared with advertisers.
- otter_seen (2 days): lets us count each signed-in user as active at most once a day.
- otter_pending_email (30 minutes): remembers the address we just sent a confirmation email to, so the “check your inbox” page can show it.
Google Analytics. On our website (otter.diy) and public careers pages we use Google Analytics 4 to understand which pages are visited and how people arrive, using Google Consent Mode. It sets the cookies _ga and _ga_<ID> (up to 2 years) to tell visits apart. Advertising features and ad personalisation are switched off. If you're in the EU, the UK or Switzerland, analytics cookies are only set after you choose Accept in the consent bar; until then Google receives only cookieless signals without identifiers. Elsewhere, analytics is on by default. Google processes this data as our service provider; see how Google uses this data.
Changing your mind. Your choice is stored in your browser (otter_consent_v1). To withdraw consent, clear this site's data in your browser settings (the consent bar then asks again) or use your browser's cookie controls, or email hey@otter.diy and we'll help. Withdrawing doesn't affect anything collected before.
Your light/dark preference on our website is stored in your browser, not in a cookie. Recruiter emails sent in bulk include an unsubscribe link; using it stops further bulk emails and new messages from that company through Otter (they can still reply if you write to them).
Your rights
Depending on where you live, you can ask to access, correct, delete or export your personal data, or object to how it's used. Customers can do most of this directly in Otter. For anything else, email hey@otter.diy and we'll respond within 30 days. You can also complain to your local data-protection authority.
Changes
If we change this policy in a meaningful way, we'll update the date above and let workspace owners know by email or in the app.