Ventra holds your business data and your clients' data in one workspace. These pages set out what we do with it, what you are responsible for, and where the line between the two sits.

Our legal documents

Three documents cover your use of Ventra. Two are binding. The third explains them.

What we commit to

These are stated in full in the Privacy Policy and the Terms. They are collected here because they are the questions buyers ask first.

• You own your content Your leads, clients, quotations, projects, invoices, messages, and files are yours. Our licence to hold them exists only to run the Service, and ends when you delete them.
• We do not sell personal information No sale, no sharing with advertisers, no advertising or cross-site tracking cookies anywhere in the product.
• We do not train models on your workspace Workspace content is not used to train machine learning models. If that ever changes, the Privacy Policy is updated and you are notified before the processing starts.
• Workspaces are isolated No customer of Ventra can see another customer's leads, clients, projects, or messages. We do not aggregate data across workspaces.
• We do not enrich your leads Ventra stores what your form sends and nothing more. We do not append, enrich, or buy information about a lead from any third-party data source.
• Access is scoped by role and project Six roles, checked on every request. A client reaches their own projects and the teams assigned to them, and nothing else.
• Passwords cannot be read, only reset Stored as one-way hashes. Nobody at Ventra can retrieve yours.
• Material changes come with notice Where a change reduces your rights or introduces a new category of processing, we tell you before it takes effect, not after.

Controller and processor

This is the distinction that matters most if you are assessing Ventra against a data protection obligation of your own.

In practice: when someone fills in a form on your website and Ventra creates a lead, you are the controller of that person's information. Your privacy notice, not ours, is what they should be reading. We store and process it on your behalf, and we act on your instructions about it.

The same applies to client portal accounts. Ventra creates one automatically when a quotation is approved, but it does so because your workflow told it to. The obligation to have a lawful basis for that, and to give whatever notice your jurisdiction requires, sits with you.

What Ventra does not do

Stated plainly, because assumptions in this area create real exposure.

• Ventra does not process payments. We generate and deliver invoices. We are not a payment processor, money transmitter, escrow agent, or payment facilitator, and we never collect, hold, or transfer funds. No card number is entered into Ventra. Marking an invoice paid records your assertion, not a settlement.
• Ventra does not determine your tax. It applies the rate you type and does the arithmetic. It does not verify registration numbers, apply place-of-supply rules, or assess whether a rate is correct.
• Ventra does not warrant document compliance. Invoice numbering, mandatory content, currency, language, e-invoicing mandates, and archival format vary by jurisdiction. Confirming a generated document meets your obligations is your responsibility.
• Ventra does not adjudicate your disputes. A milestone approval or rejection is a log of an action taken inside the platform. It does not determine whether work met contract, and we do not arbitrate between you and your client.
• Ventra is not professional advice. We are not your accountant, tax adviser, lawyer, or contract administrator, and nothing the Service produces is advice.

Where Ventra runs

Ventra runs on [Hostinger] infrastructure in [Global]. Transactional email — quotation delivery, invoice delivery, portal credentials, and notifications — is sent through [SMTP].

Those are the only third parties that process workspace data on our behalf. If we add or replace one, the Privacy Policy is updated and, where the change is material, we give notice before it takes effect.

Security measures — TLS in transit, hashed passwords, role-based access checked on every request, webhook token validation, and authenticated API endpoints — are set out in full in the Privacy Policy.

If you are a client of a Ventra customer

You may have received portal credentials from an agency, studio, or service provider and arrived here trying to work out what Ventra is.

Ventra is the software that business uses to run client projects. When you approved their quotation, their workspace created an account for you so you can see projects, approve milestones, and download your quotations and invoices.

They control your information, not us. Their privacy notice tells you what they collect and why. Requests to correct or delete your data should go to them — they can remove records and revoke your account. If you write to us, we will forward the request to them and confirm we have done so, but we cannot act on it ourselves.

The FAQ has a section written specifically for you.

Making a request

Send it to the right address and it reaches the right people faster.

We aim to acknowledge a data request within [3] days and to respond substantively within the period applicable law allows. We may need to verify your identity before acting on one.

How we handle changes

Ventra is under active development, so these documents change as the product does. Three rules apply to every change.

• The effective date at the top of each document always reflects the current version.
• Material changes — anything that reduces your rights or introduces a new category of processing — come with advance notice by email or in-product message.
• Continuing to use Ventra after a change takes effect means you accept it. If you do not, cancel before the effective date.

Two categories of change we will always announce in advance rather than quietly ship: enabling payment collection, and any processing of workspace content by a machine learning system.

Contact