Privacy policy
Effective 2026-11-15
Folnexo is an editor for reading, marking up, editing, filling in and signing PDFs in your browser. This policy explains what the Folnexo operator ("we") keeps, where, what for, and when it is deleted. Most of what you do stays in your browser, where we can't see it.
1. What stays in your browser
Whether or not you sign in, these are kept only in your browser (IndexedDB, localStorage, sessionStorage) and never sent to our server:
- PDFs you open, their edits, versions and attachments
- Your tables in Forms › Data (a SQLite file); with Google Drive connected, also in your own Drive
- Fonts you add (also in your own Drive when it is connected)
- Signing certificates and their keys, which can't be exported
- Your own OpenAI API key and settings for Ask AI
2. When you sign in with Google
Signing in gives us your Google account ID, name, email address and profile photo address, to make your account. You stay signed in with an HttpOnly cookie.
Documents you open while signed in (not the sample) are kept on our server as a copy with their edit log, so you can go on editing on another device. They are deleted when you delete them, or when you close your account and choose to delete its data. If you close it and keep the data, signing in again opens it as it was.
3. Sharing and collecting responses
- A shared PDF is a file in your own Google Drive, shared with anyone who has the link. Our server keeps no copy: it passes the file on from Drive, and records only the link's title, due date and settings.
- A respondent's name (or Google account, when they sign in) and answers stay on our server until your editor takes them into your table, and 30 days at most. Scores are kept as numbers only.
- Photos of work attached to a response (a PDF) are deleted when your editor takes them, and after 30 days at most.
- Copies you mark up and return are in your Drive; we keep their file ID.
- Approval requests: reviewers' names, decisions and comments.
- Signature requests: the signers' names you give, the Google name and email of signers who sign in, their signatures (deleted once the signed copy is made), when they consented and signed, reasons to decline, and the SHA-256 of the copy sent.
4. Google user data
Folnexo uses these Google APIs from your browser, and only with your permission:
- Google Drive (the drive.file scope): only files this app made or that you opened with it. To save documents, make copies for links, and keep your data file and fonts in step.
- Google Classroom (when you use its features): to list the classes you teach, read a class's student list (names) for per-respondent PDFs, post an assignment with your link, and read its submissions to give and return grades. Our server only handles which class and assignment a link was posted to, and, to send scores, the Google account ID of respondents who signed in.
Folnexo's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. Google user data is used only to provide the features above: it is not sold, not used for advertising, and not used to train general AI models. No person reads it except with your consent, for security, or as the law requires.
5. Information that goes to other services
- Ask AI, translation and quiz worksheets: with your own OpenAI key, the text of the pages you pick and your question go straight from your browser to OpenAI (asked not to be stored). They don't pass through our server.
- Read aloud: with Chrome's Google voices, Chrome sends the text it reads to Google. Voices on your device work on the device.
- Trusted time for digital signatures: only a hash of the signature goes to the time-stamping authority (DigiCert), through our server.
- Certificate status checks: certificates' serial numbers and issuer hashes go to the certificate authority's OCSP and CRL addresses, through our server.
- OCR (making scanned pages into text): the PDF goes to our OCR service, and is deleted once the result is fetched, within an hour at most.
6. Cookies and logs
We use a sign-in session cookie, a cookie that tells a respondent's browser apart (respondents who don't sign in), and a language cookie. No advertising or tracking cookies, no outside analytics.
Our server logs only the method, path, status and a trace ID of requests: never document text, names, emails, tokens or cookies.
7. Students and schools
When used in a school, student information is used only to provide this service: never for targeting advertising or training general AI models. What a student writes in a response, and their score, are seen only by the teacher who made the form.
8. Keeping, deleting, and your rights
You can delete what is in your browser (close or delete documents, or clear the browser's data). You can close your account yourself in Settings › Account; choosing to delete its data removes your documents, links, edit log and account. Responses you gave to someone else's form stay theirs.
You can ask to see, correct or delete your information, or to stop its processing: write to the contact below.
9. Security
Every connection is encrypted with HTTPS. Access to the server is limited to those who need it, and signing keys stay in your browser in a form that can't be exported.
10. Changes
When this policy changes, this page says so with its effective date; important changes are also announced in the service.
11. Contact
The operator's contact address isn’t set yet (NEXT_PUBLIC_EPE_CONTACT).