Updated: 24 October 2026 · Deutsch
This notice covers youproof.at, app.youproof.at and the youProof mobile app. It explains our processing when you visit, create or view a profile, share content, buy a subscription or contact us.
Key points: We store encrypted profile content together with readable account and technical metadata. People who receive your sharing link or QR code can decrypt the content it makes available and may copy or forward it. Supabase and Cloudflare provide service infrastructure; RevenueCat and Apple/Google handle subscription information. Usage statistics include fixed feature events and technical information, not the values you enter in app profile fields. Encryption does not make all service data anonymous. Protect your recovery QR code: it grants account access.
The controller and contact responsible for privacy requests and complaints is Franz Josef Drexler, sole proprietor, Silberbach 38, 4230 Pregarten, Austria. Email fj@drefrajo.dev; telephone +43 681 20887501. See our legal notice.
Where the EU or UK GDPR applies, we use the following bases. Other applicable privacy laws, including Swiss and Canadian law, may require consent or provide their own grounds and conditions; our contractual terms do not override those requirements.
| Data categories | Why we process them | GDPR basis |
|---|---|---|
| Account identifiers (including a Supabase user ID, cryptographic address and a derived technical login address), authentication records, terms version/acceptance records, settings and entitlement status | Create, authenticate and maintain your account, synchronize the service and record the agreement | Performance of our contract, Art. 6(1)(b); for necessary compliance records, Art. 6(1)(c) or legitimate interests under Art. 6(1)(f) in documenting agreements and resolving claims |
| Contact details, profile fields, links, posts and associated signatures, timestamps, record identifiers and sharing information | Store and deliver your profile and enable the sharing you request | Performance of our contract, Art. 6(1)(b) |
| IP address, request times, requested resources, browser/device and network information, error and security records, rate-limit information | Deliver websites/API responses, diagnose failures, prevent misuse and protect the service | Legitimate interests in reliable and secure operation, Art. 6(1)(f); Art. 6(1)(c) where a specific legal duty applies |
| Store purchase/transaction identifiers, product, subscription period, renewal/expiry status, entitlements and related account/device information | Activate and restore paid features, manage subscription status, handle billing support and meet recordkeeping duties | Performance of our contract, Art. 6(1)(b); applicable legal duties, Art. 6(1)(c) |
| Website usage statistics and fixed app feature events, screen size and language; related network information | Understand which pages/features are used and diagnose usability issues | Legitimate interests in proportionate usage measurement, Art. 6(1)(f), only where permitted without consent; consent under Art. 6(1)(a) where required |
| Apple AdServices attribution token and available campaign attribution information | Measure acquisition through Apple campaigns | Legitimate interests in proportionate campaign measurement, Art. 6(1)(f), where permitted without consent; otherwise consent under Art. 6(1)(a) |
| Messages, reply/contact details and attachments you send to support | Answer requests, investigate reports and resolve complaints | Art. 6(1)(b) for contract-related requests; Art. 6(1)(f) for other correspondence and handling abuse; Art. 6(1)(c) for applicable legal duties |
We receive profile information from you and, when you open someone else’s profile, from its creator. Subscription status also comes from RevenueCat and the relevant store. Providing optional profile fields is your choice. Account, security and subscription information necessary for a requested feature is needed to provide that feature. Do not upload unnecessary sensitive information or others’ data without authority. We do not use these data for automated decisions producing legal or similarly significant effects.
The current app encrypts profile content before upload. The backend still processes readable metadata, such as account/record identifiers, signatures, timestamps and subscription status. Older records may use different formats, including unencrypted records, until migrated. Support messages and technical logs are not covered by profile encryption. We therefore do not promise that every item of information is unreadable to us.
Sharing links or QR codes contain or provide access to decryption material. The recipient’s browser/app uses it to display the shared content. Anyone with a sufficient sharing key may read and redistribute that content. A restricted share may expose fewer fields, but it cannot prevent screenshots or copies. Do not send recovery credentials to us. Removing content cannot erase copies held by recipients. Visiting external links discloses ordinary connection information to their operators under their own policies.
On supported devices, biometric authentication or a device passcode unlocks locally stored credentials through the operating system/keychain. We do not receive face/fingerprint templates from this device authentication. The camera permission is used to scan QR codes, including recovery codes. The scanned value is handled by the app for the requested import or navigation; scanning itself is not a request to upload a camera image to us. You can control permissions in device settings; disabling a permission may prevent the corresponding feature.
We disclose data needed for operating the service to the following providers and recipient categories:
| Recipient | Data and purpose |
|---|---|
| Supabase | Authentication, account IDs, encrypted profile content and readable metadata, database/storage and backend processing |
| Cloudflare | Website delivery and network/security processing, including IP addresses and request information |
| RevenueCat | Subscription management: the app sends the Supabase user ID as its RevenueCat app user ID. RevenueCat processes store transactions, products, entitlements, renewal/expiry status and SDK technical information and reports subscription events to our backend |
| Apple / Google | Store purchases, billing and subscription management under their own policies. We do not receive your full payment-card details from store purchases. On iOS, the app enables collection of Apple’s AdServices attribution token through RevenueCat, which can supply Apple campaign attribution information where available |
| Umami at data.drefrajo.dev and its hosting provider | Website and app usage statistics and the technical information described below |
| Alchemy | The app configures an Alchemy Polygon RPC connection. If network requests are made, Alchemy receives connection information and the requested RPC data; this is separate from profile encryption |
| Email and communication providers | Delivery/storage of your support messages, attachments and correspondence metadata |
| People you share with | The profile content accessible through your link or QR code, as explained above |
We may also disclose necessary information to authorities where legally required, or to professional advisers to establish or defend legal claims, subject to appropriate confidentiality. Providers may act on our behalf or, for their own store, network or legal functions, as independent controllers.
Providers may process information outside your country, including in the United States. Foreign laws may permit access by local authorities. Applicable EU/UK/Swiss rules require an appropriate transfer basis and safeguards where necessary. Contact us for information about the arrangements applying to your data and how to obtain relevant safeguards.
The website loads an Umami script for page-use statistics. The app sends only allowlisted event names, such as editing a field or sharing a QR code, together with screen size, language, a fixed app path/hostname and the service’s analytics identifier. These app event payloads do not contain entered field values, profile links, recovery codes or account IDs. The analytics endpoint nevertheless receives an IP address at the network level, and hosting/security logs may permit linkage. We do not describe this as guaranteed anonymous measurement. Website requests may also contain page/referrer, browser and device information.
The app uses local preferences, secure credential storage and session information to remember settings and support login. We do not use app feature events to build cross-site behavioural advertising profiles. The Apple campaign attribution described above is a separate data flow. Linked sites and store/provider services may collect information over time across their own services under their policies.
Our application code does not currently change its behaviour in response to a browser Do Not Track signal. You can block the analytics endpoint using browser/device controls or contact us to object to processing based on legitimate interests. Where local law requires consent for optional analytics or device access, it must be obtained separately; accepting service terms or reading this notice does not supply that consent. Essential service storage and security processing remain necessary for their stated purposes.
We keep data only for as long as needed for the purpose: account/profile data for the service relationship, technical/security records for diagnosing issues and protecting the service, correspondence for handling the request and related claims, and transaction/compliance records for applicable statutory duties. The duration depends on account status, operational need, legal retention requirements and limitation periods. Backup copies may remain until their normal rotation; retained information must remain protected and used only for the relevant limited purpose.
You can edit/remove available profile fields in the app. Contact us to request account deletion or exercise privacy rights; we may need proportionate information to verify account control. Uninstalling the app is not account deletion, and account deletion does not cancel a store subscription. Never send your recovery QR code as identity evidence. We explain any information that must be retained and the applicable reason when responding. Recipients’ copies and records independently held by stores are subject to their own responsibilities.
In app versions supporting this feature, you can also request account deletion in the app. After you confirm, the server sets a deletion deadline seven days later. We retain your account/profile data during this waiting period and your account remains usable. To withdraw the request, explicitly choose Cancel deletion before the deadline; logging in or continuing to use the account does not cancel it. After the deadline, a background worker running hourly processes the deletion and retries technical failures, so completion may occur later than the deadline. The retention limits and legal/provider exceptions described above still apply; deletion cannot recall copies already held by recipients. This in-app process does not replace the email route for deletion and other privacy rights at fj@drefrajo.dev, or change applicable legal response deadlines. Store subscriptions must be cancelled separately.
Depending on applicable law, you may request access and a copy, correction, deletion, restriction, portability and information about disclosures, object to legitimate-interest processing, and withdraw consent at any time without affecting earlier lawful processing. Necessary service functions may become unavailable if you withdraw consent to processing they require; we will explain the consequences. There is no obligation to consent to unrelated optional purposes. Send requests and privacy complaints to the controller above; we will respond within applicable legal deadlines and explain any lawful limits or refusal.
For people in Canada, the same contact is responsible for privacy accountability: ask about collection, use, disclosures, safeguards and service providers, request access/correction, withdraw consent subject to legal or contractual restrictions with an explanation, or challenge our handling of your information. Where consent is required we must explain the relevant data, purpose, recipients and consequences and obtain meaningful consent, including a separate choice for a materially different optional purpose. You can complain to the Office of the Privacy Commissioner of Canada or the applicable provincial regulator.
Where applicable, you may complain to the Austrian Data Protection Authority, the supervisory authority where you live or work in the EEA, the Swiss FDPIC, or the UK ICO. US residents can contact us for access/correction requests and applicable state-law rights; we will assess requests under the laws that apply rather than assume every state’s threshold-based regime applies to this service.
The service is intended for adults aged at least 18 and the local age of majority if higher. If you believe a child has provided personal information, contact us so we can investigate and take appropriate action.
We update the date above when changing this notice. We will highlight material changes on the website and, for changes affecting app users, through an in-app notice before they take effect where practicable, or earlier where law requires. New processing that requires consent will require a separate choice before it begins. This notice is available in English and German; both versions explain the same processing.