Skip to content
PDFVelora

Privacy policy

This policy explains what personal data PDFVelora collects on pdfvelora.com, why, how long we keep it and what your rights are. We collect as little as we can: many tools work entirely in your browser, and the files we receive are deleted automatically after a few hours unless you choose to keep them.

Who we are

PDFVelora is operated by Amine AIT EL GHACHI, an individual based in Rabat, Morocco. We are the controller of the personal data described in this policy. For any question about your data, write to pdfvelora@gmail.com. More details are in our legal notice.

What we collect

If you use PDFVelora without an account

  • A guest identifier: a random identifier in a signed cookie, which links you to your files and tasks and counts your free tasks for the day.
  • The files you upload and the results we produce, for the tools that run on our servers (see "Your files" below).
  • Your IP address, used briefly to limit abuse (see "Technical data").

If you create an account

  • Your email address, and your name if you give it.
  • Your language and your plan and subscription status.
  • Sign-in data: the sessions that keep you signed in, and the codes and links we email you to sign in or confirm a change.
  • If you sign in with Google: Google sends us your name, email address and profile picture, and we store the sign-in tokens Google issues. Google only does this when you choose that option.

What you create with PDFVelora

Depending on the features you use, we store:

  • files you save to My documents, your folders and the share links you create (we store only a fingerprint of each link, and of its password if you set one);
  • signatures and initials you save for reuse;
  • unsaved work in the PDF editor;
  • agreements you build from a template, and drafts of government forms you choose to save (form drafts are encrypted, as they can contain ID numbers);
  • your questions and the answers in Chat with PDF, and the passages of text extracted from the document to answer them;
  • transcripts of your recordings.

Signature requests

When you send a document for signature, we store the document, its title and message, the fields you place and the name and email address of each signer. For each signer we record what they fill in (signature images, text, dates) and an audit trail of every step: the time, the IP address, the browser (user agent) and a fingerprint (SHA-256) of the document, as well as a reason if they decline. If someone asks you to sign a document, the sender gave us your name and email address.

Usage records

We record which tool was used and when, and quantities such as pages, AI credits or audio minutes, to apply the limits of your plan. For AI tools, we record the model used and the number of tokens, not the content. For tools that run in your browser, we only record that a task took place, so it can count towards your daily limit.

Payments

Payments are handled by Paddle.com, our reseller and merchant of record. Paddle collects your payment and billing details (such as your name, email address, country and payment method) and processes them as an independent controller under its own privacy policy. We never see or store your card number. We keep the identifier of your Paddle customer record and the details of your subscription: plan, status, billing interval, billing period and, for Business, the number of seats.

Teams

If you subscribe to Business, we store the email addresses of the people you give seats to, and their role in the team.

When you contact us

If you write to us through the contact form, we store your name, your email address, the subject and category you choose, your messages and our replies, and, if you are signed in, the account the request comes from. We answer by email, with a link through which you can follow the request and reply. If you email us directly, we keep your message to handle your request.

Technical data

Our servers use your IP address to limit the number of requests (for example sign-in attempts, uploads or downloads of shared files); this data expires within one hour at most. Our servers also keep technical logs, such as error messages, which mainly contain internal identifiers. When something goes wrong on the website or while processing a file, an error report is sent to Sentry so we can fix the problem. It contains the type of error and where it happened in our code, the page or feature concerned (with the secret part of links and the values in web addresses removed), your browser and operating system, and the version of PDFVelora. Error reports never contain your files, their names or contents, what you type in forms, your cookies or your email address, and they are sent without your IP address. We don't use advertising tools.

If you accept the "Analytics" category in the cookie banner, we measure how PDFVelora is used with PostHog: the pages you visit and the page you came from (with the secret part of links and the values in web addresses removed), your browser, type of device and screen size, and events such as starting a tool, a task succeeding or failing (with the tool and the error code), downloading a result, starting a checkout, a subscription starting, sending a signature request (with the number of signers) and creating an account. If you are signed in, these statistics are linked to your account's internal identifier, never to your email address or name. We never send PostHog your files, their names or contents, or what you type. Our servers forward these statistics to PostHog without your IP address. Nothing is sent to PostHog, and none of its cookies is set, until you accept; you can withdraw your consent at any time with the "Cookie settings" link at the bottom of every page, which stops the measurement and deletes PostHog's cookie and stored data from your browser.

Security log

We keep a log of security-relevant events: sign-ins and sign-outs, account creation and changes to your account (such as a change of email address), data exports, account deletion requests and deletions, the creation and revocation of share links, new support requests, changes to your subscription, and actions taken by our administrators. Each entry records what happened, when, the account concerned, the IP address and the browser (user agent). Entries never contain the content of your files, passwords or what you type in forms.

How we use your data and why

  • To provide the service you ask for (performance of our contract with you): creating and running your account, processing your files, keeping what you save, sending signature requests and share links, and sending the emails the service needs (sign-in codes, confirmations, signature request notifications, and a reminder before your subscription renews).
  • To bill paid plans (contract), and to keep accounting and tax records (legal obligation).
  • To keep PDFVelora secure and fair (our legitimate interest): scanning uploads for viruses, limiting requests and enforcing plan limits, preventing abuse and fraud.
  • To keep a security log (our legitimate interest): protecting accounts, detecting and investigating fraud and misuse, and establishing, exercising or defending legal claims.
  • To provide a reliable audit trail for signatures (contract, and the legitimate interest of senders and signers in being able to prove who signed what and when).
  • To answer your messages and support requests (our legitimate interest, or the contract if your message concerns your account or your subscription).
  • To find and fix errors (our legitimate interest in providing a reliable and secure service): error reports sent to Sentry.
  • To understand how PDFVelora is used and improve it (your consent, given in the cookie banner): usage statistics measured with PostHog.
  • To comply with the law (legal obligation), for example when an authority lawfully requires it.

Where we rely on your consent, you can withdraw it at any time. We don't sell your data, we don't use it for advertising and we don't use your files to train AI models.

Your files and how long we keep them

Tools that run in your browser

Many tools process your file directly in your browser, so the file never reaches our servers. Some tools process smaller files in your browser and upload larger files, or files the browser can't open, to our servers.

Files sent to our servers

Uploaded files go directly to our file storage through short-lived links. Each upload is checked for viruses by ClamAV, running on our own servers; a file that is infected or can't be scanned is deleted. Files are then processed by our own servers, each task in an isolated worker process; tools that don't need the internet run with network access disabled. If you give us a link instead of a file (for example to convert a web page or transcribe a recording), our servers download it.

How long we keep data

DataKept for
Uploads and results, without an account2 hours
Uploads and results, with an account (all plans)24 hours, unless you save them to My documents
Uploads that were never completedAbout 1 hour
Files in My documents, saved signaturesUntil you delete them or your account
Agreements and saved form draftsUntil you delete them or your account
Chat with PDF passages and conversations, unsaved editor workDeleted with the file they belong to
Signature requestsSigners can sign for 30 days after sending. Completed, declined, cancelled or expired requests are deleted 365 days after their last activity; drafts left untouched for 30 days are deleted. You can delete a request earlier.
Sign-in sessions30 days
Sign-in codes and links15 minutes
Email change and account deletion links60 minutes
IP addresses used to limit requests1 hour at most
Security log entries365 days
Support requests and their messages2 years after the last message
Error reports (Sentry)90 days
Usage statistics (PostHog, only with your consent)1 year

An automatic cleanup runs several times an hour, so expired files are deleted shortly after the time shown.

Sharing

Anyone who has a share link can download the file. For documents in My documents, you can protect a link with a password, make it expire after 1, 7 or 30 days, and revoke it at any time. A link to a result that isn't saved stops working when the file expires.

Deleting your account

You can delete your account from your settings. We email you a confirmation link, valid for 60 minutes. When you confirm, your account is deleted straight away: your paid subscription is cancelled immediately at Paddle, so you aren't charged again (the rest of the period you paid for isn't refunded automatically: see our refund policy), your stored files are deleted from our storage, and the signature requests you sent, their audit trails and the rest of your account data are deleted. Usage records are kept without any link to your account. Security log entries about your account, including the deletion itself, are kept until the end of their retention period, without IP address or browser. Support requests you sent are kept until the end of their retention period, with the name and email address you gave in them, but no longer linked to an account. Copies already sent to other people, such as signed documents emailed to signers, stay with them, and Paddle keeps its own payment records.

AI features

Chat with PDF, Summarize PDF, Translate PDF, the AI writing assistant and the AI summary of a transcript use third-party AI models. Chat with PDF, Summarize PDF, Translate PDF and the AI writing assistant say what they send, and to whom, next to their button. For every AI feature, nothing is sent before you click its button. We send the text of the document, never the file itself.

  • Summarize PDF and Translate PDF send the document's text to Anthropic's Claude.
  • Chat with PDF sends the document's text to Voyage AI to index it. Then, for each question, the question, recent messages and the most relevant passages (or the whole text of a short document) go to Anthropic's Claude.
  • The AI writing assistant sends the text you enter to Anthropic's Claude. If you open a file in it, the file is read in your browser and only its text is sent.
  • The AI summary of a transcript sends the transcript to Anthropic's Claude.

Transcription itself runs on our own servers, with open-source speech recognition (Whisper) and speaker detection (pyannote) models: the recording isn't sent to an AI provider.

AI answers can be wrong: check important details against your document.

Who we share data with

We use the following service providers, which process data on our behalf to run PDFVelora:

  • Our hosting provider, [to be completed]: the servers that run the website, the database and file processing.
  • Cloudflare (R2): storage of uploaded files and results.
  • Resend: delivery of our emails.
  • Paddle (Paddle.com Market Limited): reseller and merchant of record for paid plans (checkout, payments, invoices, sales tax). For payment data, Paddle acts as an independent controller under its own privacy policy.
  • Anthropic: the Claude AI model, for the AI tools described above.
  • Voyage AI: indexing of documents for Chat with PDF.
  • Sentry (Functional Software, Inc., United States): error reports from the website and from file processing, stored in the European Union (Frankfurt, Germany).
  • PostHog (PostHog Inc.): usage statistics, only if you accept analytics cookies, stored in PostHog's EU Cloud (Frankfurt, Germany).

If you choose to sign in with Google, Google processes your sign-in under its own privacy policy.

Data is also shared with other people when you ask for it: the signers of your signature requests (they see the document, and every participant receives the signed document with its audit trail), the people you send a share link to, and the members of a Business team, who can see the files saved in the team's shared space.

We may also disclose data when the law requires it, for example to answer a lawful request from an authority.

International transfers

Some of our service providers may process data outside your country, including outside the European Economic Area, for example in the United States. Where the law requires it, these transfers rely on appropriate safeguards, such as an adequacy decision or the standard contractual clauses adopted by the European Commission. You can ask us for more information at pdfvelora@gmail.com.

Security

  • Connections to PDFVelora are encrypted with HTTPS (TLS).
  • Upload and download links are short-lived (15 minutes to upload, 5 minutes to download).
  • Every uploaded file is scanned for viruses before it can be used.
  • Files are stored in Cloudflare R2, which encrypts all stored data (AES-256).
  • Saved form drafts, saved signature images and the values signers fill in are additionally encrypted by our application (AES-256-GCM).
  • Documents are processed in isolated worker processes, and tools that don't need the internet run with network access disabled.
  • Security-relevant events are recorded in a security log (see "Security log" above).
  • Share links, signer links and confirmation links are stored only as fingerprints, and share link passwords are stored hashed.
  • Files are only available to the account or guest session that created them, unless you share them.

No system is perfectly secure, but we work to protect your data and limit what we keep.

Your rights

Depending on the law that applies to you, in particular the GDPR, you have the right to:

  • access your personal data and get a copy of it;
  • rectify inaccurate data;
  • erase your data;
  • restrict how we use it;
  • object to processing based on our legitimate interest;
  • receive your data in a portable format (portability);
  • withdraw your consent at any time, where we rely on it.

To get a copy of your data (access and portability), sign in and open Dashboard → Settings, then choose "Download your data": you receive a ZIP file with your account data in JSON format, along with your saved documents, your saved signatures and your completed signed documents.

You can also do much of this yourself: change your email address in your settings, delete files, signatures, agreements and drafts, and delete your account. For anything else, write to pdfvelora@gmail.com. We may ask you to prove your identity, and we answer within the time limits set by law (one month in general under the GDPR).

You also have the right to lodge a complaint with a supervisory authority, for example the data protection authority of the country where you live or work.

Cookies

We use the cookies and similar technologies that PDFVelora needs to work or to remember your choices, such as your language, and, only if you accept them, analytics cookies from PostHog (see "Usage statistics" above). Read our cookie policy for the full list.

Children

PDFVelora is not directed at children under 16, and we don't knowingly collect their personal data. If you think a child has given us personal data, contact us and we will delete it.

Changes to this policy

We may update this policy when our service or the law changes; the date at the top shows the latest version. We will tell you about significant changes by email or on the website before they apply.

Contact

For any question about this policy or your personal data, write to pdfvelora@gmail.com or use the contact form. You can also read our terms.