BetaPreside is in beta. Thank you for helping us shape it: tell us what you think at info@presideos.com

Privacy Policy

Last updated: 15 November 2026

Preside is in beta. The Service is still being built and features may change. This policy describes how the Service handles personal data today. We will update it as the Service changes.

1. Introduction

Preside is a board management platform operated by Fluent XP DWC LLC, trading as Preside, a company registered in Dubai World Central, Dubai, United Arab Emirates (“we,” “us” or “our”). Preside provides meeting management, document management, resolutions and voting, document sign-off, board messaging, a regulations library and AI features that help users draft and summarise board material.

This Privacy Policy explains what personal data we collect when you use the Preside website and web application (together, the “Service”), why we collect it, who processes it for us, where it is stored and the rights you have. Section 10 covers people we contact about Preside who do not use it. It applies alongside our Terms of Service and Cookie Policy.

2. Information We Collect

2.1 Account Information

When you register, we collect your name, email address and password. You may also add a job title and phone number. We store your password only as a bcrypt hash; we cannot read it. If you turn on two-factor authentication, we store the secret for your authenticator app and your backup codes. If you add a hardware security key, we store its public key, its identifier, the name you give it and when it was last used. The private key never leaves your key. We do not take payment details: the Service has no payment processor today. If your organisation signs you in through its own identity provider (section 6.3), we receive your name and email address from that provider. We also record whether you gave permission to keep your contact details in our CRM and to email you updates, with the date and the version of the wording (section 3.5).

When we put up a notice in Preside, for example about a change to our Terms or to this policy, we record which notices you have accepted or dismissed, and when. For a notice you accept by choosing Accept or by dismissing it three times, we also record which of the two you did, and a fingerprint (a SHA-256 hash) of the exact text you were shown. We do not record your IP address or browser with it. We keep this record to show which version of our Terms you agreed to. You can see the notices you have accepted that way on your account page. Accepting or dismissing a notice never gives your consent to marketing email or to any other use of your personal data. Section 3.5 explains how you give that consent.

2.2 Board and Meeting Data

Your organisation enters board data into the Service, such as meeting agendas, minutes, attendance, resolutions, votes, action items, committee membership, board member profiles, evaluations, announcements, approval requests (with each approver’s decision, note and comments) and polls of possible meeting times (with each invited member’s yes, no or maybe). Your organisation decides what to enter, relies on its own lawful basis and controls this data. Every member of a board can see that board’s approval requests and polls. A decided approval request cannot be deleted, because it is part of the board’s record. Attendance recorded during a meeting includes the times each person arrived and left, whether an officer recorded it or the person checked in with the meeting’s code, who was present when each resolution of the meeting was put to the vote, and, for each vote, whether the director was recorded as present at the meeting when it was cast and who cast it for a director represented by proxy. An organisation can also make someone without a board seat, such as its chief executive, the owner of an action. We then hold that person’s name, email address and job title, and they see only the actions given to them as an action owner and the text of the resolution behind each.

Meeting guests. A member who schedules a meeting (anyone but an observer) can invite people who have no Preside account, such as counsel or advisers. We store each guest’s name, email address and answer to the invitation, and send them an email invitation with a calendar file and a link to answer. Every member of that board can see the guest list on the meeting page. A guest’s details are deleted when they are taken off the invitation list or the meeting is deleted, and are otherwise kept with the meeting.

Surveys. A member other than an observer can run a survey on their board. We store the questions, each person’s answers and when they answered. Every member of that board can see the results. In a named survey they see who gave each answer. In an anonymous survey they see “Anonymous” and the time of each answer, but we still record who responded, so that each person answers only once. A survey is kept until its creator, or the board’s Chair, Vice Chair or Secretary, deletes it.

Certifications and training. A member other than an observer can record a director’s certification: the director’s name, the certification, the issuing body, the dates and any notes. The Chair, Vice Chair or Secretary can change or delete it. Every member of that board can see the list. 60 days and 14 days before a certification expires, we email the board’s Chair and Secretary (or the Vice Chair, if the board has neither), and the director too when exactly one member of the board has that name. Training requirements record which members have completed them. Each member marks their own training as complete, and the board’s Chair, Vice Chair or Secretary can mark it for a member.

2.3 Documents and Files

You may upload documents, such as board packs, policies and reports. We store the files and related details such as file name, size, upload date, version, comments, notes and sign-off records. We also store, for a document limited to chosen people, the members and committees on its list and who set them. For governing documents, we also store the text read from the file so the Board Advisor can search it. When you open or download a PDF from Documents, we print your name, email address and the date and time on every page of the copy you receive, so that a copy which leaves the board can be traced to whoever opened it. The stored file is not changed. Nothing is printed on other file types, on signing records or the copy with signing record, or on board books printed from your browser.

If you pin notes to a PDF, we store each note’s text, its place on the page, the version it belongs to, who wrote it and when. A note is private unless its author shares it. The Service shows a private note only to the person who wrote it, and a shared note to everyone who can open the paper. The Chair or the Secretary of the board can hide a shared note from everyone else, giving a reason; on a paper limited to chosen people, only one who is on its list can. The note then becomes a private note of its author, kept as it was hidden: while it is hidden, the author can delete it but not change it, and a Chair or Secretary who can show it again sees only where it is on the page, when it was hidden and whether the Chair or the Secretary hid it, not its text. The Chair or the Secretary can show a hidden note to the board again, giving a reason, and it is then shared again as it was. While a note is hidden we store with it when it was hidden, the role of the person who hid it and the reason. We tell the author the reason for a hide, or for showing the note again, in the Service and, unless they turned off document emails, by email; the board’s other Chair, Vice Chair and Secretary are told in the Service that a note on the paper was hidden or shown again, and by whom. The audit log records who hid whose note, or showed it again, on which page and version, why, and a fingerprint of the note (a SHA-256 hash that can confirm a copy of its text), but not the note’s text. A note’s text is not put into exports, the API, search, the AI features, notifications or the audit log. Notes are deleted when their author deletes them, when the paper is deleted, or when we erase the author’s personal data at their organisation on a valid erasure request, which also erases the details of the audit entries recording that one of their notes was hidden or shown again, as section 7.4 sets out. Like the rest of your board data, notes are held on our servers, and section 5.3 applies to them.

2.4 Messages

If you use board messaging, we store the messages you send and their time, and who is in each group conversation and what they have read. Message subjects, message text and group names are encrypted before they are stored, with a key Preside holds. We also keep emails you send to us, such as support requests, in our Microsoft 365 mailbox.

2.5 Activity Log, Sign-in Records and Technical Data

The Service keeps a server-side activity log. It records key changes, such as creating, deleting or changing the status of meetings, documents and resolutions, casting a vote and sending a message. It also records sign-ins, failed sign-ins, sign-outs, each time a PDF, image or text file is opened in the browser (once per person per document in five minutes), downloads and data exports. Each entry records the user and the time, and the IP address and browser user agent of the request that made it. An answer to a meeting invitation that arrives from a calendar is recorded without them, because it was not given in Preside. Some actions are not logged yet.

Entries go to each organisation where you hold an active seat. The Chair, Vice Chair and Secretary of any board in that organisation where you hold or have held a seat can read them, including sign-ins you made while working for another organisation. An entry recording a change to the organisation’s logo can be read on every board in the organisation, because every board’s governance report carries that logo. If a board gives you access as an action owner without a seat, your entries about that board’s action items, and every entry about that access (the invitation, its acceptance and its revocation, whoever made it), go to its organisation, and the board’s Chair, Vice Chair and Secretary can read them, during that access and after it ends. A failed sign-in is recorded against your account even if someone else made the attempt, and the IP address is that of whoever made it.

Simple rules watch the log for bulk downloads and exports, repeated failed sign-ins and, once the organisation has a time zone set, activity during quiet hours. A flag names the person and tells the officers of the boards that person sits on. It is a prompt to look, not a finding, and nothing is decided automatically.

We also keep a security record of every sign-in attempt, including attempts on addresses with no account: a keyed hash of the email address (never the email address itself), your account reference if there is one, the IP address, the browser user agent and the reason an attempt failed. Our hosting provider, Vercel, also keeps request logs for operating and securing the Service. They record each request’s IP address and browser, and are kept for one day.

Each time you sign in, we also keep a record of that sign-in: the IP address and browser it came from, when it started and when it was last used. You can see your sign-ins in Settings and end any of them. The Chair and Vice Chair of any board in your organisation can see, for each member of the organisation, whether they have set up a second factor, how many sign-ins they hold and when they were last active, and on the Enterprise plan they can end a member’s sign-ins. A sign-in expires 30 days after it was last used, and we delete its record from time to time once it is more than a week past that.

Speak Up reports are the exception to the records above. When someone sends a report or follows one up, Preside records no IP address, browser, device or sign-in with it, writes nothing to the activity log, and sends the request without cookies. Our anti-abuse counter holds only a scrambled form of the address, replaced every hour. The hosting provider’s one-day request logs still record the IP address and browser for these requests, as for any other. Recipients are told about a report or a new message at a random time 1 to 6 hours later, so the time of the notice does not match the time it was sent.

We do not use analytics or advertising tools. We do not track which pages you view or how you move through the Service beyond what the activity log and request logs record.

2.6 Connected Calendars

If you connect your Microsoft or Google calendar, we store the access tokens that the connection needs, encrypted. You can instead add a calendar’s private iCal (.ics) address; we store that address, encrypted, and read it only for your busy times. Section 5.2 explains what Preside reads from and writes to your calendar.

You can also turn on a private calendar feed: a secret link that you add to a calendar app. Anyone with the link can read through it the meetings of the boards you sit on, from the past year onwards (title, board name, description, location and video link), and the bookings on your booking page (with each booker’s name, email address and company). Meetings of an organisation that limits access to listed IP addresses are left out. We keep only a hash of the link and when it was last used. You can reset the link at any time, which stops the old one working. The calendar service you add it to holds what it reads under its own terms.

2.7 Cookies and Local Storage

We use only strictly necessary cookies (to keep you signed in, to protect sign-in forms and to remember which board you are working in) and your browser’s local storage (to remember preferences and some in-progress work on your device). We do not use tracking, analytics or advertising cookies. Our Cookie Policy lists each one.

2.8 E-Signatures

When you sign in E-Signatures, we record your name, email address, drawn signature, the time, your IP address, your browser details, the wording you agreed to, and SHA-256 hashes of your signature and of any file. These go on a signing record that the signers and every active member of that board who can open the signed document can read and download (every active member of that board for a request with no document, or once the document is deleted, unless it had been limited to chosen people, when only the signers and that board’s Chair, Vice Chair and Secretary can). When you sign a resolution passed at a meeting, your vote on it as recorded in Preside is printed beside your signature on the resolution and on the signing record. When you sign a written resolution circulated for signature, whether you agreed is recorded and printed there instead. Your organisation controls it as a board record.

2.9 Speak Up Reports

If a board turns on Speak Up, anyone with its link can report a concern, without an account and without giving their name. We store the report’s category and what the reporter writes (a summary, details, when and where it happened, who was involved, whether it is still happening and whether it was reported before); the reporter’s name, email address and phone number, only if they choose to give them; the messages between the reporter and the board; internal notes; the case status; and the outcome. Report text, identity, messages and the outcome are encrypted before they are stored. Section 2.5 explains what we do not record.

The board’s Chair, Vice Chair or Secretary chooses which board members receive reports, and a reporter can leave out anyone the report concerns. Only the recipients of a case can read it, not the rest of the board. Recipients see dates, not times of day. The reporter follows up with a case code and a secret, and sees the case status and the conversation, but never internal notes. Speak Up is part of the Professional plan and above; if a plan ends, the channel takes no new reports, but reporters can still follow up.

Your organisation is the controller of these reports and relies on its own lawful basis, usually a legal duty to provide a reporting channel or its legitimate interest in learning of wrongdoing. We keep cases until your organisation’s data is deleted (section 7.2). We do not delete them on a timer.

2.10 Meeting Scheduler Booking Pages

A member can publish a booking page so that people can book time with them. Anyone with the link sees the member’s display name, the meeting types they offer and the times they are free. Free times take account of the busy times in the member’s connected calendars, but the page shows no details of those events.

When someone books, we store their name, email address, company if given, time zone, answers to the booking questions and any notes, and a private link, kept only as a hash, that lets them reschedule or cancel. We email the booking, with a calendar file, to them and to the host. If the host has let Preside write to a connected calendar, we also add the booking there, with the booker’s details. We send both a reminder a day before. The host and the owner of the meeting type can see the booking.

The member and the organisation they use Preside for decide how bookings are used, and we process them for them. Bookings, including cancelled ones and any reason given, are kept until the host’s account is deleted, or sooner if you ask us.

2.11 API Keys

On the Enterprise plan, a board’s Chair or Secretary can create keys for Preside’s read-only API. We store each key’s name, a short prefix, a hash of the key (never the key itself), its scopes, who created it, when it expires, when it was last used and whether it was revoked. Whoever holds a key can read, for the boards its creator sits on, the meetings, agendas, document details (not the files), action items and resolutions with vote counts that its scopes allow. Your organisation decides who holds its keys, and data read through a key is then in your organisation’s hands.

3. How We Use Your Information

3.1 Providing the Service

We use your information to run your account and the features you use: meetings, documents, resolutions and voting, sign-off, messaging, the activity log and the AI features.

3.2 Security

We use the activity log, sign-in records, IP addresses and request logs to protect accounts, investigate misuse and fix faults.

3.3 Email

We send transactional email that the Service needs, such as welcome and invitation emails, password resets, meeting invitations, requests to vote on resolutions and notices that a document has been shared with you. These are sent through SendGrid. Emails we send from our CRM to platform users are covered in section 3.5. If we send product news or marketing email, we will do so only where the law allows, and each such email will include a way to unsubscribe.

We also send reminders for your organisation: of a meeting, a day before, to the members invited who have not declined; of an action item, the day before it is due and the day after, to its owner, and 7 days after the due date to the board’s Chair (or the Vice Chair if there is no Chair); of a certification about to expire (section 2.2); and of a booking, a day before, to the host and the booker. Reminders to members also appear as a notice in the Service. Members can turn on a weekly digest of their coming meetings, resolutions waiting for their vote and their open actions; it is off unless they turn it on. Every reminder has a link to stop that kind of reminder, and members can change these choices in Settings. When someone without an account stops booking reminders, we keep only a hash of their email address, so that we send them no more. We keep a record of each reminder planned and sent (whom it was for and when, without email addresses), so that none is sent twice.

The Chair, Vice Chair or Secretary of a board can also have the board’s governance report emailed on a schedule to members of that board: each reader’s copy is made for them and attached as a PDF or Excel file, so a copy of the board information in it passes through SendGrid and stays in the reader’s mailbox, and each send is recorded in the activity log with a fingerprint of the file.

3.4 Legal Obligations

We use information where needed to comply with the law, to enforce our Terms of Service and to protect the rights and safety of our users, the public and Preside.

3.5 Your Contact Details in Our CRM

Platform users’ contact details are kept in Preside’s CRM to send service, product and feature updates, with the permission given at join. If you created a Preside account or sit on a board in Preside, our customer records (CRM) hold your name and email address and, once you sit on a board, your job title, your organisation and its industry, your boards and board roles, and your organisation’s plan status. The CRM also shows when you were last active in the Service, taken from the activity log, and we count active users from that log. The CRM is part of the Preside service, hosted as described in section 5.1, and only Preside staff with access to it can see it.

Each record shows which of three kinds of email you allow, and our CRM sends each email only to the people who allow its kind:

  • Service and system notices, such as maintenance, security and changes to your account. Running the Service needs these.
  • Product and feature updates, about changes to Preside and new features.
  • Preside news, only if you ask for it.

When you join a board, by creating an account or accepting an invitation, you tick a box that gives us permission to keep your details in our CRM and to email you service and system notices and product and feature updates. Preside news has its own box, which is optional and never ticked for you. We record the date you gave permission and the version of the wording you saw. If you joined before we added this box, we ask you once, the next time you open your dashboard. If you say no, we keep your contact details only to send service and system notices, and we send you no product and feature updates or news.

Every email from our CRM has an unsubscribe link. If you use it, our CRM stops emailing you altogether. Section 9 explains your other rights over this record.

4. AI Features

Preside’s AI features (the Board Advisor, meeting summaries, board book drafting, governance insights, the Rulebook’s reading of governing documents and the in-app assistant) use Claude, a model provided by Anthropic, through Anthropic’s API.

4.1 What Is Sent

When you use an AI feature, we send Anthropic the content needed to answer your request: your question or instruction, the earlier messages in that conversation (up to ten), and the board content the feature works from (for example, the minutes you ask it to summarise). That content can include the names of people in it, such as meeting attendees and the owners of action items. The Board Advisor also sends, with every question, your organisation’s profile, every rule your board has confirmed (including rules taken from a document marked confidential or archived, with that document’s title and clause) and the passages from your board’s governing documents that best match the question. It does not search the text of documents marked confidential or archived. When the Chair or Secretary asks the Rulebook to read a governing document, we send that document’s text, or the scanned PDF file itself if it is a scan, including a document marked confidential. We do not send other board data. AI features run only when a signed-in user asks for them.

4.2 What Is Stored

Where a feature saves its result, such as a Board Advisor conversation, we store it with your account so you can return to it. Some results, such as the in-app assistant history, are kept only in your browser’s local storage. The Rulebook’s draft rules, each with the passage it quotes, are stored with the board. A board book you save is stored with the board, where every member of that board can open it. A document limited to chosen people cannot go in a board book, and a book naming a document that is limited later is shown only to the people who can open that document. A book saved before 15 November 2026 that did not record its documents counts as naming every document its board held when it was saved.

4.3 Limits

Each user has a limit on AI requests in any 24 hours. When you reach it, AI features pause until some of your requests are more than 24 hours old. On the Free and Foundations plans, only the in-app assistant is included, with a smaller limit.

4.4 No Model Training by Us

We do not train or fine-tune any AI model on your data. We send content to Anthropic only to produce the response you asked for, under Anthropic’s commercial terms for API customers. Anthropic deletes that content within 30 days of receiving it, unless it is flagged under Anthropic’s usage policy, when it may keep it for up to 2 years, or the law requires it to keep it longer.

5. Data Sharing and Sub-processors

We do not sell, rent or trade personal data. We share it only as described below.

5.1 Sub-processors

We use the following providers to run the Service:

  • Vercel: application hosting and file storage (Vercel Blob), United States.
  • Neon: PostgreSQL database, hosted in a single United States region (East US 2, on Microsoft Azure).
  • Anthropic: AI features, through the Claude API. Anthropic is based in the United States and may run a request in any region where it serves Claude.
  • SendGrid (Twilio): sending email, United States.
  • Microsoft (Microsoft 365): our mailbox, info@presideos.com, which receives emails sent to us and replies to the meeting invitations that Preside emails.

We do not use a payment processor or an analytics provider.

New sub-processors. At least 30 days before a new or replacement sub-processor processes your organisation’s data, we will email the Chair, Vice Chair and Secretary of each of its boards, and any data protection contact it has named to us, and update this list. Your organisation can object in writing to info@presideos.com within those 30 days, on reasonable data protection grounds. If we must replace a sub-processor sooner, to keep the Service secure or running or because the provider stops its service, we will give notice as soon as we can, and the same right to object applies. Clause 7 of our Data Processing Agreement sets out these steps and what happens after an objection.

5.2 Connected Calendars: Microsoft and Google

A user may connect their own Microsoft (Outlook or Microsoft 365) or Google calendar. Once it is connected, Preside reads that user’s busy times for the Meeting Scheduler, and creates, updates and cancels events in that calendar through Microsoft Graph or the Google Calendar API. Those events carry the meeting title, description, time and location, and the names and email addresses of the people invited. When asked, the provider adds a Teams or Google Meet link to the event. For the board meeting events it created, Preside reads back the replies of the people invited and any new time or cancellation the user makes there, and applies them to the meeting. Microsoft or Google then holds that data under the user’s own account and the provider’s terms. Nothing is sent to a calendar provider for a user who has not connected a calendar, apart from what a calendar service reads through that user’s own private calendar feed (section 2.6).

Where an organisation’s Microsoft 365 needs an administrator to approve Preside before a calendar can be connected, a user can ask Preside to email the approval link to their IT team. Preside sends that email to the address the user gives, copied to the user, with the user’s name and email address and their organisation’s name. The activity log of the user’s organisation records the request with the address it went to.

Meeting invitations that Preside emails name our mailbox, info@presideos.com, which is hosted on Microsoft 365. When an invitee accepts or declines from their calendar, the reply arrives in that mailbox, and Preside reads it through Microsoft Graph to record the answer on the meeting.

Other integrations with Microsoft 365, Google Workspace and Zoom (files, mail and video calls) are not live and send no data. If we launch one, we will update this policy first, and it will share data only after your organisation turns it on.

5.3 Legal Requirements

We may disclose information where the law, a court order or a binding request from a public authority requires it, or where we believe in good faith that disclosure is necessary to protect someone’s safety or to investigate fraud. Where the law allows, we will tell the affected organisation before we disclose.

5.4 Business Transfers

If Fluent XP DWC LLC, trading as Preside, is involved in a merger, acquisition or sale of assets, personal data may transfer as part of that transaction. We will tell you by email or by a notice in the Service before your data becomes subject to a different privacy policy.

5.5 No Sale of Personal Data

We do not sell personal information, and we do not share it for cross-context behavioural advertising, as those terms are used in the California Consumer Privacy Act (as amended by the California Privacy Rights Act).

6. Data Security

6.1 What We Do

  • Connections to the Service use HTTPS.
  • Passwords are stored as bcrypt hashes.
  • Users can turn on two-factor authentication with an authenticator app (with backup codes) or a hardware security key. On the Enterprise plan, an organisation can require it.
  • Permissions are role-based and scoped to each board, so a user sees only the boards they belong to and only what their role allows. A document can be opened only on the board it was added to, and a meeting paper only on its meeting’s board, by everyone on that board unless it is limited to chosen people. A document limited to chosen people opens only for the members and committees of its board on its list, the person who added it and that board’s Chair, Vice Chair and Secretary; it is left out of everyone else’s lists, counts and search, and it is never returned through the API. A person asked to sign it on a signature request keeps that request even if they are not on its list and, once everyone has signed, its signing record and, for a PDF, the copy with signing record, which holds the document’s pages. Limiting a document later does not recall emails or notices already sent about it.
  • A server-side activity log records key changes, votes, messages sent, sign-ins, failed sign-ins, sign-outs, PDF, image and text files opened in the browser, downloads and exports, with the user and time, and the IP address of the request made in Preside (an answer to a meeting invitation that arrives from a calendar has none). Each organisation’s entries are hash-chained, and the database refuses edits and deletes, apart from a recorded legal erasure of personal details. Anything else needs a maintenance setting, which we use only to remove an organisation that has left. Some actions are not logged yet.

6.2 Certifications and Testing

Preside does not hold a SOC 2 attestation or ISO 27001 certification, and it has not had an independent security audit or penetration test. Our infrastructure providers hold their own certifications, but those cover their services, not Preside. We would rather state this plainly than have it surface during procurement.

6.3 Single Sign-on and Directory Sync

On the Enterprise plan, an organisation’s Chair or Vice Chair can set up single sign-on (SSO) through the organisation’s own identity provider, using OpenID Connect or SAML 2.0, and SCIM provisioning, for email domains the organisation has proved it owns. Both are in early release. When an organisation uses them, its identity provider sends us the name and email address of each person it signs in or provisions. It can create an account, add a seat, update the name and email address of a person on the organisation’s own domains, and end a seat in that organisation.

6.4 Breaches

If we become aware of a breach affecting your personal data, we will tell the affected organisations without undue delay and give them the information they need to meet their own obligations. For the board data we process for an organisation, we tell the Chair, Vice Chair and Secretary of each of its boards, and any data protection contact it has named to us, within 48 hours of becoming aware of the breach at most, as clause 9 of our Data Processing Agreement sets out. To report a security concern, email info@presideos.com.

7. Data Retention

7.1 Active Accounts

We keep your data while your account is active, so your organisation can rely on its records.

7.2 Closing an Account

The Service does not yet have a self-service account deletion function. To close your own account, email info@presideos.com. To delete an organisation’s data, the Chair, Vice Chair or Secretary of one of its boards, or the data protection contact it has named to us, should email info@presideos.com. Before deletion, on the Foundations plan and above, the Chair or Vice Chair can export board data from the Service (CSV and JSON). The Free plan does not include export; anyone can still ask us for their own personal data (section 9.4). We will delete the data within 90 days of a verified request, unless the law requires us to keep it.

7.3 Backups

Deleted data may remain for a limited period in our providers’ backup and recovery systems before it is overwritten.

7.4 Activity Log

An organisation’s log is append-only, because the organisation relies on a complete record. We keep entries and flags until the organisation’s data is deleted under section 7.2. On a valid erasure request we remove the IP address, device and details from your entries and keep each entry, with the action, the time and an internal reference to your account. We also erase the details of the entries other people wrote recording that one of your notes was hidden or shown again (section 2.3), or that the Chair, Vice Chair or Secretary marked your training complete or changed your date of appointment, date of first appointment, term end or independence, and with the details the IP address and device of the person who wrote the entry. Two kinds of entry written before an update we made on 15 November 2026 stay as they are: an entry recording your training marked complete, which carries no reference to your account, and an entry about a hidden note whose wording can be read in more than one way. That erasure is itself logged.

7.5 Sign-in Records

We delete these after 90 days. The record of each sign-in you hold (section 2.5) is deleted from time to time once it is more than a week past its expiry.

7.6 Hosting Request Logs

Our hosting provider keeps request logs, with IP address and browser, for one day. We do not copy them anywhere else.

7.7 Signing Records

We keep these as board records until the organisation’s data is deleted. We do not change a completed record on one signer’s request unless the law requires it, because other signers rely on it. Copies members have downloaded are outside our reach.

7.8 Other Records

Meeting guests, surveys, certifications and training records, polls and undecided approval requests are kept until they are deleted in the Service, or until your organisation’s data is deleted (section 7.2). Decided approval requests and Speak Up cases are kept until your organisation’s data is deleted. Bookings are kept until the host’s account is deleted. Records of reminders hold no email addresses and are kept. A booker’s request to stop reminders is kept, as a hash of their email address, until they ask for reminders again.

8. Where Data Is Stored

Preside data is stored 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 data in the United States. Anthropic is based in the United States and may run a request in any region where it serves Claude. Our Microsoft 365 mailbox is stored where Microsoft keeps our tenant’s data. Preside’s staff work from the United Arab Emirates and other countries. Events in a connected calendar are stored by Microsoft or Google under the user’s own account. If you use the Service from the United Kingdom, the European Economic Area, the GCC or elsewhere, your personal data will be transferred to the United States.

We do not offer a choice of data location. For the data we process for your organisation, clause 8 of our Data Processing Agreement sets out the transfer safeguards, including the EU Standard Contractual Clauses and the UK International Data Transfer Addendum. If your organisation needs data stored in a specific region, contact info@presideos.com before you put personal data into the Service.

9. Your Rights

Depending on where you live, you may have the following rights over your personal data. We will honour these requests wherever we reasonably can, consistent with the law.

9.1 Access

You can ask whether we process your personal data and for a copy of it.

9.2 Correction

You can correct most of your profile in your account settings, or ask us to correct it.

9.3 Erasure

You can ask us to delete your personal data. Some records may need to be kept where the law requires it, or where your organisation must keep its board records. Sections 7.4 and 7.7 explain what erasure does to the activity log and to signing records.

9.4 Portability

You can ask for your data in a structured, machine-readable format, on any plan. From the Foundations plan, members can export board records as CSV, and the Chair or Vice Chair as JSON.

9.5 Restriction and Objection

You can ask us to restrict processing of your data in certain cases, and you can object to processing based on our legitimate interests or for direct marketing. If you object to direct marketing, we will stop.

9.6 California Residents

If you are a California resident, you have the right to know what personal information we collect, use and disclose; to delete it; to correct it; to opt out of its sale or sharing (we do neither); and not to be discriminated against for exercising these rights.

9.7 How to Make a Request

Email info@presideos.com. We will check your identity before acting and will respond within one month, or sooner if the law requires. If your request concerns board data that an organisation controls, we pass it to that organisation within 5 business days and tell you we have done so, because the organisation decides how to answer it. You may also complain to your local data protection authority.

10. People We Contact About Preside

This section is for people we email to introduce Preside, and for people who asked to hear from us, such as by requesting a demo, writing to us or signing up for news.

10.1 What We Hold

Your name, role, organisation, country and business email address; where we found the address and on what date; and a record of the emails we send you, your replies and any request to stop.

10.2 Where We Got It

From you, if you asked to hear from us. Otherwise, from where you or your organisation published your business address in a professional setting, such as your organisation’s website, an annual report, an exchange or regulator filing, or your own professional profile. We record how we got your details and the date we added them.

10.3 Why, and Our Lawful Basis

We use it to tell you about Preside where it may be relevant to your role on a board, and to keep a record so we respect your choices. Our lawful basis is our legitimate interest in offering a governance tool to people whose role is in governance. Where the law of your country requires your consent first, we write to you only if you have given it.

10.4 Where It Is Kept

In our contact records (CRM) inside the Preside service, hosted as described in section 5.1. Our outreach emails are sent from our Microsoft 365 mailbox using Apollo.io (ZenLeads Inc., United States), which holds your name, role, organisation and business email address for us. Apollo also keeps a business contact database under its own privacy policy (apollo.io/privacy). Our other emails go out through SendGrid. If we invite you to connect on LinkedIn, we do it by hand.

10.5 How Long We Keep It

We keep your details for as long as our outreach to you needs them. You can ask us to delete them at any time by writing to info@presideos.com, and we will. After you object or ask us to delete your details, we keep only a minimal suppression entry (your email address and the date) so that we never write to you again.

10.6 Your Right to Object

You can object at any time, and we will stop writing to you. Reply “stop” to any of our emails, use the unsubscribe link in the email, or write to info@presideos.com. You also have the other rights in section 9.

11. Children’s Privacy

The Service is for business use and is not directed at children. Users must be at least 18. We do not knowingly collect personal data from children. If we learn that we have, we will delete it. To report a concern, email info@presideos.com.

12. Changes to This Policy

We will update this policy as the Service changes. When we do, we will change the “Last updated” date above. For material changes, we will also tell account holders by email or by a notice in the Service.

13. Contact Information

For questions or requests about this policy, contact:

Fluent XP DWC LLC, trading as Preside

Dubai World Central, Dubai, United Arab Emirates

Email: info@presideos.com

If you are in the European Economic Area, you can find your data protection authority on the European Data Protection Board website (edpb.europa.eu). In the United Kingdom, the authority is the Information Commissioner’s Office (ico.org.uk).