Poffli Get Poffli

Poffli privacy

Updated 17 November 2026

Your drawings

Shared drawings, images, notes and reactions are encrypted on your devices using OpenMLS. The relay stores encrypted packets, not your encryption keys. Your person can read, edit and save what you share. Widgets display locally rendered copies which may be visible on your Home Screen.

Account and connection data

Firebase Authentication processes Apple or Google sign-in. Poffli stores account IDs, device public keys, invitations, connection IDs, delivery metadata and push registrations. Your provider name and verified email may be shown to the person opening your invitation or connecting with you. Private local edits are shared only when you choose Update.

Poffli Plus purchases

If you buy Poffli Plus, Apple or Google handles the payment. Poffli receives and stores the product, store transaction or purchase reference, expiry and refund status linked to your account, so it can check the purchase with the store. Poffli never receives your card or bank details. Purchase records are deleted with your account.

Service providers

Google/Firebase provides sign-in and Android push delivery; Apple provides sign-in and iOS widget pushes; Cloudflare forwards web/API traffic and provides cookie-free visit statistics for poffli.app; Hetzner hosts the API and database. Google/Gmail processes support email. These services process the network/account data needed to operate Poffli. Push payloads contain no artwork.

Sign-in SDK data

The bundled Google Sign-In SDK declares processing of profile and contact information (including name, email and phone number where available), user/device identifiers, approximate location such as network-derived location, and sign-in usage or technical data. Google uses these for authentication, security and service analytics. Poffli requests basic profile and email access, not your address book or GPS location. See Google’s privacy policy for its handling of provider data. Poffli does not use this data for targeted advertising or sell it to data brokers.

Diagnostics

Production builds use Firebase Crashlytics for crash reports, device/app version and stack traces. Poffli does not attach artwork, names, email addresses, account IDs or exception messages. Native crash reports may include technical system diagnostics and installation identifiers. Firebase components also process technical diagnostics for service analytics. Diagnostics are not used for advertising.

Reports and support

Reports contain the selected reason, connection/content reference and text you choose to submit. Support can read reports and emails; these are not end-to-end encrypted. Artwork and encryption keys are never attached automatically. Poffli does not sell artwork or use it for advertising.

Your controls and retention

Disconnect or block a person, report shared content, or delete your account. Deletion removes the account and associated server data. Copies already saved by another person cannot be recalled. Minimal identity and deletion-receipt hashes remain for 30 days after completion to prevent stale requests recreating the account. Server backups expire after 30 days. Resolved safety reports and support correspondence are retained for up to 90 days after resolution. Safety records follow this retention even after account deletion; unresolved safety cases remain until resolved.

Email lekacoding@gmail.com. Do not send passwords or encryption keys.