Privacy Policy

Last updated: 10 November 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:

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 authorization 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 so we can answer you. A request we dismiss is deleted. If we let you in, your email address and name move to the beta list, which we keep until you’re removed from it. Requests nobody acts on are deleted after 12 months.

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.

Visit counts. Each time the app is opened in a browser tab, our server adds one to a count for that hour, split into computers, phones and tablets (worked out from the description your browser sends of itself, its user agent). Only those three numbers are kept: not your address, your account, the pages you open, the user agent itself or any identifier, and no cookie is set for it. Your address is used only for a moment, in the server’s memory, to stop one address adding too many visits, and is never stored with the counts. To count each tab only once, the app keeps a small marker (futur3.visit) in that tab’s own storage, which the browser deletes when the tab closes. Share links and the read-only board pages aren’t counted. Counts are deleted after 400 days.

Request logs. Like any website, our hosting provider (Google Cloud) keeps standard request logs, including your IP address and your browser’s user agent, for 30 days, for security and to fix faults.

Feedback reports. Feedback is for beta and Subscriber accounts; free accounts don’t have the feedback button, and our servers don’t accept reports from them. 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, only if you tick it (it starts unticked), a copy of the board you’re working on. We open a board copy only to find and fix the fault you reported, and for nothing else. 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.

2. Information we don’t store

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

When you share a board, visitors never get into your Drive. Our server reads the shared board from your Drive with your Drive authorization and sends visitors a copy with your activity log and sharing details taken out. The board file itself is never made public on Drive.

On a public link the board’s comments are taken out too; people you’ve shared the board with by name see its comments, without anyone’s email address.

If you turn on a public link (anyone with the link can view), the pictures, files and 3D models the board uses are set to “anyone with the link can view” on Drive while that link is on, so they load quickly; anyone who has one of those files’ own Drive address could open that file.

When your last public link is switched off or deleted, the app removes that setting. Links for named people never make anything public on Drive.

Our server reads only the link’s board, the files it uses and the boards it links to, and only while the link is on.

Our hosting provider’s network (Google’s) keeps each reply for up to 10 minutes, so after a link is switched off, a copy it already holds can be served for up to 10 minutes. The visitor’s browser keeps a copy so the board opens quickly next time. Share links are made from boards in Google Drive.

5. Comments and visits on share links

Commenting is only for people the owner has shared the board with by name. They sign in with Google or Microsoft, and we receive their account ID, name and email address, checked as verified by Google or Microsoft.

We use the email only to check that they’re on the board’s list and to record, in the owner’s activity log, who commented or visited. A public link is view only: nobody can comment through it.

Visitors can’t write to the owner’s Drive, so a comment (its text, its position, the person’s name, email and the time) waits on our server until the owner’s app collects it into the board file in the owner’s Drive. It’s deleted from our server once collected, when the owner deletes the link, or after 90 days, whichever comes first.

A note that someone opened the link (their name and email if they signed in, otherwise “Visitor”, and the time) is kept the same way. To prevent abuse, we keep a small per-person counter per link for one day.

So that everyone looking at a board sees comments as they’re written, our server briefly keeps, readable only by people on that board’s share links:

A visitor’s comments carry a one-way code made from their Google or Microsoft account, so that only they can edit them; it can’t be turned back into their account.

6. Editing links and live editing

The owner can let named people edit the board. They sign in with Google or Microsoft, and we receive their account ID, name and verified email address, used to check they’re allowed to edit and to note their edits in the owner’s activity log.

Editors can’t reach the owner’s Drive themselves. The changes they save, and any pictures or files they add, go to our server, which writes them straight into the owner’s board file in the owner’s Drive using the owner’s Drive authorization; no copy is kept once written.

Pictures and files editors add stay private on Drive unless a public link is on (section 4).

While people edit together, our server passes between them, so everyone sees the board update live:

No one’s email address is passed on. Each person’s live details are deleted when they leave, and anything left behind (if a connection drops oddly) is cleared within two days.

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). It also keeps a visit marker for each open tab, so a visit is counted only once (section 1); the browser deletes it when the tab closes. 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. The visit marker in section 1 is not a cookie: it’s kept only in the tab’s own storage, never sent to us, and deleted when the tab closes.

10. Service providers

11. Keeping and deleting your data

WhatHow long we keep it
Your sign-in recordUntil you log out, your session expires (180 days at most), or Google or Microsoft tells us the authorization was withdrawn. An expired record is deleted automatically.
Your Google Drive connection (an encrypted authorization token)Until you choose Disconnect for Google Drive, you lose access to Futur3 Board, or 90 days after it was last used. Logging out keeps it, so Drive is connected again the next time you log in with the same Google account.
Your plan record, if you subscribe (Stripe customer ID, status and renewal date)While you’re a subscriber, then as long as we need it for billing, tax and accounting records.
Your boardsWe have no copy, unless you included one in a feedback report.
Feedback reports30 days after you send them: your message, its details, our conversation about it, and its screenshots, voice notes, activity recordings and board copy.
A request to join the beta (your email and name)Until we let you in or dismiss the request, 12 months at most, or sooner if you ask.
Your place on the beta list (your email and name)Until you’re removed from it, or sooner if you ask.
Our log of beta decisions (let in, dismissed or removed: your email address and when)12 months.
Comments and visit notes waiting on our serverUntil the board’s owner’s app collects them, the owner deletes the link, or 90 days, whichever comes first.
Abuse countersA day.
Visit counts (per hour: computers, phones and tablets)400 days.
Request logs kept by our hosting provider (IP address, user agent)30 days.
Live editing and typing detailsUntil each person leaves; anything left behind, two days at most.

Choosing Disconnect for Google Drive revokes the Drive authorization and deletes the token straight away; Disconnect for OneDrive deletes the OneDrive token straight away. Either way, you stay signed in. Log out deletes your sign-in record but keeps your Google Drive connection for your next log-in; choose Disconnect for Google Drive to remove it. You can also remove the app’s access at any time from your Google Account permissions or your Microsoft account’s app permissions.

Your boards are yours: delete them from your Drive, your OneDrive, your computer or your browser whenever you like. Ask us and we’ll delete any plan details we don’t have to keep.

You can delete any feedback 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.

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.