Privacy Policy

Last updated: 11 October 2026 · Applies to the Effortly website, the browser editor and the Effortly Android app.

Privacy by design. Effortly fills your PDF on your own device — in the browser, or on the phone. Nothing you place on a document ever leaves it: not what you type, not what you tick, not your signature, not the photographs you insert. The app on Google Play uploads no document at all for compression — it compresses on the device. In the browser there is one optional button, "compress on our server", where the file is processed for that single request and immediately discarded; it is a choice, not a step. The other exception is "Smart placement wrong here?", where you deliberately send us the blank form — never what you filled in — so we can work out why placement missed on it. Anything you save in a wallet (your reusable fields and signatures) stays on your device and, if you connect one, in your own Google Drive — encrypted there with your master password. We do not hold your wallet at all: the server copy that used to exist as a restore path was removed on 17 October 2026, and what an account holds is your email, counters, and the key material your master password unwraps — never the names, addresses or signatures it protects.

1. Who we are

Effortly (geteffortly.com, pdf.clearlogicassist.com and the Effortly: PDF Form Filler Android app) is operated by Clear Logic Assist Ltd., Malta (clearlogicassist.com) — the data controller. Contact: support@clearlogicassist.com.

2. What the Android app sends

The app has one Android permission: internet access. It contains no analytics SDK, no advertising SDK and no third-party crash reporter. It sends exactly five things, and this is the complete list.

What	When & what it contains	Legal basis (GDPR)
Crash and ANR reports (always on)	When the app crashes, and on the next launch for a crash the system recorded (including an out-of-memory kill or an ANR): app version, device manufacturer and model, Android version, thread name and the technical stack trace. Sent to our own server, stored separately from everything else, and never linked to your account. No document content, file names, wallet data or text you typed is included.	Legitimate interest (Art. 6(1)(f)) — keeping the app working
Usage counters	Once a day at most, a small count of how often the app was launched, a document was opened, saved or compressed, plus which channel the app came from (Play or a direct APK) and the date. No identifiers of any kind — no device ID, no advertising ID, no account email — so these counts cannot be tied to you or to each other. If there is no connection they wait on the device and are sent later.	Legitimate interest — knowing whether the app is used at all
Feedback you write	Only when you use Settings → Feedback & ideas: your message, the email address you choose to give (optional), and the app version, channel and Android version. Nothing is sent unless you press Send.	Consent / contract
A blank form — only if you report one	Only when you choose "Smart placement wrong here?" in a document's menu and confirm. What is sent is the blank original of that form — never the version with your answers on it — together with the note you write. We keep it to work out why automatic placement missed on that layout, and for nothing else. Nothing is sent unless you confirm.	Consent
A document — only for "Compress on the server"	If you choose that one action, the PDF is uploaded, compressed and returned. It is not stored, not inspected and not kept after the request. Every other operation — filling, signing, saving, exporting — happens on your phone.	Contract (you asked for it)

3. What stays on your device

Your documents. Rendering, filling, signing and saving all happen locally. Recent documents and autosaved drafts are stored on the device only, and go away with the app's data.
Photos and scans. The app uses your phone's own camera app to take a picture of a form or a signature; the image goes into the document on the device. The app declares no camera permission of its own.
Your wallet (reusable fields, signatures, images), unless you choose to put it in your Google Drive. With a master password it is also encrypted at rest on the phone.
Biometrics. If you turn on fingerprint or face unlock, Android's own secure hardware holds the key; the app never receives your fingerprint or face data, and neither do we.

4. Google Drive and Google Sign-In

Sign-in — if you continue with Google, Google processes the sign-in under its own privacy policy. We receive only your verified email address.
What syncs, and how — your wallet is encrypted on your device before it is written, so what sits in your Drive is unreadable without your master password. Documents you sync are stored as regular files: they hold your answers the way any filled form does. Exporting a finished PDF does not use this at all — that goes through your phone's own save dialog, which can write to Drive without Effortly having an account or a token.
Drive — Effortly uses the narrow drive.file scope (Google classes it as non-sensitive, precisely because it grants so little): it can only see files it created or that you opened with it, never the rest of your Drive. Wallets and documents saved there are in your Drive, under your Google account. We do not receive them, cannot read them, and deleting your Effortly account does not touch them — you remove them yourself in Drive.

5. If you create an account

An account is optional: the app and the editor work fully without one. If you create one we hold:

Data	Why	Legal basis
Email address	To identify the account and sign you in.	Contract (Art. 6(1)(b))
Authentication verifier & salts (password accounts)	A one-way salted hash. We never receive your password.	Contract
Entitlement and counters: whether the account has Pro, number of documents saved	To give you what you are entitled to, and for accounting and abuse prevention.	Contract; legitimate interest
Encrypted wallet (older accounts only)	Ciphertext we cannot read. New wallets live in your own Drive instead.	Contract
The address of the Google Drive you connected (e.g. you@gmail.com)	So the app can refuse to sync your wallet into a Drive your account never agreed to. We store the address only — never a token, and never the files.	Contract
Technical server logs (IP address, timestamps, request metadata)	Security, rate-limiting, diagnosing errors.	Legitimate interest

6. What we never have

Your master password, or any key derived from it.
The readable contents of a wallet — ours or the one in your Drive.
The documents you fill in, their names, or anything you type into them.
Your fingerprint or face data.
Any advertising identifier. We run no ads and no cross-site tracking.

7. Deleting your account and data

You can delete your account yourself, in the app (Settings → Delete account) or in the browser, and the full instructions — including what is removed and what is kept briefly — are on a page of their own: How to delete your Effortly account and data.

In short: your encrypted wallet, salts, verifiers and balance are erased immediately. A minimal tombstone (your email address, aggregate counts and the deletion date) is kept for up to 90 days to prevent abuse and for accounting, then permanently purged. Files in your Google Drive stay yours and are not touched.

8. Retention

Account data is kept while the account exists, then as described above. Crash reports and usage counters are kept while they are useful for fixing and improving the app and are not linked to an account. Server logs are kept for a short period.

9. Third parties and transfers

Google (sign-in, Drive, Play) — under Google's own terms; Play's own data handling is described in the Play listing.
Hosting — our server is a virtual private server located within the EU/EEA. We do not sell or share your data, and there are no advertising or analytics partners.
Payments — not in operation yet. When they are, a Merchant of Record will handle payment and card data; we will not store card details.

We process data within the EU/EEA. Where a provider such as Google transfers data outside the EEA, it is covered by appropriate safeguards (e.g. Standard Contractual Clauses).

10. Your rights

Under the GDPR you may request access, rectification, erasure, restriction and portability, and object to processing based on legitimate interests. Write to support@clearlogicassist.com and we will answer within 7 days. You may also lodge a complaint with your national data protection authority; ours is the Information and Data Protection Commissioner (IDPC), Malta.

11. Security

Traffic is encrypted with TLS. Passwords are salted and hashed. Wallets are end-to-end encrypted (AES-GCM, PBKDF2-SHA256 key derivation) with keys derived on your device, and on the phone the key can be held in Android's hardware-backed Keystore behind your biometrics. No system is perfectly secure, but we hold as little of your data — and none of your secrets — as we can.

12. Children

The service is not directed at children under 16.

13. Changes

We may update this policy; a new version is posted here with a new "last updated" date.

14. Contact

Questions or requests: support@clearlogicassist.com.