legal · privacy

Privacy, without vague promises.

Tappex is local-first. Optional Free text sync is designed so the relay cannot decrypt your captures. Tappex does not run a cloud AI service.

Effective: 23 October 2026
Controller: Daniel Schwarz, operating Tappex in Spain
Contact: daniels@tappex.app

Who this policy covers

This policy applies to the Tappex website and Tappex applications on supported Apple, Android, desktop, and browser platforms. “Tappex,” “we,” and “us” mean Daniel Schwarz, the independent developer operating Tappex from Spain.

Tappex is the data controller for account, service-operation, and support data. If you share a capture to another app with your device’s share feature, that app handles the information it receives under its own terms and privacy policy.

Data we process

Local captures

Text, voice recordings, links, timestamps, and other capture data are stored on your device first. Free does not require a Tappex account for local use. If you create an account and enable encrypted text sync, supported text capture state is sent to Tappex only as ciphertext. Your operating system or computer may include local app data in a platform-managed backup; that backup is controlled by Apple, Google, or your computer provider rather than Tappex.

Account and device data

When you create an account for sync, Tappex processes:

a pseudonymous identifier and issuer supplied by the configured sign-in provider;
device ID, device name, platform, public encryption key, public signing key, approval state, and last-seen time;
hashed session tokens and session expiry; and
security and delivery metadata such as IP address, request time, request ID, response status, ciphertext size, and rate-limit events where generated by the service or its hosting edge.

The current server does not need or store your email address from Sign in with Apple.

Encrypted sync data

Approved devices encrypt supported text capture state before upload and sign their sync envelopes. The relay stores ciphertext, nonces, signatures, event sequence numbers, opaque cursors, encrypted checkpoints, and wrapped device key packages. It does not receive note plaintext, audio, attachments, vault keys, private device keys, or your recovery key. Protocol v1 does not upload audio recordings or general attachment blobs.

Support data

If you contact us, we process your email address, message, and anything you deliberately attach. Do not send capture content, credentials, API tokens, vault keys, or recovery keys. Tappex does not sell subscriptions and does not process payment data.

Why we process it

PurposeLegal basis in the EEA

Create sessions, approve devices, provide encrypted text sync, and enforce fair-use limitsPerformance of our contract with you

Prevent abuse, protect accounts, enforce rate limits, diagnose outages, and maintain content-free service logsOur legitimate interests in operating a safe, reliable service

Maintain legally required recordsCompliance with legal obligations

Answer support and privacy requestsPerformance of the service, legal obligations, and our legitimate interests in customer support

We do not use capture content for advertising or train a Tappex model on it.

No Tappex cloud AI

Tappex does not operate an AI gateway and does not send capture content to an AI provider on your behalf. Transcription runs on your device.

Important distinction. End-to-end encryption describes Tappex sync storage. It does not mean content you share to another app remains unreadable to that app.

Recipients and international transfers

Depending on the feature you use, data may be processed by these recipient categories:

the configured identity provider, initially Sign in with Apple;
production hosting, database, encrypted object-storage, security, and email providers.

Some providers may process data outside Spain or the EEA, including in the United States. Where GDPR requires it, we rely on an adequacy decision, Standard Contractual Clauses, or another lawful transfer mechanism. Regional processing is used where the selected provider and feature support it, but it does not guarantee that every item of service metadata remains in one region.

We do not sell personal data or share it for cross-context behavioural advertising.

Retention and deletion

Active sync account: account metadata and encrypted relay data remain while needed to provide encrypted text sync, subject to fair-use limits and the checkpoint/history compaction policy.
Operational logs: account-linked logs are deleted or de-identified within 30 days where operationally possible. Non-personal aggregate counts may be kept longer.
Account deletion: active account data, sessions, relay ciphertext, and operational metadata are deleted within seven days; backup copies expire within 30 days.
Support: correspondence is kept only as long as needed to resolve the request and meet legal obligations.

Deleting an account does not silently erase local notes from your devices. See Delete your Tappex account.

Security and recovery

Tappex uses approved-device public keys, signed sync envelopes, encrypted payloads, bounded requests, hashed session tokens, rate limits, and deletion controls. No system is risk-free. The final cross-platform vault protocol and client implementations require independent cryptographic review before encrypted sync is described as production-ready.

Your recovery key is created for you to store. Tappex does not receive it. If every approved device and the recovery key are lost, Tappex cannot decrypt or restore the vault.

Your choices and rights

Depending on where you live, you may have rights to access, correct, delete, restrict, or receive a portable copy of your personal data; object to certain processing; withdraw consent; and appeal a privacy decision. Withdrawing consent does not affect processing that was lawful before withdrawal.

EEA users may complain to their local supervisory authority. In Spain, this is the Agencia Española de Protección de Datos. To exercise a right, email daniels@tappex.app. We may need to verify that the account is yours. We normally respond within one month, subject to legally permitted extensions.

Tappex does not discriminate against users for exercising applicable privacy rights.

Website data and cookies

The Tappex website does not use advertising trackers, third-party analytics, cookies, browser fingerprinting, or local storage. Fonts and website assets are served locally. Our hosting provider may process ordinary connection information such as IP address, user agent, requested path, response status, and time to deliver and secure the site.

If non-essential analytics or browser storage is introduced later, it will remain disabled until any consent required by applicable law is obtained, and this policy will be updated.

Children

Tappex is not directed to children under 16 and we do not knowingly create accounts for them. If you believe a child has provided personal data, contact us so we can investigate and delete it where required.

Policy changes

We will update the effective date when this policy changes. Material changes will be explained in the app, on the website, or by another appropriate channel before they take effect when required. A privacy notice explains processing; it is not a request for blanket consent to new purposes.

Contact

Daniel Schwarz operates Tappex as an independent developer in Spain. For privacy, support, or legal questions, contact daniels@tappex.app.