Privacy at BriNora
This notice explains what data is involved in each part of BriNora. In short: you can use the free places without an account. If you create an account, we keep the details needed for sign-in, your profile and any membership. Optional continuity, Nora AI, Voice Journal, wearable and notification features remain off until you activate them. BriNora uses no advertising or cross-site behavioural trackers.
Last updated: 19 July 2026
1. Controller
Adnan Nadif
BriNora
Spandauer Str. 4
10178 Berlin
Germany
Email: info@brinora.de
Telephone: +49 1556 888 123
2. Free use and your BriNora account
You do not need an account to open the free places and experiences. Our hosting provider still processes technical access data so the website can be delivered and protected. This may include your IP address, access time, requested address, browser and device details, and technical server or security logs. The legal basis is Article 6(1)(f) GDPR; our legitimate interest is the secure and reliable operation of BriNora.
If you create an account, we process an internal account identifier, your email address, authentication provider, display name, 18+ confirmation, account timestamps and necessary session and security information. We use these details to create and secure your account, let you sign in and provide your profile. The legal basis is Article 6(1)(b) GDPR. Fraud prevention and account security are also based on Article 6(1)(f) GDPR.
Your basic account profile is not an advertising or behavioural usage profile. State selections, Nora messages, journal entries, practice history and connected signals are not added to your server-side account merely because it exists. Optional local features require activation and sensitive features require a separate choice. Safety visits are never added to a profile.
3. Email and Google sign-in
Email sign-in is handled through Supabase Auth. Passwords are protected by the authentication provider and are not available to BriNora in readable form.
If you choose Google, Google authenticates you and shares the account details needed to create or find your BriNora account, which may include a provider identifier, email address and basic profile details. BriNora never receives your Google password. Your use of Google is also subject to its privacy information and account settings.
Authentication may involve processing outside the European Economic Area. Where required, this is protected through an adequacy decision, standard contractual clauses or another lawful transfer mechanism.
4. Membership access and payment
If you subscribe to or manage Practice or Master, we link your internal BriNora account identifier to the selected plan, subscription status, current period end, scheduled cancellation and the Stripe references needed to reconcile the subscription. Your account identifier is kept in BriNora's own database and is not added to Stripe metadata.
Payments are handled by Stripe. Information you enter on Stripe's website — such as contact, billing and payment details — is processed there. BriNora does not receive or store complete card or bank details.
The legal basis for account-linked subscription and payment processing is Article 6(1)(b) GDPR. We process legally required billing and evidence records under Article 6(1)(c) GDPR. Security and fraud prevention are based on Article 6(1)(f) GDPR.
5. Optional practice continuity, Nora, journals, signals and notifications
A one-visit state choice, temporary sequence and “For this visit” list stay in the open browser window by default. They are not added to your account or shared with payment providers. Practice history, Favorites, N-of-1 ordering, report inputs, manual weather, notification settings and delivery history are stored in the browser's local database on the device you use. They are not uploaded to BriNora's account database.
The local Nora guide uses a small word list in the active tab, makes no AI request and stores no message. If a Master user separately chooses Nora AI and confirms the private-session notice, the current prompt and up to eight visible conversation messages are sent through BriNora's server to OpenAI for safety moderation and response generation. No account identifier, journal recording or wearable value is included in that provider request. The visible Nora AI conversation remains in memory only and disappears when the page session ends. BriNora keeps a prompt-free account request counter for abuse and cost protection; an inactive counter row is removed after approximately 30 days.
BriNora asks the OpenAI Responses API not to store application state for the response (store: false). OpenAI states that API inputs and outputs are not used to train its models by default. Under standard API data controls, content may nevertheless be retained in abuse-monitoring logs for up to 30 days unless approved enhanced data controls apply. See OpenAI's current API data controls.
Voice Journal recordings and any transcript you type are stored as local browser data only; BriNora V1 does not upload or automatically transcribe them. Wearable-data import is a deliberate local file import or manual entry, not a permanent connection to Apple, Google or a wearable account. Supported HRV, sleep, step and resting-heart-rate estimates are parsed and summarized on the device. They are never sent to Nora AI automatically.
Contextual suggestions use the device's local time and season plus weather you select manually; BriNora does not request location for this feature. Device notifications require browser or operating-system permission and a separate topic switch. BriNora V1 checks schedules locally when the Practice product opens and may use compatible browser background-sync support. It does not register a server push subscription.
State, journal and physiological signals may reveal information about your personal, emotional or health situation. Processing therefore requires a separate, explicit choice and, where Article 9 GDPR applies, explicit consent under Article 9(2)(a). Each connected source can be switched off independently. You can withdraw consent for future processing and delete retained optional data without losing Explore or Immediate Help. Data held only in browser storage must be deleted on that device; it cannot be remotely removed from BriNora's account server.
Nora and adaptive suggestions provide wellbeing information and navigation, not a diagnosis or automated decision with legal or similarly significant effects. You confirm every state and remain the final decision-maker.
6. When you contact us
If you contact support, we process your contact details, message and anything else you choose to send. For account help, this may include your sign-in method. For billing help, it may include a Stripe payment receipt. Please do not send medical records or other sensitive details that are not needed for your request.
We use this information only to respond and administer the request. Depending on its subject, the legal basis is Article 6(1)(b) or 6(1)(f) GDPR. We generally retain support correspondence for up to three years unless a longer legal retention period applies.
7. Our service providers
We use the following services to operate BriNora. They process data on our behalf or as an independent controller where required for their own service.
| Service | Purpose | Data | Region / transfer |
|---|---|---|---|
| Vercel Inc. | Website hosting, delivery and security | Technical access, browser, device and server data | Processing in the United States may occur; protected by a data processing agreement, standard contractual clauses or other appropriate safeguards |
| Supabase Pte. Ltd. | Authentication, account profile, secure sessions and membership status | Account identifier, sign-in contact, display name, provider, 18+ confirmation, session/security data and minimal subscription records | Database region Central EU / Frankfurt; protected transfers to third countries may occur under the provider's data processing terms and applicable transfer safeguards |
| Google, only when selected | Social sign-in and identity verification | Provider identifier, sign-in event, email and basic profile details made available by the provider | International processing may occur under the provider's privacy terms and applicable transfer safeguards |
| Stripe | Payment, subscriptions, fraud prevention, receipts and refunds | Contact, billing, payment, transaction and security data | International processing may occur; protected by Stripe's data processing terms and appropriate safeguards |
| OpenAI, only when Nora AI is selected | Nora AI safety moderation and response generation | The message actively sent, up to eight visible conversation messages, generated response and necessary technical API data; no BriNora account identifier, journal audio or wearable values | Processing in the United States or other provider regions may occur under OpenAI's data processing terms, standard contractual clauses and applicable safeguards; standard abuse-monitoring retention may be up to 30 days unless enhanced controls apply |
BriNora uses no advertising, cross-site behavioural tracking or marketing service and does not send newsletters. User-selected product notifications are functional reminders, not marketing messages. Product personalization uses only the optional first-party information and controls described above.
8. Essential cookies
When you sign in or begin a Google sign-in, BriNora uses essential Supabase authentication cookies. They hold the tokens and temporary verification information needed to keep your session secure, complete the sign-in and refresh or end the session. They are not used for advertising, analytics or cross-site behavioural tracking. Because these cookies are necessary for the account service you request, they are not optional preference cookies.
If you open the external Stripe checkout, Stripe's own privacy and cookie rules apply there. BriNora does not use optional analytics or marketing cookies on its own pages.
9. How long data is kept
- Account and profile data: while your account is active, then deleted when you ask us to close it unless a record must be retained by law
- Authentication sessions: until they expire or you sign out; security records may be kept longer where needed to prevent misuse
- Technical server and security logs: generally up to 30 days, and longer only when required for a security incident or by law
- Subscription records: for the term of the subscription and afterwards where needed for administration, evidence or legal duties
- Payment, billing and tax records: for statutory retention periods, generally up to ten years
- Support correspondence: generally up to three years
- One-visit choices and local Nora input: only in the current browser window or tab
- Nora AI conversation in BriNora: in memory for the current page session only; OpenAI standard abuse-monitoring logs may retain API content for up to 30 days unless enhanced controls apply
- Nora AI request counter: account identifier, rolling-window time and count only; inactive rows are removed after approximately 30 days
- Practice history, Favorites, reports, notification settings and delivery history: in local browser storage until you clear them or the browser removes site data
- Voice Journal and imported wearable data: in local browser storage until you delete the entries, disable the relevant feature or the browser removes site data
10. Your rights and account deletion
Subject to the GDPR, you have rights of access, rectification, erasure, restriction of processing, data portability and objection. You can withdraw consent at any time with effect for the future. To exercise your rights or ask us to delete your account, use the link in your Account or email info@brinora.de. Local-only Practice, Journal and wearable records are not visible to BriNora's server. The in-app account-deletion flow also asks the current browser to remove its BriNora product database and reports if the browser cannot confirm that step. Data in another browser or device must be removed there with the Privacy summary or by clearing BriNora site data.
You may also complain to a data protection supervisory authority. The authority responsible for BriNora is, in particular, the Berlin Commissioner for Data Protection and Freedom of Information (Berliner Beauftragte für Datenschutz und Informationsfreiheit), Alt-Moabit 59–61, 10555 Berlin, Germany.
11. No automated decision-making
BriNora makes no automated decisions that produce legal or similarly significant effects. Nora and personalization may rank or suggest optional Paths, sessions and tips, but do not diagnose, make medical decisions or override your choice. There is no advertising profile.
12. Security
We use technical and organisational measures to protect data from loss, misuse and unauthorised access. These include encrypted transmission, provider-managed password protection, secure session cookies, row-level account access controls, separate service roles and collecting only the data needed for each purpose.
13. Changes to this notice
We update this Privacy Notice when BriNora, our providers or legal requirements change. The date at the beginning of this page shows the current version.