Privacy notice

Responsible operator

Abdulaziz Abdullah operates Jacob Deutsch as an individual established in Germany. Postal address: Brüsseler Str. 25 13353 Berlin Germany. Privacy and support: support@peliantule.resend.app. The initial supported country is Germany. The service is in development and free early testing. Paid plans may be introduced later; no subscription or payment is offered at this stage.

Information we process

We process your email address, account ID, confirmation status, sign-in provider and session/security information. Optional Google sign-in can supply profile information such as your name and picture. Supabase Auth manages credentials; the learning database does not store plaintext passwords.

We record self-declared eligibility and, for adopted Terms, the statement and version acknowledged, account, server time and entry point. We do not collect a date of birth or identity documents for the age requirement.

Learning information includes Scenario settings and custom context, sentences and surrounding context, generated dialogue and analyses, prepared audio, saved work, bookmarks, study/listening progress, reviews and personal practice transcripts, feedback and checkpoints. Operational records include access decisions, provider usage, request/response captures, provenance, failure recovery, diagnostics and security information. Hosting providers also process IP addresses and request metadata.

If you withdraw online, we receive the name, contract details and confirmation channel you specify, the declaration, its reference and the time of receipt. We use them to issue your receipt and handle the withdrawal.

Why we process information

Article 6(1)(b) GDPR applies to authentication, requested learning and voice features, saved progress, account recovery and necessary account messages, where necessary to provide the service you request. Providing the account information needed for those features is necessary to use them.

Our legitimate interests under Article 6(1)(f) are protecting accounts and the service, preventing abuse and duplicate provider operations, recovering interrupted work, managing proportionate access decisions, and keeping minimal evidence for rights requests and claims. We limit these records to what is necessary and review their continued need. You may object on grounds relating to your situation.

Article 6(1)(c) applies to receiving withdrawal declarations, issuing receipts, handling data-protection rights and complying with actual legal duties. A Terms acknowledgement is not blanket data-protection consent. Microphone permission is separate and can be withdrawn in your browser; withdrawal does not undo earlier lawful processing. We do not request marketing consent or use your information for advertising.

Accounts and authentication

Email/password and optional Google sign-in use Supabase Auth. Email confirmation is required. Necessary session and PKCE cookies support secure sign-in and account recovery. Resend handles confirmation and recovery email, including your recipient address, message and one-time link, before it reaches your mailbox provider. Keep passwords and sign-in/reset links private. Google separately handles information under its own privacy terms when you choose it. After you agree to the Terms, Resend sends a personal contract confirmation containing the accepted edition and withdrawal information.

Private and shared learning

When you request a standard Scenario using a built-in topic and suggestion or no custom context, the service can prepare the dialogue, matching analyses and audio once and offer that material to other learners. Your own saved copy, progress and bookmarks are processed to provide the learning you request (Article 6(1)(b) GDPR). They are not shown to other learners.

While standard material can be traced to an account, we rely on our legitimate interests (Article 6(1)(f)) to create and reuse a consistent library and avoid generating the same material repeatedly. We keep restricted links to the originating operation where needed to check the source, correct errors, avoid duplicate charges and handle rights requests. Other learners receive the learning material, not the originating account, its usage history or its raw request. A shared label does not make the source anonymous.

Your own custom context is private by default and is processed for the learning you request. Sharing a particular custom source requires your separate, specific permission (Article 6(1)(a)) and review before admission. You may withdraw that permission at any time. Personal practice, recordings, transcripts and feedback are excluded from the shared pool.

You can object to interest-based reuse or provenance processing for reasons relating to your situation. Contact support@peliantule.resend.app and identify the material if possible. We will stop the processing unless we demonstrate compelling overriding grounds or need it for legal claims. We can restrict use while we check. On closure or erasure we review identifying material, links and personal activity separately. Only material that can no longer reasonably be linked to a person is anonymous; its continued use must still respect content and consumer rights.

AI, audio and microphone

OpenAI processes relevant text and context for generation, analysis, tutoring and feedback. For the reviewed text requests we ask OpenAI not to store the response as an application object. That setting does not eliminate provider abuse-monitoring retention. ElevenLabs currently handles speech synthesis, recognition and alignment, receiving relevant text and audio.

The ordinary microphone relay does not save raw microphone chunks in application storage. Committed recognized speech, dialogue, feedback, checkpoints and operation evidence can persist. Prepared audio can also be saved privately. Diagnostic/recovery captures and browser memory are separate from the relay. Avoid unnecessary sensitive information or other people’s confidential information. AI output and speech recognition can be inaccurate.

Providers and international processing

Cloudflare delivers the website and stores our encrypted offsite backups. The EU location restriction applies to the R2 backup objects. Network delivery and support can involve other countries. Under Cloudflare’s data processing addendum, covered transfers to Cloudflare in the US use the EU–US Data Privacy Framework adequacy decision; its EU Standard Contractual Clauses (SCCs) cover restricted transfers.

Supabase provides sign-in, the Frankfurt database and private media storage. Its standard data processing addendum incorporates the European Commission’s SCCs for covered transfers, including onward transfers. Resend sends account email from Ireland and stores email and log data in the US. Its account agreement includes the SCCs.

OpenAI Ireland handles text requests under the API data processing addendum. For onward transfers outside the EEA it uses an applicable adequacy decision or SCCs. ElevenLabs handles voice under its business-input addendum; its transfer terms provide for adequacy where applicable and SCCs for restricted transfers. Neither service is confined to the EEA.

Resend receives support and privacy correspondence, including the sender address, message and any attachments. The operator reviews incoming requests in the Resend dashboard. Google processes sign-in information if you choose Google sign-in. Google describes reliance on the EU–US Data Privacy Framework for covered US transfers and SCCs where adequacy does not apply. You can also contact the operator by post or telephone. Please do not email passwords, identity documents or unrequested learning records.

You may ask support@peliantule.resend.app or write to the operator for information about a particular transfer and a copy of the applicable safeguards. The provider agreements and Google’s transfer information are linked below.

Cloudflare · Supabase · Resend · OpenAI · ElevenLabs · Google

Retention

We preserve useful saved work while you remain active. After 12 months without authenticated learning activity, we manually review the account, contact you and allow 90 days to respond. Incomplete activity information means we preserve and investigate. There is no automatic deletion or access expiry.

We review personal Bella practice after 12 months, preserving useful saved work and honouring applicable erasure requests. We review raw API request/response captures for minimisation 30 days after the operation is resolved. Only specifically justified recovery, legal or security evidence remains. Routine security logs have a 90-day retention rule; incident exceptions need separate reasons and review.

We delete temporary exports 7 days after confirmed delivery and review undelivered copies after 30 days. Resolved support correspondence is reviewed after 90 days to remove unnecessary content. Necessary minimal administrative evidence may be kept for up to 3 years after account closure or case/operation completion, with annual necessity review and earlier removal when unnecessary. This does not cover entire conversations, learning histories or raw captures.

Unreferenced private audio is reviewed after 30 days, checking ownership and other dependencies before removal. Genuinely anonymous shared learning/audio is reviewed annually for usefulness and permitted reuse. Review triggers require a decision; they do not themselves delete data. Restrictions and suspension preserve saved work and are separate from account erasure.

Backups and provider retention

Encrypted application backups include database records and private media. We keep local copies and a separate encrypted copy in Cloudflare R2 with backup-object storage restricted to the EU jurisdiction. The daily job depends on the operator’s Mac being available. Archives follow a rolling 30-day lifecycle; removal of eligible objects by the provider can take longer. We protect deletion and recovery evidence separately and keep it only while necessary to honour erasures, verify recovery or document a justified obligation. It has its own retention review. Supabase currently offers daily database restore points covering approximately the preceding week; database backups contain Storage metadata, not object bytes. Point-in-time recovery is not enabled.

Resend publishes 30-day email/log retention for the inspected Free plan and 7-day backups. OpenAI distinguishes application storage from abuse-monitoring logs, normally kept for up to 30 days with stated exceptions. We do not promise approved zero retention. ElevenLabs generation history and related logs/backups follow its applicable settings and terms; deleting a generation is distinct from expiry of all logs and backups.

Backups are separated from ordinary use. Following a restoration, erased information must be suppressed and deletion replay verified before traffic, jobs or provider processing resumes. We explain applicable backup and processor follow-through in the response to your request.

Your requests

Contact support@peliantule.resend.app for access and a copy, correction, erasure, restriction, objection, portability where applicable, or withdrawal of consent where relied on. No special wording is required. We check the privacy inbox each working day and aim to acknowledge requests within three working days.

We confirm control of the relevant account through proportionate account/email confirmation. We do not routinely request passwords, reset links or identity documents. Requests and deadlines are tracked privately. An account-scoped export is reviewed and delivered encrypted, with the passphrase communicated separately through an independently confirmed channel. Corrections and erasure use an account-specific reviewed plan that protects other learners’ information. Hosted account and private-byte removal have been rehearsed on disposable test accounts. Requests involving shared information or pending provider work may require staged action; we explain and track any unfinished part within the response deadline.

We respond without undue delay and ordinarily within one calendar month of receipt. Where complexity or number of requests warrants an extension, we explain the reasons within that month; the extension is at most two additional months. The acknowledgement target does not change this deadline. If refusing or taking no action, we explain why and your complaint and judicial-remedy rights within one month. Requests are ordinarily free; any manifestly unfounded or excessive exception must be justified.

We explain completed actions, specifically justified retained information and pending processor/backup work. Necessary exceptions are assessed individually. Corrections to immutable historical records use an accurately linked supplementary record or reviewed successor. Email changes use a secure confirmation process. Suspension does not prevent you exercising data rights.

Browser storage and safeguards

We use browser storage for necessary sign-in/session state, account-change signals, pending request and progress recovery, and microphone preferences. Microphone access is optional and controlled by browser permission. You can clear browser storage, although pending unsaved work may be lost. Downloaded or buffered media cannot be remotely recalled.

Access controls protect personal learning and private media. Full is learner access, Library allows eligible saved/shared learning without new paid generation, and Suspended blocks subsequent protected requests. No access mode grants administrative authority. No solely automated decision with legal or similarly significant effects is used for this access model.

Complaints and updates

You may complain to a competent supervisory authority, including the Berliner Beauftragte für Datenschutz und Informationsfreiheit: https://www.datenschutz-berlin.de/buergerinnen-und-buerger/rechte. Mandatory rights remain unaffected. We give appropriate notice of material changes to purposes, providers or this notice before they apply.