Skip to content

Privacy

Privacy Notice

Effective November 8, 2026

01

Two relationships, kept separate

Vered handles personal data in two different roles, and this notice treats them separately because the obligations are not the same.

  • This website. If you browse vered.io or ask us for a discovery session, we decide what we collect and why. Clause 2 covers that.
  • The platform. If your employer runs Vered, the records inside it — your colleagues, their customers, their suppliers — belong to your employer. We hold and process that data on their instructions, not our own. Clause 3 covers that.
If you are an employee of a Vered customer and want to know what is held about you, or want it corrected or deleted, ask your employer. They control that data; we act on their instruction. We will help them answer you, and we will not act on it ourselves without them.
02

What we collect from visitors to this site

Information you give us

The discovery form on this site asks for your first and last name, company, role, and work email, and asks you to agree to storing the discovery conversation to prepare a brief. We use it to prepare for and hold that conversation and follow up on your inquiry. Submitting the form does not subscribe you to an unrelated mailing list.

If you email us, we keep the correspondence for as long as it is useful to the relationship.

Information collected automatically

Our hosting provider records ordinary server logs — IP address, request time, page requested, browser user-agent — for delivery, security, and abuse prevention. We do not build profiles from it and we do not use it for advertising.

Discovery also uses request metadata, including a hashed network address and browser information, to prevent abuse.

Optional marketing analytics and advertising pixels are currently disabled. Operational hosting and security logs still support delivery, troubleshooting and abuse prevention. See the Cookie Notice for the cookies supporting the platform features you request.

AI-assisted discovery

If you choose the AI-assisted conversation, its content is processed by our AI and hosting providers to respond and prepare a brief. See AI Data Handling and Subprocessors. You can contact us directly instead of using the AI conversation.

Our reasons for using this information

Where UK data protection law applies to our website and business contacts, we rely on legitimate interests to answer business inquiries, manage relevant business relationships and protect the service, taking account of the individual’s interests and rights. When you choose a recorded AI-assisted discovery conversation, we rely on your consent for that recording and related processing. You can ask to withdraw that consent using the contact below; withdrawal does not change the lawfulness of processing before it was withdrawn.

What we do not do

We do not sell personal information, and we do not share it for cross-context behavioural advertising. We do not buy contact lists. We do not enrich what you give us against third-party data brokers.

How long we keep it

Closed discovery-session transcripts are cleared after ninety days from completion, or from the last session activity if the session was never completed. Some short abandoned transcripts are cleared sooner. Contact details, the resulting brief and staff notes are separate records; the transcript purge does not delete them.

We retain prospect contact details, briefs and staff notes while they are needed for a business inquiry or relationship. These records are reviewed for continuing need, with deletion or anonymisation when they are no longer needed, subject to applicable legal requirements and legitimate recordkeeping needs. This review is handled manually; automatic deletion of these records after twenty-four months is not currently in place. You can ask us to review your information sooner.

03

Tenant data: our role as processor

When a customer runs Vered, they load their own records into it. We process that data to provide the service under our agreement with them, and for no independent purpose of our own. Specifically, we do not sell it, we do not mine it for our own analytics, and we do not use it to train models — see AI Data Handling.

Tenant data is isolated at the database on every write, not by application code that has to remember. Access by our staff is limited to what support and operation require, requires the same multi-factor authentication regulated workflows require, and is written to an append-only audit trail under the staff member’s own identity as well as the account they are acting as. The controls are described on Security & compliance, each one pointing at where it is enforced.

The third parties that can touch tenant data are listed in full, with what each one sees, on Subprocessors. How long each class of record is kept, and what is kept for the life of the record, is on Data Retention & Deletion.

Customers who need a data processing agreement should write to privacy@vered.io.

04

Platform account data

To give you an account we hold your name, work email, role, the permissions granted to you, and — if you enrol it — the secret behind your authenticator app, which is stored encrypted. We record sign-in events, multi-factor attempts, and the actions you take in regulated workflows, because a regulated system has to be able to say who did what and when.

Passwords are hashed with argon2id and are never stored or transmittable in a readable form. When you set one, we check it against a public list of passwords exposed in known breaches, using a method that never sends your password or its full hash anywhere.

05

Where data is processed

Our application is hosted in the United States. Information you provide through the website may be processed there by Vered and its service providers. The subprocessor list describes those providers. Contact us for information about the locations and transfer arrangements relevant to your use. This website notice does not replace the data-processing or international-transfer arrangements required for customer tenant data.

06

Security

We enforce tenant isolation at the database, least-privilege access by role, multi-factor authentication on regulated workflows, and an append-only audit trail. No system is perfectly secure, and we do not claim otherwise; what we claim is that each of those controls is enforced in code, and the security page points at where.

To report a security concern, contact security@vered.io.

07

Your choices

For data we hold about you as a site visitor or prospect, you can ask us what we hold, ask us to correct it, or ask us to delete it. Write to privacy@vered.io and we will respond.

For data held inside a customer’s tenant, the request goes to that customer, as clause 1 explains. We will support them in answering it.

If we contact you about Vered, we identify ourselves and provide a way to opt out. We honour objections to direct marketing and keep the minimum suppression information needed to avoid contacting you again. Where prior consent is required, we obtain it before marketing.

Depending on the applicable law and circumstances, you may also have rights to restrict processing, object, or receive portable data. We may need to verify identity and authority before responding, and some records may need to be retained under applicable exceptions. If UK law applies, you can raise a concern with the Information Commissioner’s Office. You may contact us first, but do not have to do so.

08

Children

This website and its discovery service are intended for business users and are not directed at children. Customer tenant records are handled on the customer’s instructions, as explained above.

09

Changes and contact

If we change this notice, the effective date at the top of the page changes with it. Changes that materially affect how we handle customer data are communicated to customers under their agreement, not by a silent edit here.

Privacy and data-processing questions: privacy@vered.io.


Questions about this document go to privacy@vered.io.

← All legal notices