This Data Processing Agreement forms part of Preside's Terms of Service. It sets out how Preside processes personal data for its customers. Part A is the agreement. Part B covers recordings, transcripts and the meeting room, once they are available. The Annexes describe the processing, the security measures, the sub-processors and what local law asks for.
Part A. The agreement
1. Who this agreement is between, and when it applies
1.1 This Data Processing Agreement ("DPA") is between Fluent XP DWC LLC, trading as Preside, a company registered in Dubai World Central, Dubai, United Arab Emirates ("Preside", "we"), and the organisation that uses the Preside service under Preside's Terms of Service (the "Customer", "you").
1.2 It applies whenever Preside processes Customer Personal Data as the Customer's processor in providing the Service. It forms part of the Terms of Service (the "Terms") and of any order form between us.
1.3 This DPA is incorporated into the Terms by reference. The person who accepts the Terms for the Customer accepts this DPA for the Customer. On request to info@presideos.com, Preside will countersign a copy. For a Customer that accepted the Terms before 14 November 2026, this DPA binds the Customer from the date the updated Terms take effect for it. Preside keeps its own commitments in this DPA for every Customer from 14 November 2026.
1.4 If this DPA conflicts with the Terms on the processing of personal data, this DPA wins. If the Transfer Clauses (clause 8) conflict with this DPA, the Transfer Clauses win.
2. Words used in this DPA
- Data Protection Law means every law on personal data that applies to the processing, including: the EU General Data Protection Regulation 2016/679 ("GDPR"); the UK GDPR and the Data Protection Act 2018; UAE Federal Decree-Law No. 45 of 2021 on the Protection of Personal Data ("UAE PDPL"); DIFC Data Protection Law No. 5 of 2020; the ADGM Data Protection Regulations 2021; and the Saudi Personal Data Protection Law with its Implementing Regulations and Transfer Regulations ("KSA PDPL").
- Customer Personal Data means personal data that the Customer, its users or people it invites put into the Service, or that the Service creates for the Customer, and that Preside processes for the Customer. Annex I describes it. It does not include Preside's own data under clause 3.3.
- Officers means the Chair, Vice Chair and Secretary of each of the Customer's boards on the Service, at the email address on each officer's account, and any data protection contact the Customer names in writing to info@presideos.com.
- Personal Data Breach means a breach of security that leads to the accidental or unlawful destruction, loss, alteration, unauthorised disclosure of, or access to, Customer Personal Data.
- Service means the Preside website and web application described in the Terms.
- Sub-processor means a third party Preside engages to process Customer Personal Data.
- Transfer Clauses means the clauses listed in clause 8.
- Controller, processor, data subject, processing and supervisory authority have the meanings in the Data Protection Law that applies. Where a law uses other words (for example "controlling entity" and "processing entity" in the KSA PDPL, or "Data Office" in the UAE PDPL), the matching term applies.
3. Roles
3.1 The Customer is the controller of Customer Personal Data. Preside is its processor.
3.2 Where the Customer is itself a processor for another controller (for example a company secretarial firm running boards for clients), Preside is the Customer's sub-processor. The Customer passes on that controller's instructions and makes sure this DPA is consistent with them.
3.3 Preside's own data. Preside is an independent controller, under its Privacy Policy and not this DPA, of:
- account and sign-in data (name, email address, password hash, second-factor data, sign-in records);
- its security record of sign-in attempts and its hosting provider's request logs;
- correspondence with Preside;
- each organisation's activity log, for Preside's own use of it to keep the Service secure and to count active users and show each user's last activity date in Preside's CRM;
- the record of AI requests each user makes, used to apply the per-user limit;
- the contact record of platform users in Preside's CRM: name and email address and, once a user sits on a board, job title, organisation and its industry, boards and board roles, and the organisation's plan status. Preside keeps it for every platform user to send service notices, and sends product updates and news only with the permission the user gives.
The Customer agrees that Preside may take the CRM fields above from board membership records for those purposes.
4. Instructions
4.1 Preside processes Customer Personal Data only on the Customer's documented instructions, including for transfers to other countries. The Customer's instructions are: this DPA; the Terms; the Customer's use and settings of the Service, including what its authorised users do in it; and any other instruction the parties agree in writing.
4.2 If a law Preside is subject to requires other processing, Preside will tell the Customer before it does it, unless that law forbids telling on important grounds of public interest.
4.3 Preside will tell the Customer at once if, in its opinion, an instruction breaks Data Protection Law. Preside does not have to give legal advice on the Customer's instructions.
4.4 Preside does not sell Customer Personal Data, does not use it for advertising, and does not train or fine-tune any AI model on it.
4.5 The Customer is responsible for: having a lawful basis for the processing; telling the people concerned, including meeting guests, booking invitees and people named in board papers; deciding whether to put special-category or criminal-offence data into the Service; and making sure its instructions are lawful.
5. People who handle Customer Personal Data
5.1 Preside allows access to Customer Personal Data only to staff and contractors who need it to run, secure or support the Service. Each is bound by a written duty of confidentiality or a statutory one.
5.2 There is no back-office screen in the Service that lets Preside staff open a customer's boards. Access to Customer Personal Data outside the Service is possible only through the hosting and database consoles and the database credentials held in the hosting settings, which only named people hold.
5.3 Preside runs parts of its own work with AI agents. They never read customer content, including Customer Personal Data, in production. They may run counts, schema changes and data migrations that Preside's Chair has authorised, and none of these returns customer content to them. Any look at a customer's data is made only on that customer's written request, by a named member of Preside's staff, not an AI agent, and is recorded.
6. Security
6.1 Preside keeps the technical and organisational measures in Annex II, which are designed to give a level of security appropriate to the risk, as GDPR Article 32 requires.
6.2 Preside may change the measures, but not in a way that lowers the overall protection of Customer Personal Data.
6.3 Annex II also lists what Preside does not have yet. Preside does not hold a SOC 2 attestation or ISO 27001 certification and has not had an independent security audit or penetration test.
7. Sub-processors
7.1 Authorisation. The Customer gives Preside general written authorisation to use the sub-processors listed in Annex III, Part 1.
7.2 Same duties. Preside binds each sub-processor by a written contract with data protection duties that are, in substance, the same as those in this DPA. Preside stays fully liable to the Customer for each sub-processor's performance of those duties.
7.3 Notice of a new or replacement sub-processor. At least 30 days before a new or replacement sub-processor processes Customer Personal Data, Preside will:
- email the Customer's Officers; and
- update the list on its GDPR page.
The notice will say who the sub-processor is, what it will do, which Customer Personal Data it will receive, where it will process it, how any transfer is protected, the date of the change, and whether it serves only an optional feature.
7.4 Change of region. If a listed sub-processor moves Customer Personal Data to another region in the same country, Preside will update the list and email the Officers at the time. That is not a new sub-processor.
7.5 Emergency replacement. If Preside must replace a sub-processor sooner to keep the Service secure or running, or because the sub-processor stops its service, Preside will give notice as soon as it can, and the Customer has the same right to object under clause 7.6.
7.6 Right to object. The Customer may object to a new or replacement sub-processor in writing to info@presideos.com within the 30 days, on reasonable data protection grounds. Then:
- (a) if the sub-processor serves only an optional feature, that feature stays off for the Customer and none of the Customer's data goes to that sub-processor;
- (b) otherwise, Preside will spend up to 30 days in good faith looking for a reasonable alternative, such as not using the sub-processor for the Customer;
- (c) if there is none, the Customer may end the affected service, or its whole subscription, by notice before the change takes effect. No termination fee applies and no further fees are charged. The Customer has the export period in clause 12. Fees already paid are not refunded, except where the law requires a refund.
7.7 Early opt-in. Where a new sub-processor serves only an optional feature, an Officer who has been shown the notice may turn that feature on before the 30 days end. Turning it on is the Customer's specific authorisation for that sub-processor.
7.8 Planned sub-processors. Annex III, Part 2 lists sub-processors Preside plans to add for the meetings programme: LiveKit, for live audio and video in the Preside meeting room, and Microsoft Azure, for storing and transcribing recordings. They are not in use, and no Customer Personal Data goes to them. They will be added only through clause 7.3. The features they serve are off by default and are turned on only by the Customer, so clause 7.6(a) applies to them.
7.9 Services the Customer connects. Services that the Customer or its users connect for themselves are not Preside's sub-processors. Preside exchanges data with them on the instruction of the user or Officer who connects them, and the provider holds that data under its own terms with that user or the Customer. Annex III, Part 3 lists them.
8. Where data is processed, and transfers
8.1 Locations today. The Service stores Customer Personal Data in the eastern United States: the application and files on Vercel in its Washington, D.C. region (iad1), and the database on Neon in Microsoft Azure's East US 2 region (Virginia). Vercel, Neon and SendGrid process it in the United States. Anthropic is based in the United States and may run a request in any region where it serves Claude. Preside's Microsoft 365 mailbox is stored where Microsoft keeps Preside's tenant data. Preside's staff work from the United Arab Emirates and other countries. Preside does not offer a choice of data location.
8.2 Authorisation. The Customer authorises the transfers needed to process Customer Personal Data in the places in Annex III, on the terms of this clause.
8.3 EU. Where Customer Personal Data subject to the GDPR is transferred to Preside, the standard contractual clauses in Commission Implementing Decision (EU) 2021/914 ("EU SCCs") apply and are made part of this DPA as follows:
- Module 2 (controller to processor), or Module 3 (processor to processor) where the Customer is a processor;
- Clause 7 (docking clause) applies;
- Clause 9(a): Option 2, general written authorisation, with the 30-day notice in clause 7.3;
- Clause 11(a): the optional wording is not used;
- Clause 13: the supervisory authority as set out in Clause 13(a), and recorded in Annex I;
- Clause 17: Option 1, the law of Ireland;
- Clause 18(b): the courts of Ireland;
- Annexes I, II and III of the EU SCCs are Annexes I, II and III of this DPA.
Preside applies the EU SCCs to these transfers whether or not Preside is itself subject to the GDPR. If the European Commission adopts standard contractual clauses for importers that are subject to the GDPR, Preside will offer them and update this DPA under clause 17.
8.4 UK. Where Customer Personal Data subject to the UK GDPR is transferred to Preside, the International Data Transfer Addendum to the EU SCCs issued by the Information Commissioner (version B1.0) applies. Table 1 is completed from clause 1 and Annex I; Table 2 is the EU SCCs as set out in clause 8.3; Table 3 is Annexes I to III; in Table 4, neither party may end the Addendum under its Section 19.
8.5 UAE. Transfers of Customer Personal Data subject to the UAE PDPL to countries outside the UAE are made under Article 22 (countries with adequate protection) or Article 23 (other cases) of the UAE PDPL. Where Article 23 allows a transfer under a contract that binds the recipient to protect the data to the PDPL's standard, this DPA and Preside's contracts with its sub-processors are that contract. If the PDPL's Executive Regulations or the UAE Data Office set a required transfer form, Preside will use it and update this DPA under clause 17.
8.6 DIFC and ADGM. Where the Customer is in the DIFC or ADGM, transfers out of the free zone are made under the standard contractual clauses issued by the DIFC Commissioner of Data Protection or the ADGM Office of Data Protection, as they apply, in the version in force at the time of the transfer and completed from the Annexes to this DPA, unless the destination is on that free zone's list of adequate jurisdictions.
8.7 KSA. Transfers of Customer Personal Data subject to the KSA PDPL outside the Kingdom are made under the PDPL and its Transfer Regulations, using the standard contractual clauses issued by SDAIA in the version in force at the time of the transfer. Preside will give the Customer the information it needs for any transfer risk assessment.
8.8 Onward transfers. For each sub-processor in another country, Preside relies on that sub-processor's certification under the EU-US Data Privacy Framework (and its UK Extension) where it holds one, and otherwise on the standard contractual clauses in that sub-processor's data processing terms.
8.9 Representatives. Preside has not appointed a Data Protection Officer or a representative in the EU or the UK. If it appoints one, it will name them on its GDPR page and in Annex I.
8.10 Requests from public authorities. If a public authority asks Preside for Customer Personal Data, Preside will refer it to the Customer where it can, tell the Customer unless the law forbids it, challenge a request it believes unlawful, and disclose only the minimum the law requires.
9. Personal Data Breaches
9.1 Preside will tell the Customer's Officers about a Personal Data Breach without undue delay, and in any event within 48 hours of becoming aware of it, even if not all the facts are known yet. For Customer Personal Data subject to the UAE PDPL, Preside will send the first notice as soon as it becomes aware of the breach, without waiting for the 48-hour limit.
9.2 The first notice will give what Preside knows. Further details follow as Preside learns them. Together, the notices will cover: what happened; the categories and approximate number of people and records concerned; the likely consequences; what Preside has done and will do; and a contact for more information.
9.3 Preside will take reasonable steps to contain the breach, reduce its effects and stop it happening again, and will help the Customer meet its own duties to notify regulators and people.
9.4 Preside will not notify a regulator or the people concerned about a breach of Customer Personal Data on the Customer's behalf, unless the Customer asks or the law requires it.
9.5 Preside keeps a record of every Personal Data Breach and the action taken. A notice under this clause is not an admission of fault.
10. Help with data subjects' rights
10.1 The Service has tools for most requests: users correct their own profiles; from the Foundations plan, members export board records as CSV and the Chair or Vice Chair as JSON; Officers can delete records the Service lets them delete.
10.2 If Preside receives a request from a person about Customer Personal Data, it will pass it to the Officers within 5 business days and will not answer it itself, except to tell the person it has been passed on.
10.3 Where the tools do not cover a request, Preside will help on the Customer's written request, including by exporting data on any plan. On an erasure request that applies to the activity log, Preside removes the IP address, device and details from the person's entries and keeps each entry, as the log is append-only. Preside does not change a completed signing record on one signer's request unless the law requires it, because other signers rely on it.
11. Help with security, impact assessments and regulators
11.1 Preside will give the Customer the information it reasonably needs to meet its duties on security, breach notification, data protection impact assessments and prior consultation with a regulator (GDPR Articles 32 to 36, and the matching duties under other Data Protection Law). That includes this DPA, its Annexes, and answers to security questions.
11.2 Before the recorder is available to any customer, Preside will publish an information pack for the Customer's impact assessment of recording (Part B).
11.3 Preside will cooperate with a supervisory authority that asks about Customer Personal Data.
12. Return and deletion at the end
12.1 When the Service ends for the Customer, the Customer has 30 days to export its data, as the Terms say. During those 30 days, on any plan, Preside will on request deliver the Customer's board data in a standard, machine-readable format.
12.2 Preside will delete Customer Personal Data within 90 days after the export period ends, or within 90 days of a verified deletion request from an authorised Officer if that comes first, unless a law requires Preside to keep it. Anything kept for that reason is protected under this DPA and used only for that purpose.
12.3 Copies in backup and restore systems are overwritten on their own cycle. The database's restore window is 30 days or less. Hosting request logs are kept for one day. Anthropic deletes AI request content within 30 days of receiving it, unless it is flagged under Anthropic's usage policy, when Anthropic may keep it for up to 2 years, or the law requires longer.
12.4 On request, Preside will confirm the deletion in writing and will delete emails about the Customer from its Microsoft 365 mailbox.
12.5 While the Customer uses the Service, the activity log and signing records are kept until the Customer's data is deleted, as the Privacy Policy and GDPR page say.
13. Information and audits
13.1 Information first. On request, Preside will give the Customer the information needed to show it meets this DPA, including:
- this DPA and its Annexes, kept up to date;
- written answers to one security questionnaire a year, within 10 business days;
- the security reports and certifications its hosting providers publish (Vercel and Neon hold their own SOC 2 Type II reports and ISO 27001 certification, which cover them, not Preside);
- the result of the audit-log integrity check, which the Customer's Officers can also see in the Service;
- a summary of Preside's first independent penetration test, once one has been done.
13.2 Audit. If that information is not enough to show compliance, or a supervisory authority requires it, or after a Personal Data Breach, the Customer may audit Preside's compliance with this DPA, itself or through an independent auditor who is not a Preside competitor and is bound by confidentiality.
- The Customer gives 30 days' written notice and a proposed scope.
- Audits take place in business hours, Gulf time, remotely unless an on-site visit is needed.
- No more than once in any 12 months, unless a supervisory authority requires more or after a breach.
- Auditors do not see other customers' data or Preside's security secrets.
- Sub-processors are audited through their own published reports, not on site.
- Each party bears its own costs. Preside's time is free for one working day a year; beyond that, at rates agreed in advance.
14. Records
Preside keeps a written record of the processing it carries out for its customers, as GDPR Article 30(2) and UAE PDPL Article 8 require, and gives it to a supervisory authority or the UAE Data Office on request.
15. Liability
15.1 Each party's liability arising out of or in connection with this DPA is subject to the limits and exclusions in section 12 of the Terms, as if this DPA were part of the Terms. Only an Enterprise order form signed by both parties can set a higher limit for data protection.
15.2 Clause 15.1 applies to claims under the Transfer Clauses only so far as those clauses allow.
15.3 Nothing in this DPA limits a party's liability to data subjects, or any liability that the law does not allow to be limited.
16. How long this DPA lasts
This DPA lasts as long as Preside processes Customer Personal Data, including after the Service ends until deletion under clause 12 is complete.
17. Changes
Preside may update this DPA to reflect a change in Data Protection Law or a regulator's guidance, or a sub-processor change made under clause 7. Preside will give the Officers 30 days' notice of any material change. No change that lowers the protection of Customer Personal Data binds the Customer without its written agreement. Changes to this DPA are made only under this clause, not under section 17 of the Terms.
18. Law and disputes
18.1 This DPA, and any dispute arising out of or in connection with it, including any non-contractual dispute or claim, is governed by the law set out in section 15 of the Terms: the law of the Dubai International Financial Centre ("DIFC law").
18.2 The Courts of the Dubai International Financial Centre (the "DIFC Courts") have exclusive jurisdiction over any dispute arising out of or in connection with this DPA, as section 16 of the Terms sets out. Disputes under this DPA are not referred to arbitration.
18.3 The Transfer Clauses are governed by the law, and disputes under them go to the courts, that they name: for the EU SCCs, Ireland; for the UK Addendum, England and Wales; for the DIFC, ADGM and SDAIA clauses, the law and forum those clauses set. Clauses 18.1 and 18.2 do not limit the Transfer Clauses, or any right that a data subject or a supervisory authority has under them or under Data Protection Law.
19. Notices
The Customer sends notices under this DPA to info@presideos.com. Preside sends notices to the Officers by email.
Part B. Recordings, transcripts and the meeting room
Part B applies only once Preside has told the Customer that the Preside meeting room or recorder is available to it, after the sub-processor notice in clause 7.3 (or an early opt-in under clause 7.7). Neither is available today. Part B sets the terms that will apply to them.
B1. Off by default. Recording is off by default. The Customer turns it on.
B2. Everyone agrees, or nothing is recorded. Recording runs only while everyone present has agreed in Preside. One "no", or one withdrawal, stops it for everyone, and the minutes note the gap. Closed sessions are never recorded. A recording indicator is visible to everyone, all the time it runs.
B3. Lawful basis. The Customer decides its lawful basis for recording, and whether recording is lawful and appropriate where its meetings take place. The agreement each participant gives in Preside is a condition for recording to run. Whether it is also the Customer's lawful basis is for the Customer. It is not automatically consent under GDPR Article 6(1)(a). Some laws, including in the United Arab Emirates and Saudi Arabia, forbid recording a private conversation without the agreement of the people taking part. Preside built the rule in B2, under which nothing is recorded unless everyone present has agreed, to meet that kind of requirement. This is how the feature works, not legal advice to the Customer.
B4. What is processed. Live audio and video in the meeting room; when recording, each participant's own audio track; the transcript; the times each participant joined and left; and each agreement, refusal and withdrawal. Attendance taken from the room counts any join, runs from first join to last leave, and merges drops under 2 minutes.
B5. No voice identification. Speakers are named from their own audio track. Preside does not use voice recognition or voiceprints to identify anyone, and does not use recordings or transcripts to train any AI model.
B6. Where. Live media passes through LiveKit. Recordings are stored and transcribed on Microsoft Azure (Blob Storage and AI Speech) in the East US 2 region, in the United States. Any change follows clause 7. Where a contract requires media to stay in the Middle East, Preside uses LiveKit's Middle East region for that Customer.
B7. Retention. Audio is deleted when the transcript has been checked, or 30 days after the meeting, whichever comes first. A transcript is deleted 30 days after the minutes of that meeting are signed, or 120 days after the meeting, whichever comes first. Only the board's Chair can place a legal hold. The Chair gives a reason, the hold is recorded in the activity log, and it keeps the recording or transcript until the Chair releases it.
B8. Who can read a transcript. The board's Chair and Secretary. A director who attended the meeting may ask to read it; each read is recorded in the activity log and the copy is watermarked. Observers, guests and action owners cannot read transcripts. Preside staff have no access except under clause 5.
B9. AI drafting. AI-drafted minutes start only when the Secretary asks. The transcript and notes are then sent to Anthropic, which is already a listed sub-processor; Annex I, item C8 will say so before the recorder is available. The draft goes to the Secretary or Chair first; members see the minutes only after release.
B10. Fireflies. Fireflies is the board's own connected service, not Preside's sub-processor. Preside imports a Fireflies transcript only after the Secretary confirms it, and never sends the Fireflies bot to a meeting. Once imported, the transcript follows B7 and B8.
B11. Teams, Meet and Zoom. When an Officer turns on import from Microsoft Teams, Google Meet or Zoom, Preside reads attendance and transcripts only for meetings whose links Preside created, using the permissions that Officer grants. The provider is the Customer's, not Preside's sub-processor.
Annex I. Description of the processing
A. Parties. Data exporter and controller: the Customer, contact through its Officers. Data importer and processor: Fluent XP DWC LLC, trading as Preside, Dubai World Central, Dubai, United Arab Emirates; contact info@presideos.com. Preside has not appointed a Data Protection Officer or an EU or UK representative.
B. People whose data is processed.
- Directors, officers and observers of the Customer's boards and committees, and other users the Customer invites.
- Meeting guests invited without a Preside account, such as counsel or advisers.
- People who book time through a member's Meeting Scheduler booking page.
- Signers of e-signature requests.
- People named in board content: executives, employees, shareholders, counterparties and others named in agendas, minutes, papers, resolutions, action items and messages.
- People who make, or are named in, Speak Up reports.
- Once live: action owners outside board membership, and participants in the Preside meeting room and recorder (Part B).
C. Categories of personal data.
- Identity and contact: name, email address, optional job title and phone number, profile photo, board and committee roles; on the Enterprise plan, accounts and seats that the Customer's identity provider creates, updates or ends through single sign-on or SCIM, with the name, email address and directory identifier it sends.
- Board and meeting records: agendas, minutes and their versions, attendance and proxies, meeting guests' names, email addresses and replies, resolutions and votes, action items with owners and due dates, committee membership, member profiles, evaluations (including of a named member), surveys and responses, certifications and training records, announcements, approval requests and sign-off records, polls of possible meeting times and each invited member's answer, board books, governing documents and the text read from them, and the board's confirmed rules.
- Documents and files the Customer uploads, with versions, comments and notes pinned to PDF pages (private or shared, with their author), and, for a document limited to chosen people, the members and committees on its list.
- Board messages and group conversations, who is in each, and what they have read.
- E-signature evidence: name, email address, drawn signature, time, IP address, browser details, the wording agreed, and SHA-256 hashes of the signature and of any file.
- Activity log entries: the user, action and time, and the IP address and browser of a request made in Preside; flags of unusual activity that name a person.
- Scheduling: busy times read from a connected calendar, or from a private iCal address a user adds, which is read only for busy times; calendar events Preside writes (title, description, time, location, invitees' names and email addresses); bookings (invitee name, email address, company, time zone, answers and notes); and the meetings and bookings served through a user's private calendar feed to anyone with its secret link, with the link kept only as a hash and the time it was last used.
- AI requests: the question or instruction, up to ten earlier messages in that conversation, and the board content the feature works from, which can name people. The Board Advisor also sends the organisation's profile, every rule the board has confirmed (including rules taken from a document marked confidential or archived, with its title and clause) and the governing-document passages that best match the question, not searching documents marked confidential or archived. The Rulebook sends the governing document it is asked to read, or the scanned file itself, including one marked confidential. Saved results: Board Advisor conversations and saved meeting summaries (with the user's account), the Rulebook's draft rules and saved board books (with the board).
- Speak Up: report text and category, the reporter's identity if given, case messages and the outcome.
- Reminders: a record of each reminder planned and sent (whom it was for and when, without email addresses), and a hash of the email address of a booker who stops reminders.
- API keys (Enterprise plan): each key's name, prefix, hash, scopes, creator, expiry, last use and revocation.
- Once live: the meeting-room and recording data in Part B, clause B4.
D. Special categories and offence data. Preside does not ask for any. The Customer may put such data into documents, minutes, messages or Speak Up reports (which can contain allegations of wrongdoing). The Customer decides whether to do so. Speak Up content is encrypted in the application and recorded without IP address, browser or device (Annex II).
E. Nature of the processing. Hosting, storage, organisation, retrieval and display; sending email; exchanging calendar data with a connected calendar, and serving a user's private calendar feed; receiving sign-ins and user records from the Customer's identity provider on the Enterprise plan; producing AI responses when a signed-in user asks; activity logging; export; erasure and deletion.
F. Purpose. To provide the Service to the Customer under the Terms, as the Customer sets it up and uses it; to keep the Service secure; and to give the support the Customer asks for.
G. Duration and frequency. Continuous, for the term of the Customer's use of the Service and until deletion under clause 12.
H. Retention during the Service. As the Customer decides, with these fixed rules: activity log entries and signing records are kept until the Customer's data is deleted; hosting request logs are kept for one day; Anthropic keeps AI request content as clause 12.3 says; in-app assistant history stays in the user's browser; recordings and transcripts follow Part B, clause B7.
I. Competent supervisory authority (EU SCCs Clause 13). The authority of the EU Member State where the Customer is established; if it is not established in the EU, the authority of the Member State where its EU representative is; if it has none, the authority of the Member State where the people concerned are.
Annex II. Security measures
These are the measures in place on 14 November 2026.
1. Encryption in transit. Connections to the Service use TLS 1.2 or higher. AI requests go to Anthropic over TLS.
2. Encryption at rest.
- The hosting and database providers encrypt stored data with AES-256.
- Preside also encrypts, in the application and before storage, with AES-256-GCM: board message subjects and text, group conversation names and group messages; Speak Up report text, reporter identity, case messages and outcomes; calendar, file-drive and single sign-on connection secrets; and authenticator (two-factor) secrets. Board message values, file-drive and single sign-on connection secrets and Speak Up case messages and outcomes are each bound to their own record, so a value copied to another row does not open. Production has held no unencrypted board messages.
- Speak Up outcomes and authenticator secrets have been encrypted since that protection reached production in early November 2026. An authenticator secret stored before then is encrypted the next time a code is accepted for it. A Speak Up outcome written before then stays unencrypted until Preside's backfill encrypts it.
- Preside holds these keys. This is encryption at rest, not end-to-end encryption: the Preside service can decrypt these values to show them to authorised users.
- Other board data relies on the providers' encryption. Customer-managed keys are not available.
3. Hashing. Passwords are stored as bcrypt hashes. Two-factor backup codes are stored hashed. API keys and SCIM tokens are stored only as SHA-256 hashes. The security record of sign-in attempts holds a keyed hash of the email address, never the email address itself.
4. Access control.
- Six board roles (Chair, Vice Chair, Secretary, Treasurer, Director and Observer), each with set permissions, scoped to each board. A user sees only the boards they belong to.
- A document opens only on the board it was added to, and a meeting paper only on its meeting's board. A document can be limited to chosen members and committees of its board; it then opens only for them, the person who added it and the board's Chair, Vice Chair and Secretary.
- Board documents are kept in a private file store and served only through a route that checks the signed-in user's membership. Nobody can fetch a document by its storage address. Profile photos are the one public upload, reachable by anyone with the address.
- Draft minutes reach Preside AI, the meeting page and the activity feed only for someone who can edit them. Approved minutes are locked; only the Chair can reopen them, and the approved wording is kept.
- Only a board's Chair appoints or removes its Secretary, and each change is logged.
- The read-only public API (Enterprise) uses keys created by a Chair or Secretary, scoped to the creator's boards, logged and revocable.
5. Authentication.
- Two-factor authentication with an authenticator app (with backup codes) or a hardware security key, on every plan. On the Enterprise plan, an organisation can require it.
- An authenticator code cannot be used twice.
- A member who loses their second factor is reset only by the board Chair, with the Chair's own password, logged, and must enrol again.
- A sign-in expires 30 days after it was last used. Each user can see their sign-ins, with IP address and browser, and end any of them. On the Enterprise plan, the Chair or Vice Chair can end a member's sign-ins, limit how many each member holds, and set an IP allow list for the organisation.
- On the Enterprise plan, the Chair or Vice Chair can set up single sign-on through the organisation's own identity provider (OpenID Connect or SAML 2.0) and SCIM user provisioning, both limited to email domains the organisation has proved it owns. Both are in early release.
6. Activity log and integrity.
- A server-side log records key changes, votes, messages sent (without subject or content), attendance and minutes saves, sign-ins, failed sign-ins, sign-outs, files opened in the browser, downloads and exports, with the user and time, and the IP address and browser of a request made in Preside. Some actions are not logged yet.
- Each organisation's entries form a hash chain, keyed with a secret held outside the database, so someone who can only write to the database cannot rewrite it unnoticed.
- Database triggers refuse edits and deletes of the log, apart from sealing an entry into the chain and a recorded legal erasure of personal details. Any other change or delete needs a maintenance setting, which Preside uses only to remove an organisation that has left, with the approval of Preside's Chair. The hash chain and the daily checkpoint kept outside the database would show a change made that way.
- The chain is checked every day and on request, and a daily checkpoint of every chain head is kept outside the database.
- Rules flag bulk downloads and exports, repeated failed sign-ins and, once the organisation has set its time zone, activity in quiet hours, and alert the board's Chair, Vice Chair and Secretary. A flag is a prompt to look, not a finding.
7. Speak Up. No IP address, browser, device or sign-in is recorded with a report or a follow-up; nothing is written to the activity log; requests are sent without cookies; the anti-abuse counter keeps only a scrambled form of the address, replaced every hour; recipients are told at a random time 1 to 6 hours later. The hosting provider's one-day request logs still record the IP address and browser.
8. AI. AI features run only when a signed-in user asks. Only the content listed in Annex I, item C8, is sent. Preside does not train models on Customer Personal Data. Each user has a limit on AI requests in any 24 hours. Preside's own AI agents do not read customer content in production (clause 5.3).
9. Infrastructure and availability. The Service runs on Vercel and Neon in the eastern United States, replicated across availability zones, with point-in-time restore of the database within its restore window (clause 12.3) and DDoS protection from the hosting platform. A public status page shows measured checks and incident history. No uptime commitment is given.
10. Data minimisation. No analytics, tracking or advertising tools; only strictly necessary cookies; no payment details taken.
11. People and process. No back-office screen opens customer boards (clause 5.2). Keys and secrets are held in the hosting platform's environment settings, not in the code. A written incident response plan was adopted on 2 November 2026.
12. Not in place yet. SOC 2 attestation; ISO 27001 certification; an independent security audit or penetration test; customer-managed keys; a choice of data location; malware scanning of uploaded files; a published uptime commitment.
Annex III. Sub-processors
Part 1. Sub-processors in use (general authorisation)
| Sub-processor | Purpose | Location | Customer Personal Data it receives |
|---|---|---|---|
| Vercel Inc. | Application hosting and file storage (Vercel Blob) | United States | All Customer Personal Data the Service holds or serves; request logs with IP address and browser, kept one day |
| Neon | PostgreSQL database | United States (East US 2, Microsoft Azure) | All database records |
| Anthropic | AI features (Claude API) | United States; Anthropic may run a request in any region where it serves Claude | The AI request content in Annex I, item C8, only when a user asks |
| Twilio Inc. (SendGrid) | Sending email | United States | Recipients' names and email addresses and the content of Service emails, such as invitations, vote requests and notices (message emails go without the message text) |
| Microsoft Corporation (Microsoft 365) | Our mailbox, info@presideos.com: emails sent to us and replies to meeting invitations | Where Microsoft keeps our tenant's data | Emails people send to Preside, and invitees' names, email addresses and replies to meeting invitations |
The GDPR page and section 5.1 of the Privacy Policy list the same sub-processors. Each provider's data processing terms, which form part of its contract with Preside, set its legal entity and its transfer safeguards.
Part 2. Planned sub-processors (not in use; added only under clause 7.3)
| Sub-processor | Purpose | Location | Status |
|---|---|---|---|
| LiveKit (LiveKit Cloud) | Live audio and video for the Preside meeting room | To be named in the notice; Middle East region where a contract requires in-region media | Not in use. No data sent. |
| Microsoft Corporation (Microsoft Azure: Blob Storage and AI Speech) | Storing recordings and transcribing them | United States (East US 2) | Not in use. No data sent. |
Part 3. Services the Customer or its users connect (not Preside's sub-processors)
- Microsoft and Google calendars. When a user connects their own calendar, Preside reads their busy times and creates, updates and cancels events through Microsoft Graph or the Google Calendar API, and reads back replies, new times and cancellations for the board meeting events it created. Nothing goes to a calendar provider for a user who has not connected one, apart from what a calendar service reads through that user's own private calendar feed.
- Identity providers. On the Enterprise plan, the Customer's own identity provider signs its users in through single sign-on and can create and update users and add or end their seats through SCIM, for the email domains the Customer has proved it owns. It is the Customer's provider, not Preside's sub-processor.
- When released: document import from Google Drive and OneDrive or SharePoint; Fireflies transcripts (Part B, clause B10); Teams, Meet and Zoom attendance and transcripts (Part B, clause B11). Each exchanges data only after the Customer or its user turns it on.
Annex IV. Where local law asks for something more
UK. The UK GDPR and Data Protection Act 2018 apply as the GDPR does in this DPA. Transfers use the UK Addendum (clause 8.4). The supervisory authority is the Information Commissioner's Office.
UAE (Federal Decree-Law No. 45 of 2021). As processor, Preside: processes only on the Customer's instructions and this DPA, within the agreed purpose and period; tells the Customer if processing needs to run longer than agreed; deletes or returns the data at the end (clause 12); does nothing that discloses the data except as the law allows; keeps the record in clause 14; and gives the Customer, or the UAE Data Office, the means to show compliance on request. Preside tells the Customer of a breach as soon as it becomes aware (clause 9.1). Transfers follow clause 8.5. The law does not apply to data processed in free zones with their own data protection law (the DIFC and ADGM). If the PDPL's Executive Regulations add duties for processors, Preside will meet them and update this DPA under clause 17.
DIFC (Data Protection Law No. 5 of 2020). Preside has written this DPA to contain the processor terms that Article 24 requires. Where the Commissioner of Data Protection's standard contractual clauses are needed for a transfer, they apply under clause 8.6. Preside will cooperate with the Commissioner.
ADGM (Data Protection Regulations 2021). Preside has written this DPA to contain the processor terms that section 26 requires, including sub-processor flow-down. Where the Office of Data Protection's standard contractual clauses are needed for a transfer, they apply under clause 8.6. Preside will cooperate with the Office of Data Protection.
Kingdom of Saudi Arabia (Personal Data Protection Law). Preside processes only under this DPA and the Customer's instructions, uses sub-processors only under clause 7, and gives the Customer what it needs to verify Preside's compliance. Preside notifies breaches under clause 9 in time for the Customer to notify SDAIA within 72 hours. Transfers outside the Kingdom follow clause 8.7. Preside does not offer data storage in the Kingdom today. If Saudi law comes to require Customer Personal Data to stay in the Kingdom, Preside will tell affected Customers what that means for them.
