Privacy Policy
This policy explains what personal data we collect, how we use it, and your rights under the UK GDPR and the Data Protection Act 2018.
Who we are
Data controller: 99 Developers Ltd, a company registered in England and Wales (company number 17257492), which owns and operates 99 Data Rooms. Contact: support@99datarooms.com.
We are registered with the ICO, the UK's data protection regulator (registration number ZC245763). Our data protection officer is Shahidur Rahman. To reach the DPO, write to support@99datarooms.com marked ‘For the DPO’; it is forwarded to the DPO the same day.
What we collect
- Account data: email, display name, hashed password. When you sign up, the part of your email address after the @ is checked with Cloudflare's and Google's public DNS so we can warn you about a typo; nothing else is sent.
- If you sign in with Microsoft: the name and email address Microsoft holds for you and its identifier for your account. We ask for nothing more: no access to your mailbox, contacts, calendar or files, and we never see your Microsoft password.
- How you found us: only if you agreed to analytics on our website, one of five words for how you first arrived (from an AI assistant, a search engine, an advert, another website, or directly) and the page you landed on. Your browser keeps it for that visit only, and if you create an account during it, by email or through Microsoft, it is saved with your account. For an account created before 17 November 2026, we only ever look at it as totals across all sign-ups: no screen of ours shows it person by person. For an account created from that date, our team may also see it on your account's page, to understand which ways of finding us lead to customers. It is kept with your account until your account is deleted, and you can ask us to remove it sooner by writing to support@99datarooms.com. See the
dr-first-touchentry on our cookies page. - Campaign totals: when someone arrives on our public pages from a link carrying our campaign labels (in one of our emails, adverts or posts), we add one to that campaign's count for the day. The count holds only the labels: never an account, an IP address, a cookie or anything else about who it was. When an account is created from such a link, we also add one to that campaign's count of sign-ups, and we show no count of sign-ups below 5.
- The campaign of the link you followed: if you create an account after following a link from one of our emails, adverts or posts, the link's campaign labels (which channel, campaign and message it was) and the time you arrived are recorded with your account, so we can see which of our campaigns lead to customers. They travel in the web address, so nothing is stored on your device for them, and they need no choice on the cookie card. Our team may see them on your account's page. If the link was one we sent to you personally, we also link your account to our record about you (see People we contact about our service, below).
- Security records: the time and method of each sign-in (password, emailed code, Microsoft, authenticator code), with no IP address and no device details; changes to your security settings, such as adding or removing an authenticator, changing your password, or a reset by a room owner (see below); and each security checkup, with how many authenticators and recovery codes you had at the time. We never record the codes themselves.
- Live editing wait-list, only if you join it: how many people you expect to edit at once and any note you add.
- If you connect an AI assistant: You can connect an AI assistant of your own choosing to rooms you have access to. If you do, we record which assistant you connected, which rooms you allowed it to reach, when you connected it, when it was last used, and when you revoked it. We also keep a log of what it did: the action taken, the room or document it concerned, and the time. That log holds identifiers and counts, never the contents of your documents and never your name.
- If you save a selection for your assistant: you can tick some of your own documents, add an optional note of up to 500 characters, and save that choice for the assistant you have connected. It reaches only what you ticked, and only documents you could already open. We keep the selection for seven days, or until you delete it, and record whether your assistant has collected it. Only you, and your assistant acting under your own connection, can read it.
- Content: documents and data rooms you upload.
- Usage data: IP, user agent, country (from IP), event timestamps.
- Public page requests: on our marketing pages only, the network your request came from (its registered owner and country, for example a broadband provider or an organisation's own network), the page, the referring site's domain, and whether a known AI crawler made the request, and which AI assistant sent you if one did. We do not store the IP address itself and derive no identifier from it. A network that generated very little traffic in the period is never named in our reports; that is a threshold on traffic, not on the size of the organisation. We keep the time of each request to the hour, not the minute. We keep a short list of organisations (never people, sole traders or partnerships) that we already deal with or want to reach, each with the business reason we added it. Our team can see in our internal console when one of their networks read our pages. The daily email to our own team gives counts only and never names a network or an organisation. Each entry on that list is reviewed every six months and deleted after twelve unless we renew it for a stated reason. We never use this record to decide to contact anyone, and never combine it with sign-up, account or prospect records. We can also exclude a network entirely, for example one that in practice serves a single household or small office, and then nothing about requests from it is stored.
- Visit analytics on share links: which documents were opened and when, pages viewed, dwell time, downloads, print attempts, device and the approximate country and city (from the visitor's connection), shown to the person who shared the link.
- Billing data: Paddle collects your payment details directly when you buy (we receive the subscription status, plan and a customer reference). For a company account, we also keep the billing name, billing email and VAT number entered by the people who manage its billing, and send them to Paddle at the company's next purchase so its invoices are made out to the company.
Lawful basis
- Contract: to provide the Service you signed up for.
- Legitimate interests: security, fraud prevention, aggregate cookieless product analytics (GoatCounter's page-view counter, which sets no cookies and is not the consent-based analytics below), and identifying at the level of an organisation's network who reads our public pages. We have carried out a legitimate interests assessment for that last one, and will send you a summary of it on request.
- Legitimate interests: supporting our customers, talking to them about their accounts and our plans, and understanding how the Service is used, through what our team sees of your account (see How we use data). We have carried out a legitimate interests assessment for this too, and will send you a summary of it on request.
- Legitimate interests: recording with your account the campaign labels of the link you followed, and linking a link we sent you personally to the account you create, to understand which of our campaigns lead to customers.
- Consent: session replay and heatmaps on our public marketing pages, through Microsoft Clarity, and page-load measurement there through Cloudflare Web Analytics. These run only if you agree, never inside your account and never on a document somebody shared with you, and you can withdraw at any time from the footer of any page. What they collect, how long Microsoft keeps Clarity's recordings, and the cookies Clarity sets are described on our cookies page.
- Consent: recording how you first arrived at our website (see ‘How you found us’ above). This happens only if you choose Allow on the same banner, and choosing No thanks, or changing your answer later, deletes it from your browser.
- Legal obligation: to comply with applicable law.
If you are invited to someone's data room
The owner of a data room you are invited to as a viewer can reset your two-factor authentication if you lose access to your authenticator, so you can set it up again. They can do this only when every room you can reach belongs to them and you hold no content or signature requests of your own, so a reset can never affect anything another owner controls. The owner never gains access to your account. We email you when it happens and keep a record of it, with who did it and for which room, in your account's security history.
When you open a link someone has shared with you, the person who shared it can see which documents you opened and when, which pages you read and for how long, any downloads or print attempts, and the approximate country and city you opened them from, which we work out from your internet connection without a cookie. They also see the email address you gave if the link asked for one. Documents shown to you carry your email (or "Viewer"), a short visit code and the time on each page.
If we email you because someone invited you to a room, shared a document with you or sent you something to sign, we keep a log of that email and of its delivery (sent, delivered, bounced or marked as spam) for 13 months, so that we can answer questions about whether it arrived.
How we use data
To run the Service, secure it, communicate with you, and improve it. We do not sell your data and do not use it for cross-site advertising.
What our team sees of your account: members of our team can see your name, email address, company and plan, and a record of what happens in your account, such as when you signed up and were last active, how much you and the people in your account use the Service and which features, who joined your account, your billing status and any credits you bought, messages you sent us, and how often the links you shared were opened, as totals. From these we work out which accounts may need our help. We use this to support you, to talk to you about your account and our plans, and to understand how the Service is used. They do not see the names or contents of your rooms and documents, who you shared them with, or what those people did, unless you ask us for help that needs it. We record each time a member of our team opens your account's page or looks up your account by its email address, and keep that record for 24 months.
If you signed up with a work email address at a company, a member of our team may email you about your account, for example to ask whether you need help finishing your setup or with a plan you started to buy, or to tell you about our plans. If you tell us to stop, we will. If you signed up with any other address, we email you about our plans only if you were offered the choice not to receive them when you signed up, and did not take it.
Email you send us: email to any of our addresses is received and kept in our Microsoft 365 mailboxes, in Microsoft's Europe datacentres. Members of our team read and answer it in our own staff console, which reads each email from Microsoft when it is opened and keeps no copy of it. We keep only our own record of handling it, such as who is dealing with it and whether it has been answered, for no more than 13 months after its last change. Email to our legal, privacy and billing addresses is open only to our administrators and the members of our team an administrator adds. We record each reply we send from the console, and each time a member of our team opens an email sent to our legal or privacy address, and keep that record for 24 months.
Authenticated AI access: We use the connection record to enforce the limits you set, so an assistant can never reach a room you did not allow it to, and can never do more than you could do yourself. We use the log for three things: to let you see what your own assistant did, to let a room's owner see what automated access took place in their room, and to investigate an incident if one occurs.
AI features in the Legal Hub
When you ask the drafting assistant, Legal Blinky or Legal Scoring to work on a document, or ask us to read a template of your own, the text goes to Amazon Web Services (Amazon Bedrock), in European Union regions only, to produce the result. AWS does not use it to train any model, and Amazon Bedrock does not store or log it. We also keep Amazon Bedrock's own request logging switched off.
Your content is processed in the UK and EU: our database in London, our AI in AWS EU regions, and our document processing and law library in Ireland. To find and read public pages, such as a law on its official publisher's site, Blinky sends each site the page's address; an official site it searches, such as GOV.UK, may also receive a short search the AI writes from what you asked. Its searches with our web search provider are built from the legal topic, never from your own words. When an answer quotes a page, the quoted passage and details of the page, such as its address and title, are kept with the conversation and deleted with it, if not sooner. Separately, our law library keeps a record of each official page an answer cites, such as its address and version, which holds nothing about you.
If you use credits from an organisation's shared pool, its owners and admins can see, for each month, how many credits you used and how many jobs of each kind, such as answers or drafts. They cannot see what you asked, your documents or what Blinky produced.
We keep what the feature produces for you: a draft, or a review's findings with short quotations from your document. They stay until you delete them, and they are always deleted with the document and with your account. We also keep, in your own words, what you asked for. The request behind each draft Legal Blinky makes (up to 2,000 characters) is kept with that draft, visible only to you, and deleted with it. And if you ask for something our clause library has no template for, the first 500 characters of what you typed are recorded so that our team, and our legal advisers, can consider adding one; you can ask us to delete it, and it goes with your account. We do not keep the model's raw response. When an owner or admin of a company uses AI to find the blanks in one of the company's own templates, we keep only a record of each scan, such as when it ran, who ran it, how many suggestions it made and how much model processing it used; the full responses kept for earlier scans have been reduced to that record. A review is never shown to anyone you share the document with.
We also keep a record of each use of credits: the kind of job, the credits it used, how much model processing it took, and when. The record never contains your document's text. Records tied to a paid credit pack are kept for six years from the end of the financial year, as accounting records. Records of monthly allowances are kept for 24 months after they expire. Separately, we keep a record of each AI model call (the feature, the model, the tokens used and its cost, never your text) for 24 months.
We do this to provide the service you asked for (performing our contract with you). We keep the accounting records because the law requires us to (legal obligation).
An AI review is an aid for a person to check, not a decision about you. Nothing in the Legal Hub makes a decision with legal or similarly significant effects on anyone.
If your organisation's owner switches document AI off, nobody can send the organisation's documents to Legal Scoring or to template reading, no member can use those two features at all, and Legal Blinky reads none of its members' files, including files already in a conversation.
Sharing
We share personal data only with the following categories of recipients:
- Service providers acting on our instructions, each listed with what it can see and where it runs in our sub-processor register: Supabase (our database, sign-in and document storage, in London); Cloudflare (website and application hosting, backups, and the Turnstile check on our sign-in and sign-up forms); Amazon Web Services, which in Ireland extracts the searchable text of every PDF, Word, Excel and PowerPoint file you upload and converts Office files to PDF for preview (AWS Lambda), and in the EU runs the Legal Hub's AI features when you ask for one (Amazon Bedrock: requests enter in Ireland and may be served from other EU regions; see AI features in the Legal Hub below); Resend (the emails we send); Microsoft (Microsoft 365, which holds the email you send to any of our addresses and sends our replies); Instantly (a United States company, which sends our sales emails and holds the name, work email address, company, job title, location and LinkedIn profile of each person we email); and, on our public marketing pages only, GoatCounter, which counts page views without cookies, and, only if you agree, Cloudflare Web Analytics, which measures how quickly our pages load.
- Merchant of Record (Paddle.com Market Limited): our reseller and payment processor. Paddle handles checkout, subscription billing, payment processing, tax compliance, invoicing, and refund handling. For a company account, we send Paddle the company's billing name, billing email and VAT number. See Paddle's Privacy Notice.
- Microsoft Ireland Operations Limited: if, and only if, you agree to the optional session-replay analytics on our public marketing pages. It receives how those pages were used. It never receives your documents, the personal data inside them, your name, your email address or any account identifier, and it is never loaded inside your account or on a document somebody shared with you. Microsoft uses some of what it receives for its own purposes as well, so for this it is an independent controlleralongside us rather than our processor. See our sub-processor register.
- Microsoft, for sign-in: only if you choose to sign in with Microsoft. It provides the sign-in and gives us the details listed above; for that sign-in it is an independent controller under its own privacy terms, not our processor, and we send it neither your documents nor anything from your account.
- Your own AI provider: When you connect an assistant, the contents of the rooms you allowed it to reach are read by that assistant, and therefore by whoever provides it. That is processing you have asked for and directed. It happens under your agreement with that provider, not ours: we do not send anything to them, and we hold no copy of what passes between you. You should check that your own agreement with them covers it, including any retention or zero-retention terms you rely on, because those terms may not extend to a connector like this one.
- Cloudflare: The connector runs on Cloudflare's platform, which processes the connection credential and account identifiers on our behalf. Cloudflare is named in our sub-processor register.
- Professional advisers: legal and accounting advisers where necessary.
- Authorities: where required by law or to protect rights and safety.
Your account data and documents are stored in the UK (London). Backups are held in an EU jurisdiction. Transfers from the UK to the European Economic Area rely on the UK's adequacy regulations. Where a provider can reach data from a country without them, the transfer is covered by the UK International Data Transfer Agreement (IDTA) or by the EU Standard Contractual Clauses with the UK International Data Transfer Addendum. Our sub-processor register names the safeguard for each provider.
Account closure
Closing your account deletes it straight away, with its documents, data rooms, links, analytics and the signature requests you created, and cannot be undone. Encrypted backup copies are deleted within 30 days. If you signed a document someone else sent you, that signed record stays with them.
Retention
Account data is kept while your account is open. When you delete your account it is erased at once: your rooms, documents, share links and their visit records, and your account details go immediately, and the copies of your documents in our encrypted document backups are marked for erasure and removed at the next daily purge rather than left to expire. Copies inside whole-database backups cannot be removed one account at a time; they roll off within 30 days. Some records are kept after deletion, each for the reason given, including: your agreement to our terms and the records of data exports and account deletion, for six years (see below); your other security records, such as changes to your security settings and notices of a two-factor deadline, for 24 months; the record of any complaint or rights request you made to us, for six years; the log of emails we sent you, for 13 months; your signature on a contract somebody else sent you, which stays with that contract because it is the evidence the contract exists (UK GDPR Article 17(3)(e)); and, if you asked us not to email or contact you, your email address on our suppression list, so that the request keeps being honoured.
Messages you send through our contact form are kept for 24 months. A message sent as a complaint is also recorded as a complaint, and that record is kept for six years (see Complaints), so it outlasts the message it arrived as.
A company account's billing details (its billing name, billing email and VAT number) are kept while the company's account exists, and deleted with it.
Visit analytics are retained for 24 months. Backups otherwise expire after 30 days. Public page request records are retained for 90 days, and the organisation-level counts derived from them for 36 months. A small network's name and number are discarded from those counts after 12 months. Entries on our list of organisations are reviewed every six months and deleted after twelve unless renewed for a stated reason. Records about people we contact about our service are kept as described in that section.
Security records: each sign-in and each security checkup is kept for 90 days; changes to your security settings, including a reset by a room owner, for 24 months; your agreement to our terms, and records of data exports and account deletion, for six years, because a claim about how we handled your data can be brought for that long. The record of each time a member of our team opened your account's page or looked up your account by its email address is kept for 24 months. Your choice about setup tips, product news and offers, and each change to it, is kept for six years. The live editing wait-list is kept while your account is open, and you can ask us to remove you from it at any time.
AI access records: We keep the log of AI activity for 12 months. A connection you revoke stays visible to you for 90 days after you revoke it, so you can see that it happened, and is then removed. A connection you leave unused is expired after 180 days, and we email you at 166 days first, so an integration is never cut off without warning. Even a connection in regular use asks you to connect it again 180 days after you first connected it.
Your rights
Access, rectification, erasure, restriction, portability, objection. Contact support@99datarooms.com to exercise rights.
Complaints
If you are unhappy with how we have handled your personal data, please tell us first, so we can put it right. The quickest way is our contact form: choose ‘Complaint’, and we email you straight away with a reference (it looks like C-2026-0042) so you can follow it up. You can complain by email to support@99datarooms.com instead. Either way, we acknowledge your complaint within 30 days at the latest, look into it, and tell you the outcome without undue delay. We keep a record of each complaint and what we did about it for six years. You can also complain to the ICO at any time, at ico.org.uk.
People we contact about our service
If you work at an organisation we think could use 99 Data Rooms, we may keep a record about you so that we can contact you about our service: your name, work email address, phone number, organisation, job title, location and LinkedIn profile, where we came across your details (for example an enquiry you sent us, an introduction, a referral, an event, a business contact database, or your organisation's own website), and notes of our conversations, limited to what is relevant to that conversation.
We rely on our legitimate interests in finding business customers. Unless you contacted us first, we tell you that we hold the record, and where your details came from, in our first message to you, and in any case within a month of recording them.
Our emails to you may contain a link with a code that is personal to you. If you follow it, we record that you did, the page it opened, which of our emails it was in, and the hour, and nothing else. If your browser sends a Do Not Track or Global Privacy Control signal, we record nothing. We use this to decide whether and when to follow up, and we follow up no more than 3 times, by email, by phone or by offering a demonstration. If you create an account after following it, we link your account to our record about you. We never combine any of this with what our site statistics record about the networks visitors come from.
If you are a sole trader or in a partnership, we will not email or message you about our service unless you have asked us to. Before we phone anyone, we check the number against the Telephone Preference Service and Corporate Telephone Preference Service registers within the previous 28 days.
We delete the record 24 months after the last activity on it or, if you become a customer, 24 months after that relationship ends. If we have no way to contact you, or have not told you about the record within a month of recording it, we delete it then. If we email you as part of one of our email campaigns, we delete that record 12 months after we added it, and each record of you following our link 12 months after it was made. If you create an account after following our link, we keep it while your account is open, and delete it when your account is closed or 12 months after we added it, whichever is later.
You have the right to object to this, and we will stop. If you ask us not to contact you, we keep your email address or phone number and the fact that you asked, for as long as your request stands, so that it is honoured even if your details reach us again; you can also ask us to delete the rest of the record. A copy of your data, if you ask for one, includes our notes about you. It also includes when you followed our link, and when our team opened your record. You can tell us in reply to any message from us, on a call we make, or by writing to support@99datarooms.com.
People who report content
If you report a document, a room or a shared link to us, we keep what you tell us, the item you reported, and your contact details if you give them, so that we can look into it and tell you what we did about it.
- Why we may use it: where the Online Safety Act 2023 requires us to act on a report, we rely on a legal obligation. Beyond what that Act requires, we rely on our legitimate interests in keeping the Service safe and lawful. Where a report says a crime has been committed, we also rely on a condition in Schedule 1 to the Data Protection Act 2018 for handling information about alleged offences.
- Who reported it is withheld: we withhold from the owner of the reported content who reported it, including from a subject access request, unless the law requires us to disclose it. The Data Protection Act 2018 (Schedule 2, paragraph 16) lets us withhold information that would identify another person.
- If you hold the account that was reported: when a report leads us to act on your content, we tell you only the kind of source it came from, such as a report from another person or from an authority, and not who made it unless the law requires us to disclose that. Where the law requires us not to tell you at all, we tell you nothing.
- How long we keep it: a reporter's contact details for 6 months after we close the report, and the record of the case for 3 years with the reporter's identity removed.
Children
The Service is not directed at children. You must be at least 18 years old to create an account, and we do not knowingly collect personal data from anyone under 18. If you believe a child has provided us with personal data, contact support@99datarooms.com and we will delete it.
Objecting to legitimate-interest processing
Where we rely on legitimate interests, including the network-level record described above, you have the right to object at any time. You do not have to write to us to do it: if your browser sends a Global Privacy Control or Do Not Track signal, we record nothing about the request. That signal is how an objection to this record works: the record keeps no identifier for you, neither your IP address nor any identifier derived from it, so we could not pick out the rows about one person if you wrote to us. You can write to support@99datarooms.com to object to any other processing we base on legitimate interests.
Security
TLS in transit, encryption at rest, row-level security, short-lived signed URLs, rate limiting. Details on our security page.
Cookies
See our cookie policy.