Skip to content
How it works Audience Presenters
Join a session Sign in Start presenting Join
How it works Audience Presenters Security Sign in Start presenting

Legal

Privacy policy

What Decklet collects when you present or follow a session, why, who can see it and how long it is kept. Written to match how Decklet actually works.

Last updated 19 November 2026Terms of service

DRAFTThis policy has not been reviewed by a lawyer yet. Text in [brackets] needs FregateLab's details before launch.

On this page

The short version Who we are What we collect How we use it Who can see what Where it is stored How long we keep it Cookies and device storage Security Your rights Children and schools Changes and contact

The short version

  • Your audience can follow a session without an account. We only ask for a display name, and it stays with that session.
  • Slides are encrypted before we store them and only unlocked in the browser of someone in your session.
  • We don't sell data, show ads or use tracking cookies. The only cookie keeps you signed in.
  • The presenter sees who is following, which slide each person is on, their connection quality and their questions.

Who we are

Decklet is made and run by FregateLab ([legal entity name], [registered address]). We are responsible for the personal data described here. For anything about privacy, write to [privacy@fregatelab.com].

When a school, company or event organiser uses Decklet for their own sessions, they decide who to invite and what to present. For questions about a particular session, the presenter is often the best first contact.

What we collect

If you present

  • Your account: your name, email address and password. We never store the password itself, only a one-way hash of it (scrypt).
  • Sign-in: a random login token in a cookie. We store only a fingerprint (SHA-256) of it, and it expires after 30 days or when you sign out.
  • Your decks: the PDF or PowerPoint you upload, turned into slide images and a text layer (used for highlighting). Everything is encrypted before storage. The original upload is deleted as soon as it has been accepted.
  • Your sessions: the session code, when it started and ended, and its settings, such as a passcode and whether viewers may save slides.
  • What you add during a session: replies to questions, slide labels (like "Will be examined"), slide notes and which students you tag.

If you follow a session

  • Your display name, the one you type when you join. If you are signed in to a Decklet account, we use your account name instead.
  • A random viewer ID created on your device, so a reconnecting phone is recognised as the same person. It is not linked to your identity unless you sign in.
  • Live status: which slide you are on, whether you are online, and your connection's round-trip time. This is how the presenter knows if people are falling behind.
  • What you post: questions, the part of a slide you highlighted (and the text in it), and your upvotes.

If you open a study link

  • Where you stopped: the last slide you looked at, kept in your browser so you continue there next time. No display name is asked for, and the presenter doesn't see who is reading or where.
  • If you are signed in, that slide number is also kept with your account, so you continue on another device.

If you save slides

  • A viewer account: name, email and a hash of your password, as above.
  • Your saved items: which slide or part of a slide you saved, the quoted text and your own notes.

Technical data

  • IP addresses, used briefly to limit repeated sign-in, sign-up and join attempts. These counters expire within an hour.
  • An activity log of account actions such as uploading or deleting a deck and starting or ending a session, kept for security and support.
  • Server logs, kept for [log retention period] to keep the service running and investigate faults.

How we use it

  • To run Decklet: deliver slides to the people in your session, keep them in step with the presenter, and show questions and answers.
  • To give presenters a picture of the room and a summary when the session ends.
  • To keep accounts and sessions secure and to stop abuse, such as guessing passcodes.
  • To answer you when you contact us.

We rely on providing the service you asked for as our main reason for handling this data, and on our legitimate interest in keeping Decklet secure. We do not use your content to train models, and we do not sell or rent personal data.

Who can see what

InformationWho sees it
The slidesEveryone in the session. A passcode, if the presenter set one, limits who can join.
Your display name and live statusThe presenter.
Questions, highlights and answersThe presenter and everyone in the session. Questions are shown without the asker's name; answers are shown as from the presenter.
Slide labels and slide notesEveryone in the session.
Who a slide is tagged forThe presenter and the person tagged. Other viewers never receive it.
Your saved slides and notesOnly you, signed in to your account.
Where you stopped in a study linkOnly you, on your device and, if you are signed in, in your account.
Session summariesThe presenter who ran the session.

We share data with service providers only to run Decklet (below), or when the law requires it.

Where it is stored

Decklet runs on servers rented from Contabo in [the UK / the EU: confirm region]. Encrypted slide files are stored and delivered by Dokwe Storage, which only ever holds them encrypted. If your data is transferred out of your country, we rely on [the transfer safeguards your lawyer confirms].

How long we keep it

  • Live session data (who is connected, the current slide, the questions as they arrive) is held in memory for the session and removed when it ends, or after 24 hours at the latest.
  • Session summaries (questions, answers, votes and slide notes) are kept with the presenter's account so they can look back at the session.
  • Decks stay until the presenter deletes them. Deleting a deck removes its slide files and destroys the key that unlocks them, including the pictures in anyone's saved items. Encrypted copies can stay in the storage provider's cache for a while afterwards, but without the key nobody can open them. Saved notes and quotes stay with their owners. Where readers stopped in its study link is deleted with it.
  • Accounts stay until you ask us to delete them. Until self-service deletion is available, write to [privacy@fregatelab.com] and we will delete your account within [30] days.

Cookies and device storage

Decklet sets one cookie, dk_session, only when you sign in. It keeps you signed in for up to 30 days, cannot be read by scripts on the page, and is never shared with anyone else. There are no advertising, analytics or third-party cookies.

The viewer also keeps a few things in your browser's storage so it works the same next time:

  • decklet.vid: your random viewer ID.
  • decklet.name: the display name you last used.
  • decklet.lite and decklet.fitWidth: whether you turned on Lite mode or Fit width.
  • decklet.place.<deck>: the last slide you looked at in a study link.

You can clear these at any time in your browser settings. Decklet still works; it will ask for your name again.

Security

Slides and their text are encrypted before they are stored. The key that unlocks a deck is sent over HTTPS only to people joining its session, and is never stored alongside the slides. Passwords and login tokens are stored only as hashes. All traffic to Decklet is encrypted in transit.

No system is perfectly secure. If we learn of a breach that affects your data, we will tell you and the relevant authority as the law requires.

Your rights

Depending on where you live, including under Nigeria's Data Protection Act 2023 and the GDPR where it applies, you can ask us to:

  • give you a copy of the personal data we hold about you;
  • correct it, or delete it;
  • stop or limit how we use it, or object to a use;
  • send it to you in a format you can take elsewhere.

Write to [privacy@fregatelab.com]. We will reply within [30] days. You can also complain to your data protection authority, such as the Nigeria Data Protection Commission.

Children and schools

Decklet is often used in classrooms. Students can follow a session without an account and without giving more than a display name. Accounts, for presenting or saving slides, are for people aged [minimum age] or older. Schools that use Decklet with younger students are responsible for getting any consent their rules require.

Changes and contact

If we change this policy in a way that matters, we will update the date at the top and tell account holders by email or in the app before the change takes effect.

Questions or requests: [privacy@fregatelab.com], or by post to [registered address].

How it works Security Your saved slides Terms Privacy Presenter sign in Decklet is made by FregateLab