QuickSecret 0.5.2

Privacy policy

Dated 13 November 2026. Applies to the website quicksecret.app and the Android app QuickSecret (package name app.quicksecret), version 0.5.2.

1. Controller

The controller within the meaning of the General Data Protection Regulation (GDPR) is:

Patrick Schömel
Email: info@quicksecret.app

2. This website

The site is a static offering. It uses no cookies, no tracking, no analytics or advertising tools, no social-media plugins and no external fonts or content-delivery networks. Fonts and images are served only from this domain. The site does not use local storage or similar browser storage for analytics or marketing.

Hosting and server logs

The website is hosted by OVH on the “hosting-free-100m” plan. The contracting party or technical operator may be:

OVH GmbH, Oskar-Jäger-Straße 173, 50825 Köln, Germany, and/or
OVH SAS, 2 rue Kellermann, 59100 Roubaix, France.

When you request a page, the host may create server logs. These may include in particular the IP address, time, requested resource, HTTP status, amount of data transferred, user agent and, where sent, the referrer. The purpose is to operate and secure the website and to prevent abuse (Art. 6(1)(f) GDPR, legitimate interest in a stable and secure offering). We do not use these logs for advertising, profiling or reach measurement. How long logs are kept and further details follow the host’s operational and legal requirements. See also OVH’s privacy information: ovhcloud.com/en/personal-data-protection.

Contact by email

If you write to info@quicksecret.app, we process your email address, the content of the message and typical transmission metadata in order to reply. The legal basis is Art. 6(1)(b) GDPR where the message relates to use of the app or website, and otherwise Art. 6(1)(f) GDPR (legitimate interest in corresponding with you). The mailbox is hosted at OVH; OVH may process the message technically as part of mail hosting. We keep correspondence only as long as needed to handle the request, for any evidence obligations, or for statutory retention periods. The app does not automatically send us notes, attachments, passwords or diagnostic reports.

3. The app: purpose and principles

QuickSecret creates and opens end-to-end encrypted notes. It is free, with no ads, no user account, no billing and no analytics or advertising SDK. No usage or note data is sent to the developer unless you email us yourself.

The support and privacy contact is info@quicksecret.app. In the app, “Open email app” only opens your mail app with the address and a fixed subject; nothing is sent automatically.

4. Notes, files and third-party services

Text, selected files, photos and voice recordings are encrypted on the device before transmission. Only your explicit create or send action uploads them. Capturing media alone does not.

The stable app supports the independent third-party services PrivateBin, Cryptgeon and Yopass. Attachments may use your configured PrivateBin attachment instance; check the provider shown in the app. Default configured instances include paste.systemli.org and 0bin.ch for PrivateBin, cryptgeon.org, and share.yopass.se (web link) / api2.yopass.se (API) for Yopass. Additional offered PrivateBin instances are pb.envs.net and privatebin.net. If automatic fallback is enabled, offered fallback instances may be used after a failure; check the resulting provider. A timeout may leave it uncertain whether an earlier upload was already accepted. You may approve custom instances. Their terms and actual operator practices also apply.

App startup, reopening and switching to share or the bubble do not automatically check provider availability. Only the explicit “Check availability” action in Settings contacts all integrated providers plus configured PrivateBin and fallback instances. These network checks do not create or consume notes, but they do expose connection metadata. Results are dated snapshots, not continuous monitoring. Cancellation prevents subsequent probes; an in-flight request may still finish within its network timeout. Manual checks are not required in order to create notes. Explicit note creation may perform necessary capability requests and any configured fallback. Status checks and opening a note also contact that note’s provider.

The app does not transmit the note key to the note API. A shareable link may contain a key in its URL fragment, or a key may be derived from a separately shared password. Anyone who receives the link and key, or the password, may gain access. Providers typically see the IP address, HTTP metadata such as the User-Agent, timing, ciphertext size, and protocol-dependent expiry and view options. Whether and how long operators log this metadata has not been verified live. The QuickSecret developer does not receive those server logs.

The operator of the instance you choose processes the ciphertext and connection metadata under their own responsibility. Depending on the default or custom instance, processing may take place outside the EU or EEA. The provider’s own terms and safeguards then apply. QuickSecret cannot generally warrant the location of every public or user-added server.

The legal basis for processing triggered by the app on your device and, at your request, towards those services is Art. 6(1)(b) GDPR (providing the function you asked for). If you knowingly choose an instance or an optional feature, that forms part of this use.

5. Local storage

History stores the provider or instance, identifiers, deletion and status tokens, times, status, labels and possibly the target app, encrypted in private app storage and backed by the Android Keystore. Note content, link keys and note passwords are not stored in history.

Settings, approved hosts, custom text templates and app-lock configuration are stored separately in private app storage; no blanket content-encryption claim is made for these. Templates may contain text you explicitly saved. Drafts, loaded attachments and result links may remain in process memory during use. Rotation is supported; process termination may lose unsaved drafts. An enabled password reminder temporarily retains the password in process memory.

Photo or audio capture first creates an unencrypted file in the private, non-exported app cache. The chosen camera app receives temporary access only to that specific photo URI. App capture files are deleted after processing or cancellation. Orphans left after process termination are removed at the next app or capture start once they are older than one hour; this is not a guarantee of deletion at exactly one hour. Camera apps or system document providers may keep their own copies. Loaded attachments remain in memory until removal, note creation or the end of the draft. Android app backup is disabled. Forensic secure deletion from flash storage is not promised.

6. Permissions

Microphone access requires a permission request and an explicit Start: recording is visible in the capture view and capped at five minutes or the remaining attachment budget. Leaving or interrupting discards it; it does not continue in the background.

Photo capture is delegated to a camera app you choose; QuickSecret does not request its own camera permission. Document selection grants access only to the selected URIs, not to the media library at large.

The optional bubble uses overlay access and a visible specialUse foreground service with a stop action. Optional accessibility access requires separate disclosure and consent: app or window state and an existing message draft are processed locally to show the bubble or append a link. There is no automatic sending and no reading of chat history.

Android handles biometrics and device authentication; QuickSecret receives no fingerprint data. Notifications are optional, for reminders.

Copy, share or insert transfers the generated link, possibly including a key, to the clipboard or a target app at your request. Those apps’ behaviour is outside QuickSecret’s control. Copied links are marked sensitive in the app and are removed from the clipboard after a short time if they are still there.

If you send an email yourself, your email provider also processes the message.

8. Account and data deletion

There is no QuickSecret user account to delete, and no cloud account for the app operated by the developer.

You can remove local data as follows:

In the app: “Clear history” removes only local history entries, not notes already stored with a service.
In Android settings: Apps → QuickSecret → Storage → Clear data (or the equivalent path on your device) removes local app data.
Uninstalling also removes local app data.
Accessibility consent can be revoked in QuickSecret; system permissions can be revoked in Android.

Remote deletion of a note is offered only where the service supports it (PrivateBin); the result and any retention depend on the operator. A Cryptgeon DELETE retrieves content or consumes a view; it is not remote revocation. Cryptgeon once-read notes have no time limit until first retrieval; multiple-read notes on the public instance have a time cap. Copies, screenshots and content saved by a recipient cannot be recalled. Copies held by other apps or providers are not affected by deleting local data.

Where the legal conditions are met, you have the right of access (Art. 15 GDPR), rectification (Art. 16 GDPR), erasure (Art. 17 GDPR), restriction of processing (Art. 18 GDPR), data portability (Art. 20 GDPR) and the right to object to processing based on Art. 6(1)(f) GDPR (Art. 21 GDPR). Where processing were based on consent, you may withdraw it with effect for the future.

In practice, the developer usually only holds data that you send by email, plus typical hosting logs at the host. The developer cannot read note content on third-party instances and cannot delete it there.

You also have the right to lodge a complaint with a supervisory authority, in particular in the Member State of your habitual residence, place of work or place of the alleged infringement (Art. 77 GDPR). In Germany, the authority competent for the controller depends on the controller’s seat. The Federal Commissioner for Data Protection and Freedom of Information publishes an overview of German supervisory authorities: bfdi.bund.de.

10. Security and limits

The app uses HTTPS and standard certificate and hostname verification. Connections use the validated public DNS addresses; private or special networks, redirects and system HTTP or SOCKS proxies are deliberately unsupported. This does not control the operating system, VPN routing, certificate store or the service operator.

End-to-end encryption does not protect against a compromised app, device or web viewer. Choose trusted recipients and share passwords separately.

This policy describes app version 0.5.2 and this website. Material changes will be reflected here. No security audit and no Google Play approval is claimed.