Privacy Policy

Last updated: 9 October 2026

Futur3 Board ("the app", "we") is a visual board app that runs in your web browser at board.futur3.app, and can be installed from there. It's operated by Futur3. This policy explains what information the app uses, where it goes, and the choices you have. The short version: your boards are stored in your own Google Drive or OneDrive, or on your own device, not on our servers.

See it as a board: Your information: Where it's stored maps out what lives on your computer, on our server and at Google, for free and paid users. What happens when you… walks through each thing you do in the app and where it's stored. Both are read-only boards, with no sign-in needed.

1. Information we store

You sign in with Google or with Microsoft. Either one shares only your account details with the app, not your files. Our server stores the following so that you stay signed in, and, once you connect Google Drive or OneDrive, connected to it:

• Your account ID (from Google or Microsoft), email address, name and, for Google accounts, the link to your profile picture.
• Only if you connect Google Drive or OneDrive: an authorisation token that lets the app reach its own files in that storage on your behalf. It's encrypted (AES-256-GCM) before it's stored.
• When the session was created and when it expires (180 days at most).
• Your plan (Free or Subscriber). If you subscribe, also your Stripe customer ID, your subscription's status and the date it renews or ends.

This record is linked to a random session cookie in your browser. If your account isn't on the beta access list, you aren't signed in, we don't store anything and we cancel the authorisation immediately. If you tick I want access to the beta (or choose Ask to join the beta), we keep your email address and name with your request until we invite you or you ask us to remove it.

Updates and news. If you tick I want to be notified of Futur3 Board updates and news when you first sign in, we keep your email address, name and the date you joined, and send you occasional news about the app. Every news email has an unsubscribe link, and you can switch it off at any time from your account menu (Updates and news emails). Signing in again never signs you back up. We'll send these emails through an email service provider, named in section 10 before the first one goes out.

If you make share links, we also keep one small record per link: your account ID, the Drive ID of the board it shows, whether the link, its comments and editing are switched on, and a count of the saves made through it. Nothing else, not even the link's label, which stays in your board file. This lets a link be switched off for good, from any device. Deleting a link deletes its record.

Feedback reports. The feedback button (the bullhorn under the zoom level) sends a report only when you press Send, and only what you see listed in it: your message, your account's email and plan, the app version, your browser, screen and window size, the app's last few errors and warnings and your last few actions in the app (these are kept in the page's memory, never sent on their own), and anything you add: screenshots, a voice note (with the transcript your browser makes of it; in Chrome, the browser sends the audio to Google to write it), an activity recording, and, if you leave it ticked, a copy of the board you're working on. An activity recording is not a video: it's a record of what the app showed and what you clicked and typed while it was running, so we can replay it; password fields are never recorded. Reports are kept on our servers (Google Cloud) for the Futur3 team to read, together with our notes on fixing it, and an AI assistant working for us may read them to find the fault. When we fix or answer one, the app tells you the next time you open it. Under Sent in the feedback dialog you can follow each report you sent: its status, and a conversation with us about it (your messages and ours are kept with the report). The app also keeps a full copy of each report you send, in a Feedback reports folder wherever your boards are saved (your Google Drive, your OneDrive, a folder on your computer or this browser); that copy is yours, and we never see it. If you've sent feedback and are signed in, while Futur3 Board is open in front the app tells our feedback server every 30 seconds that you're here, and when you're typing a reply, so our team can see you're available; only the latest time is kept (never what you type before you send it), and it's deleted within a month. Reports also include the link to your account's profile picture, kept with the report. The Local app sends nothing: it saves the report as a file for you to email.

2. Information we don't store

• Your boards, images and files. They're saved to a folder in your own Google Drive or OneDrive, to a folder on your computer that you choose, or, in browsers that can't save to folders (such as Safari, Firefox, iPhone and iPad), in that browser's own private storage on your device. Your browser sends them to Google or Microsoft directly; they don't pass through or stay on our servers. The exceptions are boards opened through a share link (section 4), comments from people you share a board with (section 5) and changes made through an editing link (section 6), all brief, and what you choose to put in a feedback report (section 1).
• Your password. Sign-in is handled entirely by Google or Microsoft.
• Your card details. Payments are handled entirely by Stripe (section 10).
• Analytics, advertising or tracking data. The app has no analytics, ads or third-party trackers. The errors and actions a feedback report can include stay in the page until you send a report, and are forgotten when you close it.

3. Google Drive and OneDrive access

For Google Drive, the app asks for Google's drive.file permission, the narrowest Drive permission available. It only lets the app see and change files the app itself created (your boards and the images and files you add to them). It can't list, read or change anything else in your Drive. Signing in with Google asks only for your basic profile (name, email and picture) to show who's signed in; Drive is asked for separately, when you connect it.

For OneDrive, the app asks for Microsoft's Files.ReadWrite.AppFolder permission, which only reaches the app's own folder in your OneDrive (Apps › Futur3 Board). It can't see anything else in your OneDrive. Signing in with Microsoft asks only for your basic profile (name and email); OneDrive is asked for separately, when you connect it.

Futur3 Board's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. We use Google and Microsoft user data only to provide the app's features to you. We don't sell it, use it for advertising, use it to train AI models, or let people read it, except where you ask us to (for example, for support), where it's needed for security, or where the law requires it.

4. Share links

If you share a board, the app gives the board file (and the images and files it uses, and optionally its linked boards) Google Drive's "anyone with the link can view" setting. Anyone with the link can then view those files. When you switch off your last link, or stop sharing, the app removes that setting. Share links are made from boards in Google Drive.

Visitors don't download from your Drive themselves. Our server reads the shared board and its images from your Drive with your Drive authorisation and sends them on, with images made smaller for the screen. Our hosting provider's content delivery network (Google's) keeps each reply for up to 10 minutes, so many visitors don't each make your Drive send it again. The server only reads the link's board, the images and files it shares and the boards it links to, and only while the link is on; after a link is switched off, a copy already held by the network can be served for up to 10 minutes. Nothing else is kept on our side. The visitor's browser keeps a copy so the board opens quickly next time.

5. Comments and visits on share links

A board's owner can let people with a share link add comments. To comment, a visitor signs in with Google. We receive the visitor's Google account ID and name (not their email address), which are used to label the comment and to limit how many comments one person can send.

Visitors can't write to the owner's Drive, so a visitor's comment (its text, its position on the board, the visitor's name and the time) is held on our server until the owner next opens the board. The owner's app then copies it into the board file in the owner's Drive, and we delete it from our server. The same applies to a note that someone opened the link (their name if they signed in, otherwise "Visitor", and the time), which the owner can choose to log. We also keep a small counter per visitor per link to prevent abuse; it's deleted along with the link.

So that everyone looking at a board sees comments as they're written, a note that someone is typing (where the comment will go, their name and a colour; never what they're typing) and a copy of each comment or edit just posted are kept on our server briefly, readable only by people on that board's share links. The typing note is deleted when the comment is posted or cancelled, or after two minutes. A posted copy is deleted after a day; the comment itself is kept in the owner's board file. A visitor's comments carry a one-way code made from their Google account, so that only they can edit them; it can't be turned back into their account.

6. Editing links and live editing

A board's owner can let people with a share link edit the board. To edit, a visitor signs in with Google, and we receive their Google account ID and name (not their email address).

Editors can't reach the owner's Drive themselves, so the changes they save (and any pictures or files they add) are sent to our server, which writes them straight into the owner's board file in the owner's Drive, using the owner's Drive authorisation. Our server doesn't keep a copy once the change is written. The board's activity log notes that it was edited through a share link.

While a board with editing switched on is open, each person on it (the owner and any editors) shares their name, a colour, where their pointer is on the board and which items they've selected, so the others can see who's there and what they're working on. Our server holds this for about a minute after each person's last update, then deletes it.

7. Comments and activity logs inside boards

Comments, replies and the board's activity log (who opened, commented on, shared or, if switched on, edited the board, and when) are saved inside the board file, wherever you keep it, like the rest of the board. Anyone who can open the board file can read them. The board's creator can switch logging off or delete the log at any time from Board activity in the app.

8. Data kept on your device

The app keeps some data in your own browser: your preferences (such as your default save location), the folder you picked on your computer, a backup copy of the board you have open (so work isn't lost if the tab closes), copies of board pictures (so they don't download again), and, if you install the app, its own files so it opens without a connection. To let you keep working offline, it also remembers the account you last signed in with (for up to 30 days) and your plan (for up to 14 days). If you keep boards in the browser's own storage, they're kept there too. All of this stays on your device. Clearing your browser's site data removes it, including boards kept in the browser, so download a backup first (File › This browser › Back up all boards).

9. Cookies

The app uses one cookie, __session, which keeps you signed in. It's essential, contains only a random identifier, and isn't used for tracking.

10. Service providers

• Google provides Google sign-in, Google Drive, and the cloud hosting, server and database the app runs on, in the United States.
• Microsoft provides Microsoft sign-in and OneDrive, if you use them.
• Stripe handles subscription payments. Your card details and billing address go to Stripe, not to us: we never see or store your card number. Stripe tells us your customer ID, whether your subscription is active, and when it renews or ends. Stripe's own privacy policy covers what it keeps.
• Google Fonts serves the fonts on this website and in the app.
• jsDelivr and cdnjs serve some of the app's tools (the PDF, SVG, zip, GIF and cutting tools, the 3D viewer). Your browser loads those files from cdn.jsdelivr.net or cdnjs.cloudflare.com when you use them; nothing of yours is sent.
• Iconify serves the icons in the gallery's Icons tab. When you search there, the words you type go to api.iconify.design, and your browser loads the icons from there; nothing else of yours is sent.
• Link cards and maps. When you put a website's link in an embed node, our server reads that page once (its title, description, logo and picture) to make the card; nothing is kept. Your browser then loads the logo and picture from that site. For a Google Maps link, the place's address comes from OpenStreetMap (nominatim.openstreetmap.org), which gets the place's map position, and the map itself loads from Google.
• Unsplash serves the photos in the example boards. When you open an example, your browser loads those photos from images.unsplash.com.

11. Keeping and deleting your data

Your sign-in record is kept until you log out, your session expires (180 days at most), or Google or Microsoft tells us the authorisation was withdrawn. Choosing Disconnect for Google Drive revokes the Drive authorisation and deletes the token straight away; Disconnect for OneDrive deletes the OneDrive token straight away. Either way, you stay signed in. Log out deletes the whole record. You can also remove the app's access at any time from your Google Account permissions or your Microsoft account's app permissions.

If you subscribe, your plan record (Stripe customer ID, status and renewal date) is kept while you're a subscriber and afterwards for as long as we need it for billing, tax and accounting records. Ask us and we'll delete what we don't have to keep.

Your boards are yours: delete them from your Drive, your OneDrive, your computer or your browser whenever you like. We have no copy to delete, unless you included one in a feedback report.

Feedback reports, with their screenshots, voice notes, recordings, board copies and conversation, are deleted automatically 90 days after we close or release them, and after a year at most. You can delete any report you sent while signed in yourself, at once, from the Sent tab; your own copy in your Feedback reports folder stays until you delete it. For a report sent while not signed in, ask us at support@futur3.app.

A request to join the beta (your email and name) is kept until we invite you, or deleted sooner if you ask.

Visitors' comments and visits waiting on our server are deleted as soon as the board's owner opens the board, or when the owner deletes the link. Live editing details are deleted about a minute after each person leaves. If you commented on or edited someone's board and want your contribution removed afterwards, ask the board's owner; it lives in their file.

12. Security

All connections use HTTPS. Stored Google and Microsoft tokens are encrypted, the encryption key is kept separately in Google Secret Manager, and the database can't be read from browsers. Payment messages from Stripe are checked against Stripe's signature before we act on them.

13. Children

The app isn't directed at children under 13, and we don't knowingly collect information from them.

14. Your rights

Depending on where you live, you may have the right to access, correct or delete the information we hold about you, or to object to how it's used. Contact us and we'll help. Logging out in the app deletes your sign-in record. California residents have these rights under the California Consumer Privacy Act; we don't sell or share personal information.

15. Changes

If we change this policy, we'll update the date at the top. For significant changes, we'll let you know in the app.

16. Contact

Questions about privacy: privacy@futur3.app. Help with the app: support@futur3.app.