Privacy Policy
Your data belongs to you.
Privacy is not a feature added at the end — it is the starting point of how this platform was built. This document explains in plain language what data is collected, how it is stored, how it is protected, and what you can do with it. Technical detail is included deliberately, because vague reassurances are not reassuring.
If something here is unclear, or if you have a question not answered below, write to hello@jordanelias.de. You will get a direct reply.
Who made this
The Sensory Intelligence Lab was built by Jordan Elias, a music therapist based in Berlin. This project is an attempt to build something that could hold continuity between sessions, support self-directed practice, and make music therapy tools accessible to people who cannot easily access in-person care.
Jordan Elias is the data controller for this platform. All questions, requests, and concerns go directly to one person, not a support team.
What this platform is — and is not
The platform has two distinct modes. The Lab is a self-directed space available to all subscribers — no clinical relationship is assumed or implied. The Session tiers involve a direct therapeutic relationship with Jordan Elias, governed by a separate therapy agreement completed before the first session.
Your content and your privacy
The journal, check-ins, worksheets, saved places and recordings are personal tools. The platform is built around two rules: nothing is recorded unless you choose to save it, and nothing you save is shared with anyone unless you choose to share it. Sharing is never switched on by default.
Download as a file — your entry is written directly to a file on your own device. Nothing is sent to any server. The file belongs entirely to you and is not encrypted.
Delete / Destroy — the text is erased from the page and from memory. Nothing is sent anywhere.
Writing, downloading and deleting are private in every case. No drafts are auto-saved to the server, and no keystroke or word-count data is sent while you write. The only moment saved content leaves your browser is when you press Save, and by then it is already encrypted.
Working with a therapist on the platform
If you are on a session plan you can connect to a therapist. Until you do, no therapist can see you at all, and free and Lab-only accounts are never visible to therapists. When you connect, you are shown exactly what the therapist will see before you agree: your name, your email, your subscription and intake status, and the times of the sessions you book with them. Nothing else is visible until you share it.
- Check-ins are shared only if you switch sharing on for that therapist, and you choose whether notes are included.
- Worksheets are shared one document at a time. There is no switch that shares them all.
- Messages between you and your therapist can be read only by the two of you.
- Journal entries, recordings and saved places are not shareable through the platform.
Shared items are re-encrypted so that only you and that therapist can open them. You can stop sharing, and either of you can end the connection, at any time. When a connection ends, you and the therapist each choose whether to keep or delete your own copy. You can also still download any file and send it by email if you prefer.
How encryption works
Saved content is encrypted in your browser before it is sent to any server. What the database holds is scrambled data that cannot be read without your key. The encryption key is protected by a passphrase that only you know.
Your vault
The first time you save something private you create a vault passphrase. Your browser turns it into a key using Argon2id (a deliberately slow function that makes guessing hard), and that key protects the random content key that encrypts your data. You also receive a recovery key, a second way to open the same vault if you forget the passphrase. The server stores only the protected bundle. It never receives your passphrase, your recovery key, or the unprotected content key.
Content encryption: AES-256-GCM with a fresh random 96-bit IV for every save, in your browser using the Web Crypto API
Passphrase protection: Argon2id (64 MiB, 3 passes) derives the key that wraps your content key
Recovery key: 160 random bits, a second wrapper for the same content key
Sharing keys: each account has an ECDH P-256 key pair for receiving shared items and an ECDSA P-256 key pair for signing messages. The private halves are encrypted with your content key. Shared items and messages are sealed separately to each person allowed to read them.
Binding: each encrypted item is bound to your account and its purpose, so it cannot be moved into another place unnoticed
What this means in practice
Not everything is encrypted. Your email, name, subscription, timestamps, booking times and the size of what you store are visible to the platform. Game scores and instrument or mixer settings are stored unencrypted. The table below lists each item.
This is a website. Your browser downloads the platform's code from our server each time. Encryption in the browser protects you against database access, but not against a malicious or compromised version of the site itself. We keep the number of outside code sources small and are working to remove the remaining ones.
What is stored and how
The table covers every category of data the platform stores. Anything you download or delete is not stored.
| Data | Where | State | Who can read it |
|---|---|---|---|
| Email address | Login records | Plaintext | You. Platform operator. Supabase. |
| Display name, subscription tier and status, intake status | Profile | Plaintext | You. Platform operator. Your therapist, if you connect to one (see above). |
| Journal entries (text and title) | Database | Encrypted in your browser | You only. Journal entries cannot be shared through the platform. |
| Journal details: date, length, duration, soundscape, prompt | Database | Plaintext | You. Platform operator. |
| Offline copy of the tool pages you have opened | This device | No personal content | You. It holds only the site's own pages, scripts and images, never your journal, check-ins, messages or account. |
| Intake form: name, date of birth, pronouns, contact, medications, history | Database | Encrypted in your browser | You. Your therapist, only after they ask for it and you choose to send it. We store only that it exists. |
| Check-ins: scores, emotion words, notes | Database | Encrypted in your browser | You. Your therapist, only if you turn sharing on. |
| Saved places | Database | Encrypted in your browser | You only. |
| Worksheets | Database | Encrypted in your browser | You. Your therapist, only for the individual worksheets you share. |
| Audio recordings and compositions (audio, title, length) | Private file storage | Encrypted in your browser | You only. Files are never at public links. |
| Messages with your therapist | Database | Encrypted in your browser | You and your therapist only. |
| A therapist’s private notes about a client | Database | Encrypted in your browser | The therapist who wrote them only. They stay with the therapist if a connection ends, and are removed if the client deletes their account. |
| Items you share with a therapist | Database | Encrypted in your browser | You and that therapist only. |
| Your public sharing and signing keys | Database | Plaintext | Visible to the platform. Used so others can encrypt to you and verify your messages. Not secret. |
| Your protected vault bundle | Database | Encrypted in your browser | Only your passphrase or recovery key can open it. |
| Game scores, instrument and mixer settings | Database | Plaintext | You. Platform operator. |
| Who is connected to whom, when messages were sent, how large items are | Database | Plaintext | Platform operator. The people involved. This information is not hidden. |
| Booking times and the therapist booked with | Database | Plaintext | You. Platform operator. The therapist you booked with. |
| Booking details | Cal.com or the therapist’s own booking page | Held by them | Governed by their privacy policy. |
| Card details and invoices | Stripe | Stripe-managed, PCI-DSS | Stripe. We never see card numbers. We keep only a Stripe customer and subscription ID. |
| Downloaded or deleted entries | — | Not stored | No one. Nothing is recorded. |
Identity separation
Your content is attached to a random account ID, not to your name or email, which are held in separate tables. Anyone looking only at content tables would see scrambled data under anonymous IDs. This is a precaution, not a guarantee: the platform operator can link IDs to people.
Supabase and the database
This platform uses Supabase as its database and authentication provider — an open-source alternative to Firebase, built on PostgreSQL and hosted on AWS. The database is in the EU West (Frankfurt) region, keeping all stored data within the European Union.
Row Level Security (RLS)
Every table has Row Level Security enabled. RLS is a PostgreSQL feature that enforces access control at the database level — not just in application code. Even if there were a bug in the application, the database itself would refuse to return data the requesting user is not authorised to see.
Your own data: check-ins, worksheets, journal entries, recordings, saved places and your profile can be read, changed and deleted only by the account that owns them.
Therapists: a therapist can see an account only through the connection you created, and only the few fields listed above. Free and Lab-only accounts do not appear to therapists at all.
Shared items and messages: readable only by the two people they were sealed to, and even then only as scrambled data that their own browser opens.
Key material: your protected vault bundle can be read only by you.
The service role key
Supabase provides two API keys: an anon key (used in the browser, subject to RLS) and a service role key (bypasses RLS, for server use only). The service role key is stored only in Netlify environment variables and is never exposed to the browser. The vault function that handles encryption keys uses the service role key only after verifying the user's session token.
Supabase's own privacy commitments
Supabase is SOC 2 Type 2 compliant and GDPR-ready, with encryption at rest and in transit. Read their privacy policy at supabase.com/privacy. Jordan Elias is the data controller — Supabase acts as a data processor.
Data we collect
We collect only what is needed for the platform to work. There is no advertising, no third-party tracking and no analytics that profile your behaviour.
Account data
Your email address, your chosen display name, and your password (hashed by Supabase; we never see it).
Content you choose to save
Journal entries, check-ins, saved places, worksheets, recordings and messages, stored encrypted as described above. Downloaded or deleted content is never recorded.
Session and technical data
Supabase logs sign-ins and token refreshes for security, and our hosting provider processes your IP address as part of delivering the site. We run no analytics or tracking scripts, no marketing trackers, no pixels and no fingerprinting.
Booking data
When you book a session, the booking is made on Cal.com or, if your therapist uses their own calendar, on their own booking page. That service receives your name, email and chosen time and has its own privacy policy. The platform records only when the session is and which therapist it is with, so that sessions can be counted and shown to you and to that therapist.
Intake
The platform stores only an intake status (for example, not started or complete). It is visible to a therapist you connect with. The platform does not store the contents of any intake forms.
Data sharing
Your data is not sold, rented or shared with third parties for commercial purposes.
Outside services used
| Service | Purpose | Data involved |
|---|---|---|
| Supabase (EU, Frankfurt) | Database, login and file storage | All stored data, encrypted where marked above |
| Netlify | Website hosting and server functions | Web requests (IP address and the pages you open) |
| Stripe | Payments | Email, name, subscription. Card data goes to Stripe only. |
| Cal.com | Session booking | Name, email, booking details |
| Code libraries from content delivery networks (jsDelivr, cdnjs, unpkg) | Loading open-source code libraries | Your IP address, when a page loads one |
| YouTube | Playing songs you choose in some exercises | Standard embed data, only on pages where you use it |
| Genius and LRCLIB | Song and lyric lookup in the worksheets | Your search text, passed through our server function for Genius |
Fonts are served from this site and no longer from Google.
Sharing with a therapist
This happens only through the connection described under “Your content and your privacy”, and only for what you choose to share. Nothing is shared by default. The platform operator cannot read what you share. When you or the therapist end the connection, access stops immediately.
Legal disclosure
We may be required to disclose data in response to a valid legal request or court order. We can only hand over what we hold: encrypted content stays unreadable to us. If this happens we will notify you unless legally prohibited.
Payments and Stripe
Subscriptions and payments are processed by Stripe, a PCI DSS Level 1 certified payment processor. When you enter card details, you enter them directly into Stripe's interface — your card number, CVC, and expiry date never reach our servers or our database. We store only your Stripe Customer ID and subscription status.
Cancellation
You can cancel your subscription at any time from the Account page. Cancellation takes effect at the end of your current billing period. We do not offer refunds for partial periods, but if you believe there has been an error, contact hello@jordanelias.de.
Subscription tiers
Pricing and tier details are shown on the account and booking pages. Existing subscribers will receive at least 30 days notice before any price increase takes effect.
Your rights under GDPR
As a resident of the EU, UK, Switzerland, or another jurisdiction with equivalent data protection law, you have the following rights. To exercise any of them, write to hello@jordanelias.de. We will respond within 30 days.
Right of access
Your saved content is visible to you inside the platform, and “Download my data” on the Account page gives you a copy. For anything else we hold about you, contact us. Because your content is encrypted, only you can open it.
Right to rectification
You can update your name and email from the Account page. For anything else, contact us.
Right to erasure
You can delete individual items from within the platform, and delete your whole account yourself from the Account page. See below.
Right to data portability
On the Account page, “Download my data” saves everything stored for you (journal, check-ins, saved places, worksheets, messages, bookings and scores) to one file on your own device. Audio recordings are listed in it, and can be downloaded one by one.
Right to object / restrict processing
Contact us to discuss any concerns about how your data is being processed.
Lawful basis for processing
We process your data under GDPR Article 6 on the bases of performance of a contract (providing the service), legitimate interests (security logging, fraud prevention), and consent (for any processing not covered by the above, including everything you choose to share with a therapist). Health-related data under Article 9 is processed with your explicit consent.
Deleting your account
You can delete your account yourself from the Account page. It takes effect straight away and removes your login, your profile, all of your saved content, your recordings and files, your keys, your messages and shared items (including the copies held by a therapist), your booking records and your therapist connections. It also cancels your subscription immediately.
Some records are kept by others and are outside the platform: Stripe keeps the payment records it is legally required to keep, and Supabase's backups are cleared on their own schedule. Your encrypted content in any such backup cannot be read without your passphrase or recovery key.
Crisis disclaimer
| Service | Contact | Availability |
|---|---|---|
| Telefonseelsorge (Germany) | 0800 111 0 111 or 0800 111 0 222 | Free, 24/7 |
| Crisis Text Line (UK) | Text HELLO to 85258 | Free, 24/7 |
| International directory | findahelpline.com | Worldwide |
If you work with Jordan Elias in a session tier and experience a crisis between sessions, please contact emergency services first. Jordan will have shared a safety plan and out-of-hours contact protocol as part of the therapy agreement.
Frequently asked questions
No. Saved content is encrypted in your browser with a key protected by your passphrase, and the server never has it. A therapist can see a check-in or worksheet only if you choose to share it, and then only that item, sealed to you and them.
No. Nothing is sent while you write. No drafts are saved on the server and no keystroke or word-count data is sent. Only when you press Save does the encrypted entry leave your browser.
No. Downloading writes the file directly to your device. The platform has no record of it. The downloaded file is not encrypted, so keep it somewhere you trust.
Use your recovery key. If you have lost both, your encrypted content cannot be recovered by anyone, including us, because we do not hold a copy of your key. Resetting your account password does not unlock it.
No. Free and Lab-only accounts are never visible to therapists. A therapist sees you only after you connect with them, and then only your name, email, subscription and intake status, the times of the sessions you book with them, and whatever you choose to share.
Only you and your therapist. Messages are encrypted to the two of you and signed so they cannot be forged. Each of you can delete your own copy.
Their access stops immediately. You and the therapist each choose whether to keep or delete your own copy of what was shared and of the messages.
Cancelling removes access to paid features at the end of the billing period. It does not delete your data. To remove your data, delete your account from the Account page.
No advertising cookies, no tracking pixels and no analytics. Your browser keeps your sign-in session and a few settings needed for the platform to work.
No. Your data is not used to train AI models, sold to AI companies, or used for anything other than providing you with the platform.
The database and file storage are hosted by Supabase in the EU (Frankfurt). Netlify hosts the website and server functions and does not keep your content. Stripe and Cal.com have their own storage under their own policies.
You will be given at least 90 days notice and a way to export your data before closure. Data will not be transferred to a third party; it will be deleted.
Contact
For questions about this privacy policy, to exercise your rights, or to make a complaint:
If you are not satisfied with the response to a complaint, you have the right to lodge a complaint with the relevant supervisory authority. In Germany, this is the Bundesbeauftragte für den Datenschutz und die Informationsfreiheit (BfDI).