Privacy policy for web2print.app, a service of Data Handler LLC. Effective date: October 24, 2026List of subprocessors
1. Who we are and what this policy covers
1.1 web2print.app (the "Service") is operated by Data Handler LLC, 573 Old Franklin Rd, Stahlstown, PA 15687, USA ("we", "us"). This policy explains what personal data we collect when you visit web2print.app, buy a license, or use the Service (the studio, the API, webhooks and the desktop app), why we collect it, who we share it with, how long we keep it and what you can do about it.1.2 For account, billing, usage and security data we decide how the data is used (we are the "controller"). For the files and data your company puts into the Service ("Customer Content", defined in our Terms of Service), your company decides, and we process it only on its instructions to provide the Service (we are the "processor"). If you are a member of someone else's workspace, that company is responsible for the Customer Content it holds about you.1.3 Questions or requests: privacy@web2print.app.
2. What we collect
2.1 Account details: name, email address, password (stored only as a one-way hash), time zone, the workspace you belong to and your role (owner, admin or member), and invitations you send or receive.2.2 Billing details: company name, billing contact, any address details you give us for invoices and tax, licenses bought, invoices, payments, refunds and payment status. Card and bank account details are collected and held by Stripe, our payment processor; we keep only what Stripe returns to identify the method (such as the card brand and last four digits). For checks, we keep the payment reference and a scan of the check.2.3 Mobile phone number, only if you turn on two-step sign-in. We keep the number, the date you turned it on, and hashed copies of your one-time codes and backup codes.2.4 Sign-in and security records: when you sign in and out, the IP address and a browser fingerprint for each sign-in, two-step code attempts, active sessions, paired computers (name, who they belong to, when last used), and API keys (name, scope, rate limit, when last used).2.5 Usage records: each billable job (which app, how many PDF pages or approved runs, which template or file, who or which API key started it, when, and whether it succeeded), concurrent-session use, storage totals, and limit notices sent.2.6 Activity log: an append-only record of important actions in a workspace, such as sign-ins, members invited, joined, changed or removed, API keys created, rolled or revoked, licenses added, changed or ended, templates uploaded or deleted, batches started or canceled, and files deleted. Each line records who did it and when. Workspace owners and admins can see and export it.2.7 API and webhook records: API requests (time, path, key, IP address and result) and webhook deliveries (event, destination, attempts, the response code and the first part of your server's response).2.8 Messages: emails and support requests you send us, with their headers.2.9 Technical data: when you visit our pages, our servers record your IP address, the page requested, date and time, browser and operating system, and the referring page.2.10 We do not collect special categories of personal data on purpose, and we do not buy personal data from data brokers.
3. Customer Content
3.1 Customer Content is your templates, artwork, PDFs, images, fonts, color books, data files (for example a CSV of names for business cards), job details and every output the Service makes. It can contain personal data about your own customers or staff.3.2 We use Customer Content only to provide the Service to your workspace: to store it, check it, render and convert it, show previews, and deliver outputs to you, your integrations and your paired computers. We look at it only when you ask us to (for example in a support request), when needed to keep the Service secure or working, or when the law requires.3.3 No AI and no training. The Service contains no artificial intelligence or machine learning features. We do not use Customer Content, or any personal data, to train, test or improve any AI or machine learning model, and we do not give it to anyone who would.3.4 We do not sell Customer Content or personal data, use it for advertising, or share it with other customers.
4. Text messages (two-step sign-in)
4.1 Two-step sign-in is optional and off by default. If you turn it on in Settings, Security, you agree to receive one-time sign-in codes by text message from web2print.app (Data Handler LLC) at the mobile number you give us. We text a code to confirm the number when you turn it on, each time you sign in with your password, and when you ask for a new code. A typical message reads: "Your web2print.app sign-in code is 123456. It expires in 10 minutes. Never share it."4.2 Message frequency varies with how often you sign in. Msg & data rates may apply. Carriers are not liable for delayed or undelivered messages.4.3 Reply STOP to opt out of text messages at any time; reply HELP for help, or write to support@web2print.app. You can also turn two-step sign-in off in Settings, Security. After you opt out we send no further texts, so use your backup codes to sign in until you turn two-step sign-in off or choose another number.4.4 We use your mobile number only to send sign-in and security codes. We never send marketing texts. Mobile numbers and text-messaging consent are not shared with or sold to third parties or affiliates for marketing or promotional purposes. Texts are sent through Telnyx, which receives your number and the message only to deliver it.
5. How we use personal data, and why
5.1 To provide the Service you or your company signed up for: accounts, workspaces, members, sign-in, rendering, storage, the API, webhooks and the desktop app (performance of our contract).5.2 To bill you: taking payment, issuing invoices, renewals, handling failed payments, and keeping accounting and tax records (contract and legal obligation).5.3 To measure use against your license: counting allowances, seats and storage, showing usage on your dashboard, and emailing owners and admins when a limit is reached or passed (contract).5.4 To keep the Service and your account secure: sign-in protection, two-step sign-in, bot protection on sign-up, rate limits, the activity log, and investigating misuse (our legitimate interest in security, and yours).5.5 To support you and to answer your messages (contract and legitimate interest).5.6 To run and improve the Service: fixing faults and planning capacity, using technical and usage records without building profiles of individuals (legitimate interest).5.7 To account management: the sales representative assigned to your workspace may contact the owner or admins about your license, for example when usage passes an allowance (legitimate interest). You can ask us to stop these contacts at any time.5.8 To meet legal duties and to protect our rights (legal obligation and legitimate interest).
6. Email
6.1 We send service emails: account confirmation, invitations, password resets, receipts and invoices, renewal reminders, payment problems, limit notices, security notices and changes to the Service or these policies. These are part of the Service and you cannot opt out of them while you have an account. We do not send marketing email without your consent, and every marketing email has an unsubscribe link.6.2 Our emails are sent through our email delivery provider listed on the List of subprocessors.
7. Who we share personal data with
7.1 Subprocessors. Companies that run parts of the Service for us, under contracts that require them to protect the data and use it only for that work. They are listed, with what they do and where, on our List of subprocessors. Render workers that process your files are operated by Data Handler LLC itself, on Amazon Web Services or on our own hardware in the USA.7.2 Stripe processes payments under its own privacy policy (https://stripe.com/privacy). If you choose to save your details with Stripe Link, Link is governed by Stripe's terms.7.3 Your sales representative. The sales representative assigned to your workspace (who may be an independent contractor working with us) can see your company name, owner and admin contact details, your licenses and your usage counts per app. They cannot see your Customer Content.7.4 Your own workspace. Owners and admins of your workspace can see members' names, email addresses, roles, sign-in status, usage and activity log entries. Integrations and webhook endpoints your workspace connects receive the data that your workspace sends them.7.5 The law. We disclose data when the law requires it, such as a valid court order, and we tell the affected customer first unless the law forbids it.7.6 Business transfer. If the Service or Data Handler LLC is sold or merged, personal data passes to the new owner, who must honor this policy for the data already collected. We will tell you before that happens.7.7 We do not sell or rent personal data, and we do not share it for cross-context behavioral advertising.
8. Where your data is kept
8.1 The Service is hosted in the USA. Your account data and Customer Content are stored and processed in the USA.8.2 If you use the Service from outside the USA, your data is transferred to the USA. Where the law of your country requires a transfer safeguard, we rely on the European Commission's Standard Contractual Clauses (or the equivalent approved for your country) in our agreements with you and with our subprocessors.
9. How long we keep data
9.1 Files in your Drive stay until you or your workspace delete them. Deleted files go to Trash, where they can be restored for 30 days. After 30 days in Trash they are deleted for good, together with their previews and thumbnails. Emptying Trash or choosing "Delete forever" deletes them at once.9.2 Zip downloads we build for you are removed one day after they are made. Temporary upload files on our web servers are removed after about an hour.9.3 The event feed (the list of workspace events available through the API) keeps events for 30 days and then deletes them.9.4 Sign-ins last 24 hours, after which the session ends and can no longer be used. One-time sign-in codes expire after 10 minutes. Records of past sign-ins are kept as security records while your account exists.9.5 The activity log and usage records are kept for as long as the workspace exists, so that owners can see who did what and who used the allowance, and because usage records support billing.9.6 API request and webhook delivery records are kept while the API key or webhook endpoint exists. Deleting an API key in Settings deletes its request records.9.7 Invoices, payments and other accounting records are kept for as long as tax and accounting law requires, even after an account is deleted. When an account is deleted, the name and email on those records are replaced so they no longer identify you.9.8 After your licenses end. When every license in a workspace has ended, we keep the workspace and its files so that you can sign in, download your files or renew. We delete the workspace and its files when the owner asks us to (section 10).9.9 Backups. Deleted data may remain in our backups for up to [BACKUP RETENTION PERIOD: to be confirmed by Data Handler LLC] before it is overwritten. We do not restore deleted data from backups except to recover the Service after a failure.9.10 Messages you send us are kept as long as needed to deal with them and for our records of the account.
10. Your choices and rights
10.1 See and correct. You can see and change your name, email, password, phone number and two-step sign-in in Settings. Owners and admins can see the activity log and usage records for their workspace.10.2 Export. You can download your account details from Settings, Privacy, and download any file, folder or selection from your Drive. Owners and admins can export the activity log and usage records as CSV. Ask us for anything else we hold about you.10.3 Delete your account. In Settings, Privacy you can delete your account. That deletes your sign-in, sessions, API keys and their request records, saved payment methods and your customer record at Stripe, removes your phone number and backup codes, and replaces your name and email on any remaining records. If you are a workspace owner, your members' sign-ins are deleted too. Files in the workspace's Drive are not deleted by that button: delete them in Drive first, or ask us to delete the whole workspace.10.4 Delete a workspace. The owner can ask us at privacy@web2print.app to delete the workspace and all its Customer Content. We confirm the request with the owner, then delete it, apart from records the law requires us to keep and copies in backups (section 9.9).10.5 Other rights. Depending on where you live (for example in the European Economic Area, the United Kingdom or certain US states), you may have the right to access, correct, delete or receive a copy of your personal data, to object to or restrict some uses, and to withdraw consent. We honor these requests for everyone, free of charge. Write to privacy@web2print.app; we may need to confirm your identity first, and we answer within 30 days. We will not treat you differently for using these rights. You may also complain to your local data protection authority.10.6 If your data is Customer Content held by a company that uses web2print.app (for example your name on a business card order), please contact that company. We will help it answer your request.
11. Security
11.1 We protect personal data and Customer Content with measures that include: encrypted connections (HTTPS) between your browser, the desktop app, integrations and our servers; passwords stored only as salted one-way hashes; one-time codes and backup codes stored as hashes; optional two-step sign-in; sign-ins that expire after 24 hours; separation of each workspace's data in our software and storage; render workers that have no access to our database; signed webhook deliveries; limits on API requests, on two-step code attempts and on desktop pairing attempts; and limiting staff access to what each person needs.11.2 No system is perfectly secure. You help by using a strong, unique password, turning on two-step sign-in, keeping API keys secret, and removing members and paired computers that no longer need access.
12. If something goes wrong
12.1 If we learn of a security breach that affects your personal data or Customer Content, we will tell the affected workspace owners by email without undue delay, and within any time limit the law sets. We will tell you what happened, what data was involved, what we are doing about it and what you can do. We will also notify regulators and affected people where the law requires.
13. Cookies and similar technology
13.1 We use a cookie to keep you signed in. It is needed for the Service to work. The studio also stores a few preferences in your browser (such as light or dark theme and unsent drafts).13.2 Our pages load Stripe's payment script, which Stripe uses to take payments and to prevent fraud and may set its own cookies; our sign-up page uses Cloudflare Turnstile to block automated sign-ups; and our pages load icons and fonts from the providers on our List of subprocessors, which receive your IP address when they serve them.13.3 We do not use advertising cookies or third-party analytics trackers. You can block cookies in your browser, but you will then not be able to sign in.
14. Children
14.1 The Service is for businesses and is not meant for anyone under 18. We do not knowingly collect personal data from children. If you believe a child has given us personal data, write to privacy@web2print.app and we will delete it.
15. Changes to this policy
15.1 We may update this policy. For a material change we will email workspace owners and show a notice in the Service before it takes effect. The current version is always at web2print.app/privacy-policy/, with a log of changes at the end.
October 24, 2026: Rewritten for web2print.app. Replaces the general Data Handler LLC privacy policy. Adds Customer Content and no AI or training, two-step sign-in text messages, the activity log, usage and sign-in records, API and webhook records, sales representatives, retention periods, account and workspace deletion, breach notice, and an effective date.