Privacy policy

Controller

Zusage.app is operated by SESSILE STUDIO LTD, 71-75 Shelton Street, Covent Garden, London, WC2H 9JQ, United Kingdom, hello@zusage.app. We are the controller for the processing described here, except where a third party such as Paddle acts as an independent controller for its own checkout, payment, tax, fraud, and compliance processing.

We have not appointed a separate data protection officer. For privacy requests, contact hello@zusage.app.

What the service does

Zusage.app helps renters in Germany read listing wording, structure a renter profile, preview German application copy, and, after payment, download PDF or ZIP files. You remain responsible for checking every detail before sending it to landlords, brokers, portals, or any other third party.

Browser-first profile storage

Profile, listing, application tracker, notes, checklist, and draft content you enter can be stored in your browser's local storage so the app can remember your work between visits. During free preview and normal copy-paste use, this working profile stays on your device unless you copy it elsewhere, sign in, submit an email form, start checkout, or request a paid export.

Legal basis: legitimate interests in providing a browser-first product and, where you actively use the service, contract or pre-contract steps. Retention: until you clear your browser site data, use an in-app delete/reset control where available, or your browser removes the data.

Paid PDF and ZIP exports

If you sign in, have paid access, and request a PDF or ZIP download, the current profile and listing details needed to create that file are sent to a Supabase Edge Function. The function verifies your account entitlement, generates the requested file, and returns it to your browser. Free preview and copy actions do not send the full profile merely because you typed or copied text.

The export request is processed to provide the paid digital feature. We do not intentionally store generated PDF or ZIP files after returning them to your browser. Server and platform logs may temporarily contain technical request metadata for security, debugging, and abuse prevention.

Account and sign-in

Email sign-in is provided through Supabase. If you sign in, we process your email address, Supabase user ID, session tokens, and entitlement status so you can restore paid access and use authenticated downloads.

Legal basis: contract or pre-contract steps for sign-in and paid access; legitimate interests for security and abuse prevention. Account and entitlement records are kept while needed to provide access, handle support, comply with accounting or tax obligations, resolve disputes, and protect against fraud.

Payments and access

Purchases are handled by Paddle, which acts as merchant of record where shown at checkout. Paddle processes payment details, tax, fraud checks, invoices, refunds, chargebacks, and related customer information under Paddle's privacy policy.

We receive and store the information needed to grant and support access, including Paddle event IDs, event names, transaction or subscription identifiers where present, customer email where present in the webhook payload, user ID, entitlement state, event timestamps, and webhook payloads needed to audit purchases, refunds, chargebacks, and fraud. Legal basis: contract performance, legal obligations for accounting and tax, and legitimate interests in payment security and dispute handling.

Voluntary email list

On selected pages you may choose to subscribe to product-related emails, such as checklist or feature updates. If you do, we store your email address, source page label, consent flag, and timestamp in Supabase. The signup function also keeps a one-way fingerprint derived from IP address, user agent, and a server-side salt for rate limiting.

Legal basis: consent for the email list; legitimate interests for anti-abuse rate limiting. You can withdraw consent at any time by contacting hello@zusage.app. Withdrawing consent does not affect processing that happened before withdrawal.

Usage analytics and diagnostics

We collect first-party product events to understand whether the app works and where users get stuck. Events can include route, event name, CTA placement, funnel step, limited metadata, UTM or click identifiers from the URL, timestamp, and runtime error messages. Events are kept in browser local storage and, when Supabase is configured, are sent to a Supabase Edge Function and stored in our Supabase database.

The analytics endpoint also stores a one-way fingerprint derived from IP address, user agent, and a server-side salt for rate limiting. We do not intentionally include profile text, email content, landlord messages, or full rental details in analytics events. Legal basis: legitimate interests in product improvement, security, debugging, and preventing abuse.

If a tag manager or third-party analytics tool is later added, this policy must be updated before that tool goes live.

Cookies, local storage, and similar technologies

The app uses browser storage for profile data, application state, attribution parameters, analytics events, runtime diagnostics, and authentication sessions. Paddle may load its checkout script when you start checkout. Supabase may store authentication/session information when you sign in. We do not currently use non-essential third-party advertising cookies in the app.

Recipients and processors

Personal data may be processed by Supabase for authentication, database, and Edge Functions; Paddle for checkout and merchant-of-record services; hosting, DNS, security, logging, and email infrastructure providers used to run the service; and professional advisers or authorities where required by law or needed to handle disputes.

Some providers may process data outside your country, including the UK, EEA, and United States. Where required, we rely on adequacy decisions, standard contractual clauses, provider data processing terms, or another lawful transfer mechanism.

Retention

Browser-stored profile data remains until you or your browser remove it. Auth and entitlement records are kept while your account or paid access may need to be supported. Payment and invoice-related records are kept for the periods required for accounting, tax, fraud prevention, chargeback handling, and legal claims. Email-list records are kept until you unsubscribe or ask us to delete them, unless we need a limited suppression or audit record. Analytics and rate-limit records are kept only as long as useful for product improvement, security, and abuse prevention, then deleted or aggregated.

Your rights

Depending on where you live and which law applies, you may have rights to access, rectify, erase, restrict, object to processing, port your data, withdraw consent, and complain to a supervisory authority. To exercise a right, contact hello@zusage.app. We may need information to verify your identity before acting on a request.

If UK data protection law applies, you may contact the UK Information Commissioner's Office. If EU data protection law applies, you may contact your local EEA data protection authority.

Contact

Questions about this policy: hello@zusage.app