The short version
Most tools on this site run inside your web browser: your files are opened, processed and saved on your own device and never reach us. On the free plan your browser tells us when a task finishes, with its sizes and counts but never the file, so that the dayโs tasks can be counted. A few tools, marked โRuns on our serversโ and part of Pro, send the file to our servers because the work cannot be done in a browser; those files travel over an encrypted connection, are stored encrypted, are read by software only, and are deleted automatically, after the time the account chose. The AI tools, also part of Pro, send the text of a document, never the file, through our servers to Anthropic, which writes the answer and deletes the text within 30 days. Accounts are optional for the free tools and hold an email address, your name, a phone number if you give one, and a scrambled form of your password. Sign requests keep the document and a record of who signed it until the request is over, then for 90 days. Payments are taken by Paddle, not by us; we never see a card number. We set no advertising cookies, collect usage statistics only when you say yes, and sell nothing about you. The rest of this policy explains the details.
Who we are
UV pdfTool is made and operated by UV ResearchLabs (โweโ), a company established in Ireland. We are the controller of the personal data this website handles, under the General Data Protection Regulation (GDPR) and the Irish Data Protection Act 2018. We have not appointed a data protection officer; questions about personal data go to the address under โContactโ. We make no decision about you by automated means alone that has a legal or similarly significant effect on you.
Your files in the browser tools
When you choose a file for a browser tool, your browser reads it into its own memory and the tool works on it there, using code that this site delivers to your browser. Downloads are made on your device too. Closing the tab discards the file. No copy of your file, its text, its pictures or its properties is sent to our servers or to any third party. The AI tools, described below, are the one exception: they send the text of the pages you ask about, never the file.
The editor keeps the changes you have not saved yet in your browserโs own database, so that a closed tab or a crash does not lose them, and offers them back when you open the same file again. They can hold text and pictures of your document; they are found again by a fingerprint of the file, never leave your device, and are removed when you save, when you choose not to restore them, or after 30 days. The name you give for the comments you add is kept in this browser too, and put only in the comments you save. So are the words you add to your dictionary in a spell check, so that they are not flagged again; they are sent nowhere, and Spell check PDF lists them and takes them out. The details you save to fill forms with (your name, address, phone and the like) are kept in this browser in the same way, sent nowhere, and removed with Forget my details.
The readerโs Read aloud speaks with the voices of your device and browser. Most speak on the device. Some browsers also offer online voices, such as Chromeโs Google voices: with one of those, your browser sends each sentence it reads to its makerโs service, under that makerโs terms, never to us. The reader marks them online and chooses a voice on the device first.
Text recognition (OCR) and spell checking download language data from this site the first time they are used, in the same way that fonts and scripts are downloaded. The data flows one way, from us to you. Verify PDF signatures downloads the Adobe and EU trust lists from this site in the same way and checks the signatures against them on your device; it connects to nothing else.
Sign PDF with a certificate (part of Pro) opens your certificate file in your browserโs memory and signs there: the certificate, its password, its private key and the document are never sent. When you ask for a trusted timestamp, your browser sends our servers the SHA-256 fingerprint of the signature, 32 bytes that reveal nothing about the document or the people in it, and we pass it to a public timestamp authority (DigiCert, or Sectigo when it does not answer) and return the authorityโs answer. The fingerprint is not kept.
On the free plan, when a tool has made a file for you, your browser tells our servers that one task has finished: the toolโs name, the number of files, the size of the largest and the most pages among them. That is how the dayโs tasks are counted and the planโs limits checked. The fileโs name and contents are never sent. Reading a PDF in the viewer, or checking its signatures, is not a task and sends nothing.
Your files in the server tools
The tools marked โRuns on our serversโ (converting Office documents to PDF and back, converting to PDF/A and checking it, printing web pages, HTML files, Markdown and e-books to PDF, and drawing pages as SVG), and the stronger compression and the recognition of long scans when you choose our servers for them, are part of Pro. They upload your file, or fetch the page you named, and process it on servers we control. HTML files, Markdown and e-books are printed by a browser that runs none of their scripts and fetches nothing from the web. For these tools:
- The upload and the download use an encrypted connection (HTTPS), and the file is stored encrypted while it waits for and after processing.
- Processing happens automatically, on machines that run nothing but our tools, in a working folder of the jobโs own that is deleted as soon as the job ends. Nobody reads your files; they are handled by software only.
- The result is deleted from our servers as soon as your browser has fetched it. A file whose job did not finish, or a result you did not fetch, is deleted automatically after the period chosen in the account (one hour, one day, seven days or thirty days). A job whose files never arrive is deleted after twenty minutes.
- We record, for each job, the tool, the fileโs size and type, timings, the outcome and whether it counted as one of the dayโs tasks, without the fileโs name being used as anything but a label for you, so that we can keep the service fair and find faults. These records are deleted with the job.
- Each plan has a daily number of tasks. We count the tasks of each day per browser (by the cookie described below), per network address and per account. The address is stored only as a keyed hash that cannot be turned back into the address, with the dayโs count, and the counts are deleted after 60 days.
- Your files are not used for anything else: not to improve the tools, not to train software, and not for advertising.
Google Drive, Dropbox and OneDrive
A tool can open a file from Google Drive, Dropbox or OneDrive, and save its result there, if you ask it to. A small window of ours opens on an address of its own (the cloud picker), where you sign in with the service in the serviceโs own window and choose in the serviceโs own picker. The file then travels directly between the service and your browser; it never passes through our servers, and we receive nothing about your account there.
- Google Drive: the site asks only for access to the files you pick and the ones it saves (Googleโs โdrive.fileโ permission), and saves into a folder named UV pdfTool.
- Dropbox: opening uses Dropboxโs own Chooser, which shares only the files you pick; saving asks for access to an app folder, Apps/UV pdfTool, and writes only there.
- OneDrive: Microsoftโs own file picker shows your files; opening receives short-lived links to the files you pick, and saving writes to the folder you choose.
The access a service gives lasts as long as that window: it is kept only in the windowโs memory, never stored and never sent to our servers, and closing the window ends it. Signing in to OneDrive keeps the sign-in request and a one-time secret in the windowโs session storage until it closes (see the cookie policy). You can remove the siteโs access at any time in your Google, Dropbox or Microsoft account settings.
The browser extension
The UV pdfTool extension for Chrome, Edge and Firefox reads only the PDF you choose: a link you right-click, or the PDF open in the tab where you click its button. To read it, it uses the leave that click gives, or asks for leave to read that site when it needs it; you can take that back in the browserโs settings at any time. It hands the file to the toolโs page on our site in your browser, where it is treated as a file you added yourself. The extension sends the file nowhere else, keeps nothing, and collects no data about you or the pages you visit.
The sponsored card
On Free, a tool page may show one card marked โSponsoredโ: an advertisement we place ourselves, not one from an advertising network. Its words and picture come from our own servers. It stores nothing in your browser, and nothing about you goes to the sponsor or to anyone else. We count, for each card and each day, how many times it was seen (half of it in view) and how many times it was followed, without any address, identifier or anything else about the visitor. Following the card goes through an address of ours, which counts the click and then opens the sponsorโs site; the sponsor learns only that the visit came from this site, and from there its own privacy terms apply. Pro has no sponsored card.
The AI tools
Summarize PDF, Chat with PDF and Translate PDF are part of Pro. Your browser opens the PDF and takes its text out, reading scanned pages with OCR on your device first; the file itself is never sent. When you start a summary, ask a question or translate, the text that task needs (the pages you chose, the passages that match your question with your last three questions and answers, or the paragraphs of a page) goes over an encrypted connection to our servers, which pass it to Anthropic, PBC, in the United States, whose model Claude writes the answer. The answer comes back the same way and is shown on the page; our servers keep neither the text nor the answer.
Unless you turn it off, your browser first replaces the personal details it recognises in that text (email addresses; phone, payment card, Aadhaar, PAN, IBAN, US Social Security and Irish PPS numbers; and any names or other words you add) with markers such as โฆPHONE 1โง, and puts the real values back into the answer on your device. The list of what each marker stands for never leaves your device. Details it does not recognise, such as a name you did not add, are sent as they are.
Anthropic processes the text on our behalf under its commercial terms: it does not use it to train its models, and deletes it within 30 days, except where its safety systems flag a request as breaking its usage policy, which it may keep longer to enforce that policy, or where the law requires it to keep it. A short notice says this before the first use.
For each request we record the account, the kind of task, the AI credits it cost, the tokens it used, what it cost us and whether it worked, with the time; never the text, the questions or the answers. These records keep the credits right and the costs in check, appear in the copy of your data the account page gives, and are deleted after 400 days; when an account is deleted, its records lose the link to it.
Accounts and signing in
You can use the free tools without an account. An account is needed for Pro, for gift codes and for sending documents for signature. Accounts are for people aged 16 and over (18 and over in India); if you believe a child under 16 has opened one, write to us and we will delete it. To create or use an account we hold:
- Your email address. When you create an account we email you a link that proves the address is yours; it works once and for a short time. We also write to it about the account itself: a welcome, the links you ask for (a new password, a copy of your data, a change of address), security alerts such as a new sign-in, sign requests you send or are asked to sign, your purchases and subscription, a pass or AI credits about to end, and notices about the accountโs standing or its deletion after long inactivity. News about the site and offers are sent only if you ticked the box for them, and each such mail has a link that stops them. We keep a log of the mail we send (the address, which mail it was, its subject and whether it was delivered or bounced) for a year, to answer questions about mail that did not arrive; when the account is deleted, the address in that log is blanked. An address that unsubscribed from our news, whose mail bounced, or whose owner marked our mail as spam goes on a list that holds back our news to it, until its owner asks for news again.
- Your name, and a phone number if you give one. The form that creates an account asks for your name, so that the account page, our mail and our support know what to call you; a sign-in with Google, Apple or your companyโs sign-on gives us the name it holds instead. The phone number is optional: we use it only to reach you about your account (for example about a problem you reported or a payment that failed), never for advertising, and we do not pass it on. It is checked against the numbering rules of its country, not by a call or a text. You can change or remove either on your account page at any time, and both are deleted with the account.
- Your password, scrambled. We never store the password itself, only a salted hash of it (scrypt), which is enough to check a sign-in and useless to anyone who copies it. When you choose a password, your browser checks it against the public list of passwords exposed in past data breaches by sending the first five characters of its SHA-1 fingerprint to the Pwned Passwords service of Have I Been Pwned; the password itself never leaves your device, and that service cannot learn it from those five characters. Ten wrong passwords in fifteen minutes lock sign-in for fifteen minutes; the counter and the lock time are stored with the account.
- Sign in with Google, if you choose it: Google tells us the address of your Google account, the name on it and a stable identifier for it, and we store those so that the next sign-in finds the same account and the account has your name. We keep nothing else from Google, and Google learns only that you signed in to this site.
- Single sign-on, if your company set it up for its team: you sign in on your companyโs own sign-in page, and its identity provider tells us your address, your name and a stable identifier for you there, which we store so that the next sign-in finds the same account. A team that sets this up gives us its providerโs address and client details (the client secret is kept sealed with a key of our own), and proves its email domain with a DNS record that we look up. If the team requires it, addresses at its domain can sign in only this way, and people who sign in this way may join the team.
- Sign in with Apple, if you choose it: Apple tells us a stable identifier for your Apple account and an address, which is either your own or one Apple makes to pass mail on to you without showing yours (โHide My Emailโ), and, the first time only, the name you let it share. We store those so that the next sign-in finds the same account. We receive nothing else from Apple, and Apple learns only that you signed in to this site.
- Passkeys, if you add them: the public half of each passkey, a counter the passkey raises with each use, whether it is synced between your devices, the name of the device that made it, and when it was added and last used. The passkey itself, and the fingerprint, face or screen lock that unlocks it, stay on your device or in your password manager and never reach us.
- Our apps, if you sign in to one: which app, the device name it gives, the country the sign-in came from, when it was signed in and last used, and scrambled copies of the tokens that keep it signed in. Each app shows on the account page beside your browsers, where you can sign it out; one unused for 90 days is signed out by itself.
- A session cookie that keeps you signed in on that browser for up to 30 days, and a record of when the account was made. For each browser signed in we keep its self-description (โuser agentโ), its country, a keyed hash of its IP address, and when it signed in and was last used, so that the account page can list your browsers, you can sign each one out, and we can warn you of a sign-in from somewhere new. The account also notes the day, the language and the country it was last used in, for the language of our mail and for those warnings.
- Two-step sign-in, if you turn it on: the secret your authenticator app shares with us, sealed with a key of our own, and your recovery codes, scrambled. Both are deleted when you turn it off.
- Your consents: which version of the terms and of this policy you accepted, and whether you want news by mail, each with its time, so that we can show what was agreed.
- Your Pro and your AI credits: where the accountโs Pro comes from (a subscription, a pass, a gift code or our support) and until when; each lot of AI credits with its expiry, what was spent and returned, and credits taken back after a refund of a purchase.
- Who invited you, if you opened the account through someoneโs invitation link: the code of that link, so that invitations can be counted. Nothing is given for it, and the person who invited you is not told who you are.
- Your retention choice: how long the files of your jobs are kept.
- Your saved workflows, with Pro: the name of each and its steps, which tool and which settings, never a file and never the password Protect PDF sets, until you delete them or the account. They run in your browser.
- Our care of the account: the days on which the account was used, kept for 400 days, to count how many accounts are in use; notes and labels our support staff add to keep track of a conversation with you, which go with the account; when our support staff change an account, for example to restore Pro after a fault or to answer a request, what they did, the reason and the time, kept for two years with the accountโs identifier only; and requests for a copy of your data or for its erasure, with their dates, kept for six years to show that they were answered. An account that breaks the terms may be suspended, and the reason is noted with it.
You can delete the account yourself on the account page. Deleting it cancels a running subscription at Paddle and removes the address, the password hash, the passkeys, the sessions and the apps signed in, the AI credits and their history, every remaining job and file, and every sign request you sent, at once. Records of purchases stay, without the account, for as long as accounting law requires (see โHow long we keep dataโ).
Paying for Pro
Purchases are made on a checkout page of Paddle.com Market Limited (โPaddleโ), our reseller and merchant of record, which is based in the United Kingdom and has an Irish entity for sales in the European Union. Paddle collects your payment details, your billing country and any tax number, charges you, issues the invoice, collects the tax that applies where you are, and handles refunds, under Paddleโs privacy policy. We never see or store a card number.
- We give Paddle your email address, the product you chose and the identifier of your account, so that Paddle can send the receipt and tell us which account the purchase belongs to. While we offer a student and teacher price and the address is at a school or university, which we tell from its domain alone, we also ask Paddle to take that discount off Pro, and keep with the purchase a keyed hash of the address that cannot be turned back into it, so that one account per address has the discount in a year.
- Paddle tells us, by signed messages to our servers, when a payment is completed, a subscription changes, or a payment is refunded or reversed. We store Paddleโs identifiers for your customer record, each transaction and each subscription, the product, the amount and currency, the status, and the time of each event, so that we can give the account its Pro or its AI credits, show your purchases on the account page, and end a pass or take back a packโs credits after a refund.
- Paddleโs customer portal, reached from the account page, is where you see invoices, change the payment method and cancel a subscription; it is Paddleโs page under Paddleโs policy.
- An address whose payment was reversed through a bank is marked, so that it cannot buy again: we store a keyed hash of the address in a normalised form (lower case, without a โ+tagโ, and without the dots Gmail ignores), kept after the account is deleted. The hash cannot be turned back into the address.
Teams
A team is an account that pays for seats, and the accounts that join it by invitation.
- Everyone in a team sees the other membersโ names and email addresses, their roles and when they joined. The owner and the admins also see the open invitations and the teamโs activity: who invited, joined, left or removed whom, changed a role or the seats, and when the subscription started or ended.
- An invitation keeps the address it was sent to, the role and a fingerprint of the linkโs secret part; the link itself is only in the email. Invitations are deleted 90 days after they are accepted, withdrawn or expire.
- The teamโs AI credits are shared by its members. The record of each AI request names the member and the team, with counts and costs only, as for any AI request.
- Sign templates and workflows that a member shares can be used by the teamโs members until the member stops sharing them or leaves the team; they stay the memberโs own.
- The teamโs subscription is paid by the account that started it, through Paddle as described above. When the ownerโs account is deleted, the team passes to its longest-standing admin, or member; a team with nobody else in it is deleted with it. Deleting a team deletes its membersโ places, invitations, activity and AI credits.
The developer API
If you use our API from your own software, its jobs are handled as described above for the server tools, and their files are deleted 24 hours after the job ran. In addition:
- Each API key is shown to you once; we keep a fingerprint of it, its first characters and last four to tell it apart, its name, what it may do, the address ranges you allowed, and when it was made, last used and revoked.
- If you set a webhook, we keep its address and its signing secret, sealed with a key of our own, and a record of each message we sent to it (the event, the job, when, and what your server answered) for 30 days. The messages carry the jobโs id, tool, state and the names and sizes of its results, never a file or a download link.
- We count the API tasks you buy and spend, as for any purchase, and write to you when four fifths and all of them are used.
Sign requests
When you send a document for signature (part of Pro), we store it with the request so that each signer can open it from their link, and we keep a record of the signing, which is what makes the signature worth something as evidence:
- For the sender: the name and email address of the account, and the IP address and its country when the request was sent.
- For each signer: the name and email address you gave; the signature and initials they adopted (the strokes they drew, the name typed in the style they chose, or the picture they uploaded) and how they made them, including whether a finger, a mouse or a pen drew them and whether they drew on a phone through a one-time code; the consent text they accepted, in the language they read it, with its version and time; and for each step (sent, delivered to their mail server, opened, access code entered, reminded, signed, declined, downloaded, link locked or unlocked) the time, the IP address with its country, and the browser.
- When the sender sets an access code for a signer, we keep only a one-way hash of it (scrypt), never the code itself, and never put it in an email; the sender gives it to the signer some other way. Wrong codes are counted until the sender unlocks the link; five lock it, and we tell the sender by email. The right code lets that browser open the link for twelve hours, through a cookie that only the linkโs own pages receive.
- The signed copy is the document with those fields drawn in and a certificate of completion added that lists this record and the SHA-256 fingerprints of the document as sent. The finished file is then sealed with a document timestamp from a public timestamp authority (DigiCert, or Sectigo or FreeTSA when it does not answer), which receives only the fileโs SHA-256 fingerprint, never the file or anything about the people in it.
- The sender sees the request and its record and can download the audit report; each signer sees the document through their own link, which is private to them and is replaced by a new one when a reminder is sent; after completion, every party receives the signed copy and its fingerprint by email.
- Signers do not need an account. Their name and address are used only for this request: to send them the link, reminders and the finished copy, and to appear in the certificate.
- A drawing made on a phone through a one-time code is kept on our server only until the signer signs, a day at most.
- The document, the fields and the record are kept until the request is completed, declined, cancelled or has expired, then for 90 days so that every party can download the signed copy, and are then deleted. The sender may keep a completed requestโs files for longer, until they delete them or their account, and may delete an ended request sooner. A draft that was never sent is deleted after a day.
- For the public verify page, the SHA-256 fingerprint of each signed copy is kept with its request ID, the time of completion, its number of pages and of signers and its timestamp, for seven years after completion, even when the request itself is deleted. That record holds no names, addresses or content. The verify page computes the fingerprint of a file in the visitorโs browser and sends only that fingerprint.
- Documents sent for signature are stored encrypted with the same provider as the server toolsโ files; the invitations, reminders and the completion mail are sent through Resend, which tells us whether each invitation reached the signerโs mail server.
Client documents collected for a filing
The client workspace (part of Pro) lets an accountant, bookkeeper or consultant collect the documents a filing needs from their clients. For each client folder we store the clientโs name, email address and postal address as the account typed them, the list of documents asked for with its rules, and the files the client or the account uploads: the file itself, its name, size, page count and fingerprint, and whether it met the rules. Every step (asked, link opened, file received or replaced, accepted, sent back, submitted) is recorded with its time and, for the clientโs own actions, the IP address with its country and the browser. The request mails go to the client through Resend, with the accountโs own address as the one to reply to. A client never needs an account: the link in the mail is their key, works for at most 90 days, and is replaced by every reminder.
The account controls these files: it can delete a clientโs folder at any time, which removes every file and record at once, and when it marks a folder submitted the files are deleted 90 days later. The files are stored encrypted with the same provider as the server toolsโ files. We act as the accountโs processor for them: a client who wants a file removed should ask the accountant, who can do it in a click, and can also write to us.
Cookies, storage and your privacy settings
The site stores a few things in your browser, all set by this site and by nobody else. The cookie policy lists every one of them with its purpose and lifetime. In short:
- Necessary, set without asking because the site cannot work without them: a cookie that remembers your privacy choice, a cookie with a random number that identifies your browser to us (for counting the free planโs daily tasks and for seeing your own jobs), the session cookie when you sign in, a short-lived cookie that protects a sign-in with Google, Apple or your companyโs single sign-on, the choices of the sign-up form until the emailed link creates the account, what your Pro allows so that it works offline, a note or an announcement you already closed, the state of a sign-in to OneDrive in the cloud picker window while it is open, and the offline copy of the tools.
- Statistics, only with your consent: a random number for the sitting, kept in session storage and forgotten when the tab closes, so that the usage statistics can count visits.
The first time you visit, a notice asks you to accept or reject statistics, with both choices and โSettingsโ given the same weight; nothing is collected until you choose. The at the foot of every page let you change your mind at any time, with effect at once. A browser that sends the Global Privacy Control signal is treated as having said no unless you say yes in the settings. The language of the site is in its address, so no cookie is needed for it. No cookie is used for advertising or shared with anyone.
What we receive
Using the site sends the following to us or to our hosting provider:
- Server logs. Like every website, our hosting provider records each request: the address of the page or file requested, the time, your browserโs self-description (โuser agentโ) and your IP address. These logs exist to keep the site running and secure, and are kept for a limited time by the provider.
- Usage statistics, with your consent. We measure which pages are visited, which tools are used and whether they succeeded, whether results were downloaded, and how the site performs. Each measurement is recorded as an event: the page or the tool, the outcome, file sizes and timings, the country, the kind of device and browser, the site you came from, whether you were signed in, the random number of the sitting described below, and a visitor code for the day, a keyed hash of your IP address and browser that changes at midnight (UTC) and cannot be turned back into either. The events are kept for 90 days and then only as daily totals. The measurement stores no IP addresses, never records a fileโs name or contents, does not follow you to other sites, and is not used to find out who you are. Our servers discard such measurements when they arrive without the consent cookie or with the Global Privacy Control signal.
- Error reports. If something breaks in your browser, a short report is sent to us so that we can fix it: the error message, the part of the code involved, the page you were on, the site language and your browserโs self-description. Error reports never include your file or anything from it, store nothing in your browser and carry no identifier; they are counted in the statistics only with your consent.
- Mail you send us. Mail to our support address is received by Resend, which passes it to the mailbox we read it in. We keep your message as long as the conversation needs it, and use it for nothing else.
What we do not do
- We do not require an account for the free tools, and an account holds only what is listed above.
- We do not show advertising and use no advertising or tracking cookies.
- We do not sell, rent or share personal data.
- We do not use your files for anything, including training software.
- We do not store card numbers; Paddle takes the payment.
Why we process this data, and on what basis
- To provide what you asked for (Article 6(1)(b) GDPR): running the server tools on the files you give them, sending the text you give the AI tools to Anthropic for the answer, keeping your account, carrying the sign requests you send, and supplying what you bought.
- Our legitimate interests (Article 6(1)(f)): keeping the site working, fair and secure, including the daily count of tasks, the mark on an address that reversed a payment, the server logs and the error reports. You may object to processing on this basis; write to us.
- Your consent (Article 6(1)(a), and the ePrivacy rules on storage in your browser): the usage statistics, which you can withdraw at any time in the privacy settings.
- Legal obligations (Article 6(1)(c)): keeping records of purchases for as long as tax and accounting law requires.
Who else is involved
The site is hosted by Vercel Inc., which operates the servers that deliver the pages and receive the requests described above. Files given to the server tools and documents sent for signature are stored with Cloudflare, Inc. (R2 object storage, in a bucket restricted to the European Union) and processed on servers we rent from Fly.io, Inc. in Amsterdam; job, account, billing and sign-request records live in a database run by Supabase, Inc. in London; account links, sign-request invitations and the mail you send to our support address go through Resend, Inc.; payments are taken by Paddle.com Market Limited as merchant of record; checking a new password against known breaches uses the Pwned Passwords service of Have I Been Pwned, which receives five characters of a fingerprint and nothing else; signing in with Google or Apple involves Google LLC or Apple Inc. as described above, and single sign-on the identity provider your company chose, acting for your company; the text given to the AI tools is processed by Anthropic, PBC in the United States, as described above. Each of them processes data on our behalf under a contract, or, in Paddleโs case, as a controller of the payment in its own right, under its own privacy terms. Some of them are outside the European Economic Area; transfers rest on the European Commissionโs standard contractual clauses or on an adequacy decision (the United Kingdom). No other company receives personal data from this site. The timestamp authorities that seal finished sign requests (DigiCert, Inc., or Sectigo Limited or FreeTSA when it does not answer) receive only a fingerprint of the file, and those that timestamp a signature made with your own certificate (DigiCert, or Sectigo) only a fingerprint of the signature; neither says anything about anyone. When you open a file from, or save one to, Google Drive, Dropbox or OneDrive, you use Google LLCโs, Dropbox, Inc.โs or Microsoft Corporationโs service directly, under its own privacy terms, as described under โGoogle Drive, Dropbox and OneDriveโ; none of them receives anything from us.
How long we keep data
Server logs and error reports are kept by our hosting provider for at most 30 days, and are then deleted. Usage statistics are kept as single events for 90 days, and after that only as daily totals that name no visitor. Files given to the server tools are deleted as described above, and their job records with them; the daily counts of tasks are deleted after 60 days. The log of mail we send is kept for a year, the days an account was used for 400 days, and the record of what our support staff changed for two years. Sign requests are deleted 90 days after they end unless the sender keeps them, drafts after a day; the fingerprint record of a signed copy, without names or content, is kept for seven years. A client folderโs files are deleted 90 days after the folder is marked submitted, or at once when the account deletes the folder or itself. Account data is kept until you delete the account or until it has been unused for two years; an app that has not been used for 90 days is signed out and its record deleted. Records of AI requests, which hold counts and costs but no text, are deleted after 400 days. A teamโs activity is kept for two years, its invitations 90 days after they end, and both go with the team. Records of purchases, with the amount, currency, product and Paddleโs identifiers but without the account once it is deleted, are kept for six years, as Irish tax and company law requires, and so is the mark on an address that reversed a payment.
Your rights
Under the GDPR you may ask to see the personal data we hold about you, to have it corrected or deleted, to restrict or object to its processing, and to receive it in a portable form; where processing rests on consent you may withdraw it at any time, with effect for the future. Everything we hold about an account is shown on the account page, where the account can also be deleted and the privacy settings changed. Logs and reports cannot be tied to a person, so there is usually nothing more we can look up; still, write to us and we will help where we can. If you were asked to sign a document and want the record of it removed before the 90 days are over, write to us or to the person who sent it, who can cancel the request. You also have the right to complain to a supervisory authority: in Ireland, the Data Protection Commission (dataprotection.ie), or the authority of the country where you live; in the United Kingdom, the Information Commissionerโs Office.
If you live in India, the Digital Personal Data Protection Act 2023 gives you the right to see, correct and erase your personal data, to nominate someone to exercise those rights for you, and to complain, first to us and then to the Data Protection Board of India. Our grievance contact is the address under โContactโ. Wherever you live, the rights your own privacy law gives you are honoured on request: write to us.
Changes to this policy
When the site changes in a way that touches personal data, this policy changes with it, and the date at the top moves. A change that matters to accounts is announced by email.
Contact
Questions about this document can be sent to support@uvpdftool.com.