Legal
Privacy policy
Onvanto is a company portal with field apps for planning lab trips of measuring instruments. This policy explains what the portal, the apps, this website and our support process.
On this page
1 The short version
You sign in with your work email. Your company's planning, instruments, jobs and certificates are stored in Cloudflare's EU jurisdiction. We use no analytics, advertising or tracking in the service, and we never sell personal data. You can export the planning and delete your account or company yourself.
2 Who decides about which data
Oomny B.V. provides Onvanto and is the controller for account administration, sign-in security, this website, support and any billing. Our registration and address are on the legal information page.
Your company is the controller for the planning, documents and team data it enters. We process those records on its instructions to provide the service. Contact your company first about its records; we assist it with requests concerning data we process on its behalf.
Privacy questions and requests: [email protected].
3 What the service stores
- Your account. Your email address and the name you enter.
- Signing in. Sign-in codes (stored only as a hash, valid for 5 minutes), sessions (with a 14-day expiry that can be renewed when used) with the IP address and browser or app identification of the sign-in, and request counts per IP address to stop abuse.
- Your company. Its name, country, time zone and language, its members with their roles and technical qualification, open invitations with the invited email address, and an activity log of changes to the company and team.
- Planning. What your company enters, such as instruments, jobs, lab shipments, certificate PDFs and the planning history.
The field apps keep your sign-in token in the device's secure storage and send planning only to the service you connect. They contain no analytics or advertising.
If you register a passkey, we store its public credential and technical sign-in information, not the private key held by your authenticator. Recovery codes are stored as hashes.
A member can connect their own Google or Microsoft calendar for a company; Onvanto then creates its own calendar there. It writes the job or lab name and relevant date as an all-day event for a job or shipment, and reads changes to those events back into the service. We store the connection details and encrypted OAuth tokens. The provider’s consent screen describes the permissions requested; disconnecting stops future access through that connection. The calendar Onvanto created in your Google or Microsoft account remains there until you delete it in that account.
Authorised administrators can configure scoped API keys and webhooks. A webhook sends the selected event data to the endpoint your company chooses. The receiving provider or company then controls that copy.
Where a checkout is offered, the checkout requests a billing address and applicable tax identification. Stripe processes this information and payment details and returns customer, checkout, subscription and payment status identifiers. We do not receive your full card number. A test checkout does not create a real payment; any paid order must show its price and obtain your confirmation.
A demo creates a temporary workspace with fictional records without requiring an account. It expires after 24 hours. The service limits demo starts and connection requests using a hash of your IP address to prevent abuse. Avoid entering real personal or business data in the demo.
A member can create personal read-only calendar feed addresses. We store a hash of each feed’s access secret, its owner, company, optional team filter and creation time. Anyone who has the address can read the planning entries in that feed. The calendar app that subscribes to it fetches them under its own privacy policy. A feed stops working when it is revoked, when the membership ends or when the company is suspended or being deleted.
If you turn on the daily email overview, we store your choice, the kinds of items and the hour you picked, and record the daily delivery status without the message content. The email contains the names of the relevant items and links to the portal.
If your company enables the returns module, we store its supplier records, returns and credit documents, line items, amounts, allocations and their confirmations, and activity history, together with uploaded originals, filenames, file hashes and processing results. Documents may contain personal data that your company or its suppliers include. Your company controls these business records and decides which members hold which returns rights; we process the records on its instructions to provide the module.
Where the returns email inbox is available, a member with the right to manage the returns module can create a secret company address, set approved sender addresses with supplier mappings and revoke the address; disabling the module also revokes it. We store only a hash of the address token, together with those settings. The service reads incoming email to extract supported attachments and stores each original with its filename, file hash and processing status. Every incoming attachment is held for review and is not processed further until a member with review rights releases it and assigns a supplier. Keep the inbox address private; a sender setting alone does not authenticate a message.
4 Why, and on what basis
We process the account information needed to deliver the requested service on the basis of the contract with you (Article 6(1)(b) GDPR), or our legitimate interest in administering access for your company where it is the contracting party (Article 6(1)(f)). Your company determines the legal basis for its planning and team data.
Sign-in limits, activity records and security checks protect the service and its users (Article 6(1)(f)). We use contact details and message contents to answer support requests on the same basis, or to perform the contract where the request concerns that service. Applicable tax or accounting duties require retention of relevant billing records (Article 6(1)(c)).
We send sign-in codes, invitations and service notifications needed for the functions you use. There is no advertising profiling or automated decision with legal or similarly significant effects. You must provide a work email to have an account; optional connections require the information shown when you enable them.
5 This website
Cloudflare processes IP addresses and request data to deliver and protect this website. Cloudflare Web Analytics counts visits and measures loading speed without cookies and without building a profile of you. The planning board on the home page runs in your browser and sends nothing.
6 Who processes data for us
- Cloudflare, Inc. hosts the service, its databases, this website and the delivery of sign-in codes.
- Microsoft 365 provides the mailbox we use to handle support and privacy requests.
- Apple and Google distribute the field apps under their own privacy policies.
Oomny staff can see account metadata (company name, country, status, creation date, number of members, trial end date, billing status and paid-until date, and the latest sign-in activity of its members) to run the service. That view has no access to planning or documents.
Cloudflare also sends invitations and service notifications and routes incoming email for the product domain. Microsoft 365 stores and handles support correspondence. Google and Microsoft process calendar requests under their own privacy policies. Stripe handles any checkout and associated payment records under its own applicable terms and privacy policy. Endpoints selected by your company receive the webhook data it configures.
Cloudflare hosts the returns records, original files, email handling and processing queue. Where document recognition is available and enabled, we send the whole PDF or image of an uploaded or released document without supported structured data to Microsoft Azure Document Intelligence to extract text and document fields on your company's behalf. Onvanto stores the extracted result with its confidence and source information for review. Supported structured XML and CSV files, and PDFs with embedded structured invoice data, are read without an Azure recognition request. Recognition can be wrong; it does not itself approve a financial allocation.
7 Location and transfers
Company records and the planning are stored in Cloudflare's EU jurisdiction. Our service providers may process website, delivery, correspondence and document-recognition data outside the European Economic Area; such transfers rely on the European Commission's Standard Contractual Clauses and, where applicable, the EU-US Data Privacy Framework.
Calendar providers, payment providers and the endpoints your company selects may operate outside the EEA under their own policies. Contact [email protected] for information about safeguards for processing under our responsibility.
8 How long we keep it
Your account remains until you request deletion. Deletion removes your name, email, sign-in methods, passkeys, recovery codes, sessions and memberships from the active account. A pseudonymised account identifier remains so company audit history can still be read without your profile. This is not a promise that every historical reference disappears. If you are a company’s only owner, you must first transfer ownership or delete that company. Account deletion also removes your calendar connections and feeds, the API keys you created with their webhooks, and your notification settings. A calendar Onvanto created in your Google or Microsoft account remains there until you delete it in that account.
Company planning and documents remain while the company exists. An authorised owner can request deletion. Active billing or an open checkout must be resolved first; a suspended company needs support to resolve the suspension. The service closes the company before erasure. A minimal audit event remains with the actor and company identifiers and deletion time to record the deletion. It has no scheduled expiry.
Cloudflare database recovery history may retain deleted data for up to 30 days. That recovery window does not apply to the audit exceptions above or records we must retain by law. Sign-in codes expire after 5 minutes and sessions have a 14-day expiry that can be renewed when used; expiry prevents their use but does not itself promise immediate erasure of every technical record. Support messages are kept while needed to answer, document handling, resolve a dispute or comply with a legal duty.
Deleting a company removes its billing status and checkout records from the portal database. It does not delete invoices or payment records held by Stripe under its own retention rules. Records we must keep for tax or accounting purposes are retained for the applicable statutory period (Article 6(1)(c) GDPR). Contact us for the records and retention period applicable to a particular transaction.
Returns records and original documents remain in the company workspace. Disabling the module or ending access does not erase them; members can still read and export existing records according to their returns rights. Company erasure removes the active returns workspace, its originals and its processing data. A minimal deletion marker remains so that delayed processing cannot recreate erased data. The separate audit and recovery-history exceptions described above still apply. Exported copies remain with whoever holds them.
For Azure document recognition, after the result has been stored in your Onvanto workspace, the service asks Azure to delete that analysis result. A failed deletion request is retried while the processing job remains active, but success cannot be guaranteed, for example after company erasure. Microsoft's published privacy documentation states that submitted input and analysis results are deleted automatically 24 hours after the analysis completes. Neither step removes the original or the extracted result retained in your Onvanto workspace.
9 Your rights
You can correct your name and request account deletion in Account or Settings. Company owners manage membership and company deletion; qualified members can export planning. Where a self-service action is unavailable, contact support.
Where the GDPR applies, you can request access, correction, erasure, restriction and data portability, and object to processing based on legitimate interests. These rights depend on the circumstances. Where processing relies on consent, you can withdraw it at any time without affecting earlier lawful processing.
Contact [email protected]. We normally respond within one month. We may need proportionate information to verify your identity. If an extension is permitted for a complex request, we explain it within that month. We cannot retrieve content that exists only on your device.
You may complain to the Autoriteit Persoonsgegevens or your local EU/EEA supervisory authority.
11 Changes
We update this policy when the service changes and show the date above. Material changes are announced in the portal.