Legal
Privacy Policy
Privacy Policy
Notanda
| Controller | [Legal name] |
| Company number | [Company number] |
| Registered office | [Registered address] |
| Privacy contact | [Privacy email] |
| Data protection lead | [Name, or “not appointed”] |
| EU representative | [Name and address, or “not required”] |
| Effective | [Effective date] |
| Last updated | [Last updated date] |
This notice is given under the UK GDPR and the Data Protection Act 2018. Where the EU GDPR applies, it is also given under that Regulation. It tells you what personal data we process, why, on what basis, who receives it, how long we keep it, and how to use your rights.
“Notanda” is the service at https://notanda.co. “We” and “us” mean [Legal name]. A “workspace” is one customer organisation. “Staff” means a person with an account in a workspace. A “guest” means a person who receives a link and has no account.
1. Summary
Notanda is software for writing meeting minutes, issuing them as a fixed record, and chasing the actions that follow.
- Staff have an account. Guests do not. A guest gets a link to an agenda, to issued minutes, or to an action they own, and sees only that.
- We do not record meetings. There is no audio, no video, and no transcription.
- We do not sell personal data, and we do not use meeting content to train models.
- Issued minutes are not rewritten after they are sent.
- For the content of a workspace, your organisation is the controller and we are its processor. For accounts, billing, the public site, and privacy requests, we are the controller.
2. Scope
This notice covers:
- staff who create or join a workspace
- guests who open a link we send
- people named on a roll, whether or not they have a link
- visitors to the public site, and anyone who writes to us
It does not cover a third-party site you reach from a join link that your organisation pasted into a meeting. That site has its own notice.
3. Controller and processor
Workspace content. Projects, companies, contacts, meetings, agendas, minutes, decisions, actions, comments, files, and guest links are processed by us on the instructions of the customer organisation. That organisation is the controller. We are the processor. Our duties are set out in the data processing terms that form part of the customer agreement.
Our own purposes. We are the controller for:
- your account and sign-in
- billing and tax records
- the public site and, if you consent, analytics
- support correspondence
- privacy requests made to us
- security, abuse prevention, and our own legal compliance
If you are a guest and your question is about what a meeting says, ask the organisation that invited you. If your question is about a link we sent, your account, or this notice, write to [Privacy email].
4. The data we process
We process the following categories. We do not seek special-category data (health, biometrics, religion, trade-union membership, and the like). Do not put it in a meeting unless your organisation has its own lawful basis for doing so.
| Category | What it contains | Source |
|---|---|---|
| Identity and account | Name, email address, account identifier | You, or the person who invited you |
| Authentication | Email-link tokens, session identifiers, sign-in events | Generated when you sign in |
| Workspace | Organisation name, members, roles, minutes brand (logo, header, footer, classification) | The workspace owner or admin |
| Roll | Name, email, phone, job title, company, attendance (present, apologies, absent, in copy) | Staff of the workspace |
| Meeting content | Title, date, time, place, a join link your organisation pastes in, agenda, notes, decisions, actions, owners, deadlines, comments, requests to add an item | Staff, and a guest where a link allows it |
| Issued record | The snapshot and the file sent at issue, and each later version | Generated when minutes are issued |
| Guest access | The token, what it opens, and when it was used | Generated when a link is created |
| Messages | Recipient, template, and the fact of sending for invites, packs, action links, digests, membership mail, and privacy confirmations | Generated when we send |
| Billing | Plan, subscription status, Stripe customer reference, invoices | You, and Stripe |
| Support | The correspondence you send us | You |
| Privacy requests | A hash of the email address, the kind of request, and the time | Generated when you submit the form |
| Device and log | IP address, user agent, and security logs | Generated by your use of the service |
| Analytics | A cookie identifier and pages viewed, only if you accept analytics cookies and a tool is configured | Your browser, if you consent |
We do not buy personal data, and we do not collect it from brokers.
5. Purposes and legal bases
| Purpose | Data | Basis | Detail |
|---|---|---|---|
| Provide the workspace, the meeting, and the issued pack | Account, workspace, roll, meeting content, files | Contract | Performance of our contract with the customer organisation |
| Give a guest the agenda, the minutes, or the action they were sent | Roll, meeting content, guest token | Legitimate interests | Delivering a link the organisation chose to send. See 5.1 |
| Sign-in, session security, and abuse prevention | Email, sessions, logs | Contract; legitimate interests | Contract for staff. Legitimate interests for guests and for security events |
| Send invites, packs, action links, and digests | Name, email, the content needed for that message | Contract; legitimate interests | Contract for staff. Legitimate interests for a guest who was sent the message |
| Take payment and keep accounting records | Billing reference, plan, status, invoices | Contract; legal obligation | Contract for the subscription. Legal obligation for tax and accounting |
| Answer a privacy request | Email, matching roll rows | Legal obligation | UK GDPR Articles 12 to 22, and the equivalent EU provisions |
| Analytics on the public site | Cookie identifier, pages viewed | Consent | Only if you accept, and only if a tool is configured. You can withdraw at any time |
| Establish or defend a claim, or meet a legal duty | The record we are required to keep | Legal obligation; legitimate interests | As the duty or the claim requires |
Where the basis is contract, you must provide the data marked as account and billing if you want an account or a paid plan. Without it we cannot create the account or take payment. Meeting content is provided by the workspace, not by us.
5.1 Legitimate interests
Where we rely on legitimate interests, the interest is running a minutes service safely: delivering a link a guest was sent, keeping an issued edition intact, rate-limiting the privacy form, and securing the service. We have balanced this against your rights. The processing is limited to what that interest needs. You can object. See section 11.
5.2 Consent
Consent is the basis for analytics cookies only. It is not a condition of using Notanda. You can refuse, and you can withdraw, without affecting the rest of the service.
5.3 No automated decisions
We do not make decisions about you by automated means that produce a legal effect or a similarly significant effect. We do not profile you.
6. Issued minutes
When minutes are issued, we store the edition that was sent. A later revision is a new version. Earlier versions remain.
We do not rewrite an issued edition because a draft later changed. We do not rewrite it because a person on the roll asks to be removed. On an erasure request we remove the contact, the attendance rows, and the guest links. The issued snapshot and the file that was sent stay. The organisation that issued the minutes remains responsible for what the document says.
7. Recipients
We share personal data with:
- The workspace. Members see the projects and meetings their role allows. An owner or admin can export a project file. A guest sees only the agenda, the minutes, or the action covered by their link.
- Sub-processors, bound by written terms:
- Supabase — database, authentication, and file storage
- Stripe — subscriptions and payment
- Resend — transactional email
- Plausible or PostHog — site analytics, only if configured and only if you have consented
- Professional advisers, auditors, insurers, and public authorities, where we have a legal duty or where it is necessary to establish, exercise, or defend a claim.
We do not sell personal data. We do not share it for advertising. We do not permit a sub-processor to use Notanda content for its own purposes. A current list of sub-processors is available from [Privacy email].
8. International transfers
We are established in the United Kingdom. Our providers may process data in the United Kingdom, the European Economic Area, or the United States.
Where personal data leaves the UK, we use a transfer tool recognised by UK law: an adequacy regulation, or the International Data Transfer Agreement or Addendum, with the supplier’s standard clauses. Where the EU GDPR applies and data leaves the EEA, we use an adequacy decision or the EU Standard Contractual Clauses. Details of the tool used for each provider are available from [Privacy email].
9. Retention
We keep personal data only for as long as the purpose requires, then delete it or anonymise it.
| Data | Period |
|---|---|
| Account | While the account is open, then deleted. Deletion is blocked while you own a workspace. |
| Workspace content | While the workspace is open. An owner can delete it. Deletion cancels the subscription. |
| Issued minutes and sent files | For the life of the workspace. They are the record. |
| Guest link | Until it is revoked, the meeting is removed, or an erasure request is completed. |
| Billing and tax records | Six years from the end of the accounting period, or longer if the law requires. |
| Privacy-request log | Long enough to enforce the rate limit, then deleted. |
| Security logs | Ninety days, unless needed for an incident. |
| Analytics | As set by the analytics tool, and only while you allow it. |
| Support mail | While the thread is needed, then deleted. |
Backups follow the provider’s cycle. A deleted record may remain in a backup until that cycle ends. It is not restored except to recover the service.
10. Security
Workspaces are isolated. Access to a meeting is by membership or by a guest link. Issued files are served for a limited time. Actions that matter are written to an audit log. Access to production systems is limited to staff who need it.
No method of storage or transmission is perfect. If we become aware of a personal-data breach that is likely to risk your rights, we will notify the ICO without undue delay and, where the risk is high, the people affected. Where we are processor, we will notify the customer organisation without undue delay.
11. Your rights
Subject to the exemptions in the law, you have the right to:
- be informed of this processing
- access your personal data, and receive a copy
- rectify inaccurate data
- erase data, subject to section 6 and to any legal duty to keep it
- restrict processing in the cases the law allows
- port data you provided, where the basis is contract or consent and processing is automated
- object to processing based on legitimate interests, including profiling
- withdraw consent at any time, without affecting processing already carried out
- complain to a supervisory authority
You will not be treated differently for exercising a right. These rights are against the controller. For workspace content, that is your organisation. For the purposes in section 3 where we are controller, it is us.
11.1 Staff
You can see and correct your account in the app. You can leave a workspace. You can delete your account once you no longer own a workspace. An owner can export a project file and can delete the workspace.
11.2 Guests, and anyone on a roll
Use the form at the foot of this page. Choose a copy or erasure. We email a confirmation link to that address. The link is the only thing that acts. It expires after 24 hours. We answer the same way whether or not we hold the address, so the form cannot be used to test whether an address is on a roll.
Erasure removes your contact, your attendance rows, and your guest links. It does not rewrite issued minutes. See section 6.
11.3 Time
We answer within one month of a verified request. If a request is complex or numerous, we may extend by up to two further months, and we will tell you why within the first month. If we refuse, we will explain the exemption and how to complain.
12. Cookies
Essential cookies are required to keep you signed in and to protect the service. They do not require consent.
Analytics cookies run only if you accept them, and only if an analytics tool is configured. Refusing them does not affect the service. You can change your mind by clearing the stored choice in your browser.
The cookies we use are listed in the cookie policy at /cookies.
13. Children
Notanda is not directed at children. We do not knowingly open an account for anyone under 16. If you believe we have, write to [Privacy email] and we will delete it.
14. Changes
We will update the date at the top when this notice changes. If a change is material, we will give workspace owners notice in the app or by email before it takes effect. The previous version is available on request.
15. Contact and complaints
[Legal name]
[Registered address]
[Privacy email]
If you are in the United Kingdom, you can complain to the Information Commissioner’s Office, Wycliffe House, Water Lane, Wilmslow, Cheshire, SK9 5AF, https://ico.org.uk, or by telephone on 0303 123 1113.
If you are in the EEA, you can complain to the supervisory authority of your country of residence, place of work, or the place of the alleged infringement. A list is published by the European Data Protection Board.
We would like the chance to put the matter right first.
Last updated 10/23/2026