Privacy policy
This policy explains what personal data VorxOS processes, why, where it is stored, how long it is kept and what rights you have. It covers this website and the VorxOS web app, API and AI assistant connection.
Last updated: 29 October 2026
1. Who we are
VorxOS is operated by Linvium LLC, a limited liability company registered in Wyoming, USA (filing ID 2024-001576234), with its principal office at 30 N Gould St, Ste R, Sheridan, WY 82801, USA (“VorxOS”, “we”, “us”).
For privacy questions and requests, write to privacy@vorxos.com. We have not appointed a data protection officer, because our processing does not meet the conditions that make one mandatory.
2. Our two roles: controller and processor
We process personal data in two different roles, and this policy treats them separately.
- As controller, we decide how and why we process data about website visitors, people who contact us, account users and the companies that pay us. This policy describes that processing in full.
- As processor, we process the documents our customers upload (bank statements and invoices) and the data extracted from them, only on our customers’ instructions. These documents contain personal data of people we have no relationship with: account holders, counterparties, suppliers and buyers. For that data our customer (usually an accounting firm or a company’s finance team) is the controller, and our Data processing agreement governs what we may do with it.
If your name or account details appear on a bank statement or invoice that someone processed with VorxOS, please contact the company or accountant who uploaded it. We will help them answer your request, and we will forward any request we receive directly.
3. What we collect
| Category | What it includes | Where it comes from |
|---|---|---|
| Website visit | Your chosen language (in a cookie), and the technical data any web server receives: IP address, browser, requested page and time. | Your browser |
| Contact requests | Name, company, email address, expected monthly volume and your message. | You, through the contact form on the pricing page |
| Account | Email address, display name, password (stored only as a hash by our authentication provider), two-step sign-in factor, role, language and notification preferences. | You, or the colleague who invited you |
| Company | Company name, contact email, tax identification numbers, default currency. | The account owner |
| Billing | Credit purchases and balance, the Stripe customer reference, the email used at checkout. Card details go to Stripe; we never see or store them. | You and Stripe |
| Usage and security | Request logs (IP address, user agent, method, path, status, duration, API key used), sign-in events, an activity log of who changed what, API key prefixes and when keys were last used. | Generated when you use the service |
| Integrations | Google Drive authorisation and folder choices, SFTP and HTTPS delivery settings, email addresses for deliveries and notifications, webhook URLs. Credentials are stored encrypted. | You, when you connect an integration |
| AI assistants | Which assistant you connected (for example Claude or ChatGPT), and whether it may only read or also change data. | You, when you authorise an assistant |
| Customer content | Uploaded documents, extracted data, corrections, code lists, export formats, folders and checklists. We process this as a processor (see section 2). | Our customers |
| Support | Emails and messages you send us, and our replies. | You |
We do not use analytics, advertising or tracking tools on the website or in the app, and we do not buy personal data from third parties.
4. Why we use it, and our legal basis
We rely on the legal bases in Article 6 of the GDPR and the matching provisions of the Law on Personal Data Protection of Bosnia and Herzegovina (Official Gazette of BiH 12/25) and the Law on Personal Data Protection of Serbia (Official Gazette of RS 87/2018).
| Purpose | Data | Legal basis |
|---|---|---|
| Creating and running your account, processing documents, exports and deliveries | Account, company, integrations, customer content | Performance of a contract |
| Selling credits, issuing invoices, keeping accounting records | Company, billing | Performance of a contract; legal obligation |
| Service emails: email confirmation, team invitations, notifications you switched on | Account | Performance of a contract |
| Answering contact requests and preparing offers | Contact requests | Steps at your request before entering a contract; legitimate interest in answering business enquiries |
| Keeping the service secure: detecting abuse, enforcing rate limits, investigating incidents, fixing errors | Usage and security | Legitimate interest in a secure and reliable service |
| Improving the service using aggregated figures (for example how many documents need review) | Usage, statistics without content | Legitimate interest in improving the product |
| Establishing, exercising or defending legal claims | Any relevant data | Legitimate interest; legal obligation |
Where we rely on legitimate interest, you can object at any time (see section 10). We do not send marketing emails. If that changes, we will ask for your consent first.
VorxOS reads documents; it does not make decisions about people. We do not carry out automated decision-making that has legal or similarly significant effects on you within the meaning of Article 22 GDPR.
5. How documents are read by AI
To read a document, VorxOS either uses a reader written for that bank’s layout, which runs on our own servers, or sends the document to an AI model from Anthropic through Anthropic’s commercial API. Scanned documents, photos, invoices and unknown layouts go to the model. A small random sample (about 2%) of documents read by our own readers is also sent to the model to check that the readers are still correct.
- Under Anthropic’s commercial terms, content sent through the API is not used to train Anthropic’s models.
- By default, Anthropic keeps API inputs and outputs for up to 30 days, for abuse monitoring and its own backend storage, and then deletes them.
- We do not use your documents or your corrections to train any AI model. Corrections and learned bank layouts only improve results inside your own company’s account and are never shared with other customers.
- Diagnostic traces of model calls contain document content only if your company has agreed to it in writing. By default they contain timing and error information only.
7. Where data is stored, and transfers abroad
VorxOS is operated by a company established in the United States. Our database and uploaded files are stored with Supabase in the EU (Ireland), and the application runs on Railway in the EU (Amsterdam, the Netherlands). Emails are sent through Resend’s EU region.
We and some of our providers can access data from the United States, and Anthropic which processes document content to read it. When personal data leaves the EU/EEA, Bosnia and Herzegovina or Serbia, we use one of the safeguards the law recognises: an adequacy decision (including the EU–US Data Privacy Framework, where the recipient is certified), or the European Commission’s Standard Contractual Clauses (2021), together with the safeguards required by the BiH and Serbian laws.
You can ask us for a copy of the safeguards that apply to a particular transfer.
8. How long we keep data
| Data | How long |
|---|---|
| Uploaded source files and the model’s raw answer | 30 days after the document finished processing, unless your company agreed a different period with us (between 1 day and 10 years). Deleted at once if you delete the document or job. |
| Extracted data (statements, transactions, invoices, results) | Until you delete the document or job, or until the account is closed. |
| Files uploaded but never used in a job | About one hour. |
| Request logs (including IP addresses) | 90 days. |
| AI assistant and automation transcripts | 90 days. |
| Activity log (who changed what) | 12 months. |
| Account and company data | While the account exists, and 7 days after it is closed. |
| Billing records and invoices | 7 years after the end of the tax year, the longest period US federal tax record-keeping rules can require, unless the law requires longer. |
| Contact requests | 12 months after the last exchange, unless they lead to a contract. |
| Backups | Deleted data disappears from backups when they expire, within 7 days. |
When a team member is removed, their profile, API keys and assistant authorisations are deleted, and work they did stays in the company’s account without their name.
9. How we protect data
Data is encrypted in transit. Each company’s data is separated in the database by row-level security. Integration credentials are encrypted with a separate key, API keys and invitation tokens are stored only as hashes, and every user can switch on two-step sign-in. File contents are never written to logs. The Security page describes these measures in more detail.
If a personal data breach is likely to put your rights at risk, we notify the competent supervisory authority within 72 hours and inform the affected people (or our customer, where we act as processor) without undue delay.
10. Your rights
Under the GDPR and the BiH and Serbian data protection laws, you have the right to:
- access the personal data we hold about you and receive a copy;
- have inaccurate data corrected;
- have your data deleted, where we have no legal reason to keep it;
- restrict how we use your data while a question about it is being resolved;
- receive data you gave us in a structured, machine-readable format, and have it sent to another provider;
- object to processing based on legitimate interest;
- withdraw consent at any time, where we rely on consent, without affecting what was done before.
Write to privacy@vorxos.com. We answer within one month. For complex requests we may extend this by two more months and will tell you why. We may ask you to confirm your identity first. Requests are free unless they are clearly unfounded or excessive.
The account owner can close the account and delete the company’s data in the app’s settings, or by writing to the same address.
You can also complain to a supervisory authority: in Bosnia and Herzegovina the Personal Data Protection Agency (Agencija za zaštitu ličnih podataka u BiH), in Serbia the Commissioner for Information of Public Importance and Personal Data Protection, or in the EU/EEA the authority of the country where you live or work. We would appreciate the chance to answer your concern first.
11. Google Drive data
If you connect Google Drive, VorxOS asks Google for access to your Drive so that it can watch the folders you choose, read the PDF and image files you put there, and write the results back to the folder you choose. We use this access for nothing else.
VorxOS’s use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements. In particular:
- we use Google user data only to provide the import and delivery features you set up;
- we do not transfer it to others except as needed to provide those features (for example to read documents with our AI provider), for security, or to comply with the law;
- we do not use it for advertising, and we do not sell it;
- we do not use it to develop, improve or train generalised AI or machine-learning models;
- our staff do not read it unless you ask us to, it is needed for security or to investigate abuse, or the law requires it.
The Google authorisation is stored encrypted. You can disconnect Drive in VorxOS at any time, or revoke access in your Google account settings.
12. Children
VorxOS is a business service. It is not intended for anyone under 16, and we do not knowingly collect their data.
14. Changes to this policy
We will update this policy when our processing changes. The date at the top shows the latest version. For significant changes we will email account owners at least 30 days before they take effect.