FUTUREFAULT
Privacy

Privacy notice

FutureFault is open-source software. Whoever operates an instance is responsible for it; this notice describes what the software itself collects.

What is stored

DataWhy
Name and email addressTo identify you, show you to teammates, and send invite and password-reset emails
Password hash (scrypt)To sign you in. The password itself is never stored.
Sessions: creation time, last activity, browser user agentTo keep you signed in and let you review and revoke devices
Workspace content: rehearsals, evidence, artifacts, audit eventsThe service itself
NotificationsTo tell you when a rehearsal finishes

Cookies and local storage

  • ff_session: your sign-in session (HttpOnly).
  • ff_ws: which workspace you are viewing.
  • ff_oauth_state: a ten-minute anti-forgery value during GitLab sign-in.
  • Local storage: your theme choice and whether you hid the getting-started checklist.

There are no analytics, advertising or third-party tracking scripts. Fonts are self-hosted.

Sharing

Data is not sold or shared. If GitLab sign-in is used, FutureFault requests only the read_user scope to learn your name and email. If the operator configures SMTP, email addresses are passed to that mail provider to deliver messages.

Your controls

  • Edit your name in Settings → Profile.
  • Review and revoke sessions in Settings → Security.
  • Export any rehearsal’s complete evidence as JSON from its page.
  • Delete your account in Settings → Danger zone. This removes your profile, sessions and every workspace you solely own, including its rehearsals and artifacts.

Guest sessions are anonymous: no email is collected, and they can view and run rehearsals only in the shared public demo workspace.