FORMRAIL
Privacy
Effective September 9, 2026.
Your PDFs
We process submitted PDFs and field values in memory to inspect, validate or fill them. We do not save the document, its field values, or the generated PDF in our application database, logs or analytics. Retry records contain a hash of the input and a small completion receipt. You resend the same input to regenerate an output.
Account and payment data
Clerk handles sign-in. Stripe handles payments and stores payment details. We store your account identifier, API key hashes, credit balances, payment references, request receipts, fixed error codes and operational usage totals. FormRail credits and billing are separate from other Voltenworks products.
Hosting and retention
Vercel processes requests and Neon stores application records in the United States. Providers may process limited network and security metadata under their own policies. The application does not log request bodies. Operational and account records are retained while needed to provide the service, handle support, prevent abuse and meet recordkeeping obligations. Contact support to request account deletion; legally required payment records may be retained.
Attribution and analytics
Public pages use our self-hosted Umami analytics. A first-party cookie, lasting up to 30 days across Voltenworks product subdomains, remembers the referring product and a limited campaign category. It contains no account ID or unique visitor token. It helps distinguish a first visit from a returning browser and identify movement between product pages.
After sign-in, the campaign category can be associated with signup, first successful fill, subsequent use and confirmed purchases. When products use the same verified sign-in system, an internal aggregate report can count customers using or buying multiple products. We do not merge separate accounts by email. Documents, field names, field values, API keys and personal identifiers are never sent to Umami.
We honor Do Not Track and Global Privacy Control for attribution and analytics. Operational credit and payment records still exist to run the service. Missing attribution remains unknown. Clearing or blocking cookies can make a returning browser look new. Analytics delivery failures may leave totals incomplete; our payment ledger remains authoritative.