noDocsLast updated: 9 October 2026.
Who is responsible
Ion OÜ, registry code 11874469, VAT ID EE101815547, Vilde 6-5, Kohtla-Järve, Estonia, is responsible for the personal data we process to operate OnoDocs and respond to customers. Contact support@onodocs.com for privacy questions or requests.
Your documents stay on your device
The demos process selected Word documents and entered values in your browser. They do not upload document contents or filenames, or put them in URLs, analytics or error reports. The form demo stores working and saved drafts in this browser so you can restore your answers on a later visit. Valid changes are saved after you leave a field. Start new request removes the drafts for the current form and clears its answers. Drafts for other templates remain until you clear the site's browser storage. Leaving or resetting other demos releases their in-memory data. Exported files remain on your device. The original Word file stays unchanged.
The source-linked report demo uses a labelled local sample reviewer. The email workflow also runs locally. Neither sends document data to an AI provider or sends email. Applications built by other developers, including those that connect a provider or save documents on a server, have their own data practices and privacy policies.
Website requests and demo licenses
Our hosting providers, OpenAI Sites and its infrastructure providers including Cloudflare, receive technical information needed to serve and protect the website, such as IP addresses, request URLs and browser information. Demo licenses are embedded in HTML and may be refreshed through our website. Those requests contain no document content. Customer SDK licenses verify offline and do not contact a license server.
We load no third-party advertising scripts and do not use document data for advertising or AI training. The private sandbox uses hosting-provider sign-in and necessary authentication cookies. External sites, including GitHub, have their own privacy policies.
Website analytics
With your permission for Analytics and advertising measurement, our own website collects limited usage events to understand visits to public pages and guides, demo selections, successful document loading, editing, generation, form completion, export initiation, handled demo failures, and clicks on sample, source and evaluation links. Each record contains the public page path, time, fixed action name and, where relevant, the built-in sample name. For Google, Bing, DuckDuckGo and GitHub referrals, we record only the referring site. Other referrers are omitted. We exclude full URLs, fragments, page titles, document contents, filenames, extracted values, form inputs, license keys and private purchase links. Campaign tags are included only with the permission described below.
Our backend reduces browser information to a broad browser family and device category. When the hosting platform supplies a country code, we retain that code. We do not store IP addresses or full user-agent strings in analytics. A random identifier groups actions during one page load. It changes on navigation or reload and is not saved in browser storage. We use no analytics cookies, persistent visitor identities, session recordings or heatmaps. With your permission, the campaign labels described below can connect activity to an advertising campaign without identifying a unique visitor.
Records are stored in the website's own Cloudflare D1 database through OpenAI Sites, separately from commerce records. They are retained for product analysis and removed when no longer needed. No external analytics service receives these events.
Do Not Track and Global Privacy Control prevent collection. Analytics is absent from the SDK, downloaded document samples, downloaded guides and private checkout. Hosted demos collect the same limited events after permission; embedded homepage demos report fixed outcomes through the parent page. No error details or document values are sent. Automated WebDriver visits are excluded. Evaluation-link counts measure clicks to npm and GitHub. They do not confirm installations or completed downloads.
Privacy preferences and advertising measurement
Our Privacy preferences notice offers one optional choice: Analytics and advertising measurement. This covers the website usage events above and measuring which advertising leads to purchases. Accept and Decline are equally available. Closing the notice without accepting leaves both off. Essential website functions, document demos and purchasing remain available when you decline.
You can change your choice at any time using Privacy preferences in the footer. Declining stops future optional analytics events and clears the remembered advertising source. Do Not Track, Global Privacy Control and the analytics opt-out also prevent this measurement.
With that same permission, we remember the advertising source in this browser for up to 30 days. We store campaign labels (utm_source, utm_medium, utm_campaign, utm_content, utm_term and campaign_id) and, if present, one Google ad click identifier (gclid, gbraid or wbraid). Click identifiers are kept separately from general website analytics. The most recent tagged campaign receives credit; ordinary visits keep that campaign until it expires. We remember your choice until you change it or clear this browser's storage. A new campaign replaces the previous one, and each remembered campaign expires 30 days after its tagged visit. Changing devices or browsers does not carry it across.
Campaign labels accompany public website events and, when you start checkout, your order. With explicit permission for Google advertising measurement, the click identifier and consent time also accompany your order. We send Google the click identifier, a transaction reference, purchase time, currency and amount from verified paid orders. Approved refunds reduce that amount. We do not send your email, name, documents or license key, and we do not enable personalized advertising. Existing analytics permission alone does not authorize Google uploads; the updated notice asks for a new choice. Read Google's privacy policy. Completed purchases are counted from verified payment records. Reports show campaign activity, paid purchases, complimentary orders and refunds. Withdrawal clears the browser's remembered source and stops future attribution. Declining from your purchase-link page also clears that order's click identifier and stops further uploads for that order. To withdraw for an earlier order, open its purchase link and decline, or contact support@onodocs.com. Withdrawal does not undo uploads already processed by Google or delete required business records. The daily commerce sync removes stored click identifiers after 90 days; browser storage expires after 30 days. Optional website analytics stays off after withdrawal, including events without campaign labels.
Support and licensing data
If you contact us, we process your email address, correspondence, technical details you choose to provide, and information needed to identify your license and applications. This lets us answer your request, provide contracted support, and manage licenses. Avoid sending confidential documents unless necessary. A minimal file with fictional content is usually sufficient. Public GitHub issues must not contain personal data or private documents.
Our email and repository providers process the messages and reports you submit. Support email is hosted by Zoho Mail. Automated purchase and recovery emails are sent through Zoho CPaaS in the EU region, which processes the recipient address and secure delivery link. We do not sell personal data.
Purchasing data
Live checkout is available for OnoDocs licenses. A separate private sandbox is used for testing. Paddle processes payment, tax and billing details under its privacy policy. We receive order, customer contact, payment status, named application scope and entitlement information needed to deliver and support your license and maintain business records. Orders and fulfillment are stored separately from our local commercial reports. Reports retain stable transaction references and campaign labels attached with your permission at checkout, but exclude license keys, named applications and billing email addresses. We do not receive full payment-card details.
Purposes, retention and transfers
We process contact and order information to respond to requests and perform contracts. We keep business records to meet legal obligations. We process limited technical and support information for our legitimate interests in operating, securing and improving the product. Where processing requires consent, you may withdraw that consent.
We keep support correspondence only as long as needed to resolve the request and manage related issues, and license records as needed to establish ongoing entitlements. Accounting records are kept for the applicable statutory period. On request, we can explain the retention applicable to your record. Service providers may process information outside Estonia or the EEA using safeguards required by applicable data-protection law.
Your rights
Depending on the processing and applicable law, you may request access, correction, deletion, restriction or portability, and object to processing. Contact support@onodocs.com. We may need to verify your identity. You can also complain to the Estonian Data Protection Inspectorate or your local supervisory authority. These rights do not require us to erase records we must retain by law.