Privacy Policy

In short

Luseed works without an account. Without one, nothing you write leaves your device.
If you sign in, your journal is copied to our server so it can sync between your devices. That includes private entries, and they stay private.
Other people only see dreams you switch to Share Publicly and names you add to the shared dream sign catalog, and only after moderation.
Your audio recordings, transcripts and night cue and reality check settings stay on your device unless you send them somewhere yourself.
No ads, no analytics, no tracking. We never sell or rent your information.
You can export your journal, and delete your account and everything on our server, at any time.

Who is responsible

Luseed (the apps for iPhone, iPad and Android, the web app at luseed.org/app and this website) is operated by Intercode inc., a company based in Quebec, Canada (“Intercode”, “we”, “us”). Intercode is responsible for the personal information described here.

Person in charge of the protection of personal information

As required by Quebec’s Act respecting the protection of personal information in the private sector (“Law 25”), Intercode has a person in charge of the protection of personal information. You can reach them for any question, request or complaint about your personal information:

Pierre-Verthume Larivière, person in charge of the protection of personal information, Intercode inc.
29 Du Marché, Roxton Falls, Québec J0H 1E0, Canada
info@intercode.ca

What stays on your device

Your journal lives in a database on your device (in the web app, in your browser’s storage). If you never sign in, nothing you write is sent to us.

Even when you are signed in, these stay on your device and are never sent to Luseed:

Audio recordings: your dream clips and the voice recordings in your night cues. When you are signed in, only a short list of what was recorded syncs (each clip’s identifier, when it was recorded and how long it is) so your other devices can show that a clip exists. The sound itself is never uploaded.
Transcripts of your recordings. If you choose Add to dream text, those words become part of the entry and sync like the rest of its text.
Reality check and night cue settings, reminders and schedules. Notifications are scheduled on your device; we don’t use a push notification service.
The API key of a Whisper server you set up, kept in your device’s secure storage.

Speech-to-text runs on your device, using your phone’s own recognizer in on-device mode or a Whisper model you download. Reading the Library aloud also happens on your device.

When you choose to send something elsewhere

A Whisper server. If you set up A Whisper server for transcription (the app offers presets for OpenAI and Groq, or your own computer), the recording you transcribe goes straight from your device to that service, under its own terms and privacy policy. It does not pass through Luseed and we never receive it.
Share recording and Or your own AI open your device’s share sheet. The recording goes to the app you pick.
Export Data (in Settings) saves your journal to a file that you control.

What we receive when you sign in

Signing in is optional. You only need it to sync between devices and to use the shared spaces. You can sign in with Apple, with Google, or with an email address and password. Sign-in itself is handled by Firebase Authentication, a Google service (see Other services involved). Once Firebase confirms who you are, our server at luseed.org creates your Luseed account and stores the following.

Your account

Your email address, and whether it is verified. If you use Apple’s Hide My Email, this is the relay address Apple gives us.
Your display name, if your sign-in provides one or you set one.
When your account was created, and its standing in the shared spaces (see Safety and moderation records).
The link to your sign-in: the Firebase identifier, the email address it reported, and when it was first and last used.
A session for each device you sign in on: a random access token, a generic device type (such as “iOS Device”, “Android Device” or “Web Browser”, never your device’s name or identifiers), and when it was created and last used.

Our server never receives your password and does not store your profile photo.

Your synced journal

Everything in your journal syncs, including entries you keep private:

Entries: the title and text of every language version you wrote, the date, the type (dream, intention, reality check mark or other), the lucid and nightmare flags, tags, the dream signs linked to it, your sharing choices (Share Publicly, Post Anonymously), and when it was created, changed or deleted.
Reality check marks: when you did a check, your answer, and which tool you used.
Dream signs: name, description, language, order, and which shared catalog signs they are linked to.
The list of audio clips described above, never the audio.
For anything you asked to share, its moderation status and, if it was held or refused, the reason.

Private means private. Other users never see your private entries or signs. They are on our server only so they can sync. The people at Intercode who run Luseed can technically access the database; we only look at private content when it is needed to keep the service working or fix a problem, when you ask us to, or when the law requires it.

What becomes public

Nothing is public by default.

Shared dreams. An entry is shown to other people only if you turn on Share Publicly, and only once it passes moderation. Other signed-in Luseed users can then read its title and text, date, tags, lucid and nightmare flags and language, under your display name, or with no author name if you turn on Post Anonymously. Turning sharing off, deleting the entry or deleting your account takes it out of the shared feed.
The shared feed is only available to people signed in to Luseed. It is not published on the open web.
Shared dream signs. Your own dream signs are always private. If you add a name or a description to the shared catalog, other users can see it, with no author attached. Linking your own signs to shared ones only adds to anonymous counts (for example, how many dreamers share a sign). Your own sign’s words and your name are never shown.
Your display name appears next to dreams you share without Post Anonymously, and in the blocked list of anyone who blocks you.

Anonymous means anonymous. A dream shared with Post Anonymously reaches other readers with no name and no account number, so it cannot be tied to you or to your other dreams. Readers can report it; they cannot block its author, since nothing says who that is.

Safety and moderation records

To keep the shared spaces free of spam and abuse, the server keeps:

What the sharing gate needs: whether your email is verified, how old your account is, how many entries you have written (the count only), and a trust level. A new author’s first shared dream is reviewed by a person; after it is approved, later ones publish straight away.
The result of automatic checks. Before anything is shared, our server checks its words for signs of spam: links, email addresses, phone numbers, messaging handles, advertising words, repeated or duplicated text and the like. Depending on the result, it is published, held for a person to review, or refused, and the app shows you why. Only content you ask to share is checked. For private entries we keep only a fingerprint (a hash) of the text, used to tell whether the words changed if you share the entry later.
Reports. If you report a dream, a sign or an account, we keep who reported what, the reason you picked, and any note you add. The person you report is not told who reported them.
Blocks: who you blocked and when.
A moderation log: what was held, approved, refused, reported or suspended, when, and the signals or short reason behind it. It does not contain the text of your entries.
If an account is suspended, when and why.

The automatic checks are decisions made by software. You can always ask a person to review one, and ask what information it was based on, by writing to info@intercode.ca.

Technical data and logs

IP addresses. Like any website, our server sees the IP address of each request. To slow down abuse of sign-in, it counts attempts per IP address, stored as a shortened one-way hash rather than the address itself. Other limits count requests per account. All of these counters are deleted after 24 hours.
Web server logs. Our web server records standard access logs: IP address, date and time, the page or API address requested, and the browser or app type. These logs, and the server’s error log, are kept for 14 days and then deleted.
Sync log. A technical log of sync activity: account number, entry numbers, counts and times, never titles or text. It is emptied automatically when it reaches a fixed size.
Server errors are logged so we can fix them.

Other services involved

Firebase Authentication (Google LLC) handles every way of signing in. It processes your email address, your sign-in method, your password if you use one (Firebase stores it as a hash), the name and profile details your Google or Apple account provides, and sign-in details such as IP address, device type and times. It also sends verification and password-reset emails. Firebase processes this on Google’s servers in the United States. See Privacy and Security in Firebase and Google’s Privacy Policy.
Sign in with Apple (Apple Inc.) and Google Sign-In (Google LLC). If you choose one, you sign in on Apple’s or Google’s own screen, under their terms. When you delete your account, the app asks Apple to revoke Luseed’s access to your Apple ID.
Our server host, Hosting.com, whose server in Toronto, Canada, stores your account and synced journal.
Email. Messages sent through the contact form, and the copy sent back to you, are delivered by Twilio SendGrid (United States). They reach our mailbox, which is hosted by Microsoft 365.
Downloads. Some optional files come straight from other sites: speech-recognition (Whisper) models from Hugging Face (huggingface.co), the Library narrator’s voice and a voice-detection model from GitHub (github.com), and the list of available models from luseed.org. These are ordinary downloads. The site sees your IP address and app type, as with any web request; nothing from your account or journal is sent.
Google’s content servers. The sign-in screen shows Google’s logo, loaded from www.gstatic.com. The web app also loads part of its display engine from www.gstatic.com, and may load fonts from fonts.gstatic.com, as Flutter web apps do by default. These requests carry your IP address and browser details.
Services you choose: a Whisper server you set up, or an app you share a recording with. They work under their own terms and privacy policies.
Apple and Google distribute the apps under their own terms and may give us aggregated statistics, such as download counts and crash reports, under their own privacy policies.

What we never do

No advertising, no ad networks, no analytics or tracking tools, and no tracking you across other apps and websites. The only third-party software in the app is Firebase Authentication and Google Sign-In.
We don’t sell, rent or trade your personal information, and we don’t “share” it for targeted advertising in the sense of California law.
We don’t use your dreams to train AI models, and we don’t build profiles about you.
We don’t collect your location, contacts, photos or health records. The microphone is only used while you record, and recordings stay on your device.

Why we use your information

We use personal information only for these purposes, and collect only what they need:

To run your account and sync your journal between your devices. This is the service you ask for; for users in the EU and UK, the legal basis is the performance of our contract with you.
To show what you choose to share in the shared spaces. The basis is your consent, given when you turn sharing on. You can withdraw it at any time by turning sharing off.
To keep Luseed safe: moderation, reports, blocks, rate limits and logs. The basis is our legitimate interest, and yours, in a service free of spam and abuse, and our legal obligations.
To answer you when you contact us.
To meet legal obligations, and to protect our rights if we must.

Dreams can reveal sensitive things, such as your health, sexuality or beliefs. We treat everything in your journal as sensitive. We use it only to store and sync it for you, and to publish what you explicitly choose to share. By turning on sync, you give your express consent to that. You can withdraw it at any time by deleting your account. We will not use your information for any other purpose without asking you first, unless the law allows or requires it.

How long we keep it

Information	How long
Account, sign-in link, synced journal and dream signs	Until you delete your account, or we close it. It is then deleted from our database straight away.
Entries and signs you delete in the app	The server keeps a “deleted” marker so your other devices remove them too. 30 days after an entry is deleted, like the app’s trash, its titles, text, tags and links are erased from the server; only the marker remains, with no content.
Sessions	Until you sign out on that device, 90 days after sign-in, or until you delete your account, whichever comes first.
Shared dreams	Until you turn sharing off, delete the entry or your account, or we remove them.
Names you add to the shared dream sign catalog	As long as the catalog exists, with no author attached. They stay when the account that added them is deleted: they belong to the shared catalog, and nothing in them points back to that account.
Reports you file	90 days after the report is resolved, or until you delete your account.
Reports about your content or account	90 days after the report is resolved. If you delete your account first, the report is no longer linked to you; the reported content is deleted with your account.
Blocks	Until the block is lifted, or either account is deleted.
Moderation log	Kept as a lasting record of moderation decisions. When you delete your account, the entries about you are no longer linked to your account.
Rate-limit counters	24 hours.
Sync log	Until it is emptied automatically, when it reaches a fixed size.
Web server logs	14 days.
Messages to support	The email stays in our support mailbox for as long as we need it to help you, and no longer than two years after the conversation ends. The server’s log line for each message (its reference number and topic) is kept 14 days, like the other logs.
Backups	We copy the database before changing its structure. Each copy is kept on the same server, readable only by its administrator, and deleted after 30 days; data you delete is gone from the copies by then.
Your sign-in record at Firebase	Deleted with your account: the app deletes it when you delete your account there, and we delete it when you ask us by email.

If the law requires us to keep something longer, for example to deal with a legal claim, we keep only that, only for as long as required, and then destroy it.

Where your information is stored

Your synced journal and account are stored on the luseed.org server, rented from Hosting.com in Toronto, Canada. Sign-in is processed by Firebase Authentication on Google’s servers in the United States. Your information may therefore be stored and processed outside Quebec and outside Canada, where local laws, including laws that let authorities access data, apply.

Before personal information is communicated outside Quebec, Quebec law requires us to assess whether it will be adequately protected there, and to put a written agreement in place. We do so for each service named in this policy: Firebase is covered by Google’s data processing terms, our server by Hosting.com’s service agreement, and email delivery by Twilio SendGrid’s. For users in the EU and UK, transfers to the United States rely on the safeguards Google offers for them, such as standard contractual clauses.

Your rights and choices

Wherever you live, you can:

See your information. Ask what we hold about you and get a copy.
Correct it. Edit your display name and your journal in the app, and ask us to correct anything else.
Delete it. Delete entries in the app, or your whole account under Account › Delete Account. See Delete your account.
Stop it being shown. Turn off Share Publicly, or ask us to stop publishing information about you or to remove it from the shared spaces.
Withdraw consent. Turn off sharing, sign out, or delete your account. Everything keeps working on your device.
Take it with you. Settings › Export Data saves your journal as a file (JSON). You can also ask us for the information on our server in a structured, commonly used format.
Ask a person to review an automatic decision, such as a dream that was refused or held.
Object to a use of your information, or ask us to restrict it.

To make a request, write to info@intercode.ca, preferably from the email address of your Luseed account. We may need to confirm that the account is yours. It is free, and we answer within 30 days.

Complaints

If you are not satisfied with our answer, you can complain to a privacy regulator:

In Quebec: the Commission d’accès à l’information du Québec.
Elsewhere in Canada: the Office of the Privacy Commissioner of Canada.
In the EU or the UK: your local data protection authority, or the UK Information Commissioner’s Office.

California residents

You have the right to know what personal information we collect and how we use it, to have it corrected or deleted, and not to be treated differently for using these rights. We do not sell or share personal information, as those words are defined in California law, and we do not use sensitive personal information to infer things about you.

Security and incidents

Connections between the apps and luseed.org are encrypted (HTTPS).
Firebase checks your identity; our server never sees your password. Access tokens are random and expire after 90 days.
Access to the server and the administration tools is limited to the people who run Luseed, and requires them to sign in.

No system is perfectly secure. If a confidentiality incident affects your personal information, we take reasonable steps to reduce the risk of harm and prevent it from happening again, and we record it in our register of incidents. If it presents a risk of serious injury, we notify the Commission d’accès à l’information and the people affected promptly, as Quebec law requires, and other regulators where their laws require it.

Found a vulnerability? Please tell us privately; see Security & privacy on the support page.

Children

Luseed is meant for people aged 16 and over. It is not directed to children, and we do not knowingly collect personal information from anyone under 16. If we learn that someone under 16 has created an account, we delete the account and its data from our server. The journal on their device is not affected. If you think a child has created an account, please write to info@intercode.ca.

This website and the web app

No tracking cookies. luseed.org sets no cookies for ordinary visits and uses no analytics.
The contact form on the support page sends us your email address, the topic, your device and version if you give them, and your message, by email, and sends you a copy. The server writes a log line with a reference number and the topic, and counts recent messages per IP address (stored as a one-way hash) to stop abuse. If you send the form with JavaScript turned off, a session cookie carries the confirmation to the next page; it is deleted when you close your browser.
The administration area uses its own cookies, only for the people who run Luseed.
The web app keeps your journal in your browser’s storage (IndexedDB), and your preferences and sign-in session in your browser’s local storage. These are not used for tracking. They stay until you sign out or clear the site’s data. Clearing the site’s data also erases the journal kept in that browser, so export it first if you are not signed in.

Changes to this policy

When Luseed changes, this policy may change too. We will post the new version here with a new effective date. If a change is significant, for example a new use of your information, we will tell you in the app or by email before it takes effect, and ask for your consent where the law requires it.

Contact us

Intercode inc.
29 Du Marché, Roxton Falls, Québec J0H 1E0, Canada
Pierre-Verthume Larivière, person in charge of the protection of personal information
info@intercode.ca
luseed.org/support