Contact ussales@ventavid.com
VentaVid
Home / Product / Privacy and retention
Venta Capture · Feature

Kept as long as you say, then gone

The first question a privacy officer asks is what you keep and for how long. Venta Capture, a product of VentaVid, is a guided visual capture platform: your customer, tenant, driver or contractor films what you need on their own phone, guided step by step, with no app and no account, and it arrives as a sealed, structured case in your team's inbox. What happens to that case afterwards is set by you, and it is written down for the customer before they start.

Encrypted in transit and at rest. Retention you configure. Raw IP address deleted after 14 days by default.

Security and retention card

Without it

Video of a customer's living room, a driver's licence plate, a tenant's voice. This is personal data, and today it sits in WhatsApp threads on private phones, in mail attachments and in a shared drive nobody cleans up.

Insurers, housing associations and public bodies cannot answer "where is this footage and who has seen it".

Consent is assumed, not asked, and the privacy statement the customer should have read is nowhere near the camera.

Nothing is ever deleted, because nothing was ever scheduled to be.

How it works

01

Send the link with consent built in

The customer opens a secure personal link. Before the first step, they see your consent line with a link to your own privacy statement, and a tick is required to start.

02

Guided capture, with the customer in control

The flow asks for the camera and the microphone in the browser. Location is optional: if the customer declines, the case says so plainly and treats it as neutral.

03

A sealed case, encrypted on the way and at rest

The submission travels encrypted and is stored encrypted. It gets a server-verified receipt time and a seal, and every action on it is logged with an account and a time.

04

Retained, then purged

The case is kept for the period you configure and auto-purged afterwards. The raw IP address goes earlier: after a configurable number of days, 14 by default.

What it delivers

Your privacy officer says yes

Encryption in transit and at rest, GDPR-ready processing, a configurable retention period with auto-purge and an audit log are the answers to the first four questions on the checklist. No certifications are claimed on this page; ask us what you need for procurement.

Your customer knows what you keep

The consent screen names your organisation, links to your privacy statement and says that recordings may be processed with AI and external services. The customer ticks before filming, and what was shown is logged.

Nothing is punished for privacy

A customer who declines to share location is not flagged. The case records "location declined by the submitter", neutral, never counted anywhere.

Send the consent screen to your privacy officer before you send a single link.

In the product

The landing page carries a configurable consent line with a link to your own privacy statement, a mandatory tick before the flow starts, and a disclaimer that recordings may be processed with AI and external services (for analysis and transcription). Notices can be shown right before filming or at the start of the flow, with "ask for a tick" and "store what was shown" so the consent moment is part of the record.

Retention is set per organisation and enforced by auto-purge

Separately, raw IP retention runs from 1 to 30 days (default 14); after that, the raw IP address is deleted while a non-identifying network fingerprint stays for reuse signals.

Location is optional

When a submitter declines it, the case states it as a neutral fact with no effect on any signal. The location that is shared is labelled as shared by the customer, not verified by us.

Access is scoped: visibility per form (everyone or named people), roles with only the permissions a job needs, and an audit log of who did what and when. Data is encrypted in transit and at rest.

Sectors that ask these questions first: insurers and property managers and housing associations. What we do and do not claim about signals is on claims discipline; the signals that use device and network context are explained on device integrity signals. Consent texts are edited in the flow builder. Glossary: GDPR, data retention, data subject access request. Background: insurance claim documentation.

Consent screen on the phone
When location is refused

Questions

How is the data protected?

Encrypted in transit and at rest, processed in a GDPR-ready way, with a retention period you set and auto-purge when it ends. Every action on a case is in the audit log.

How long do you keep the raw IP address?

A configurable number of days between 1 and 30, 14 by default. After that it is deleted; a non-identifying network fingerprint remains for reuse signals.

Does the customer have to share their location?

No. Location is optional. A refusal is recorded as a neutral fact in the case and never counts against the submission.

Does the customer consent to anything?

Yes, before filming: a consent line you write, linked to your own privacy statement, with a mandatory tick, plus a disclaimer that recordings may be processed with AI and external services. What was shown can be stored with the case.

Can we set different retention for different processes?

Retention is configured for the organisation and enforced by auto-purge. If your processes need different periods, discuss it on the setup call so the account is set up around them.

Are you certified?

We do not claim certifications on this page. Ask us for the documentation your procurement process needs.

Related features

Set the retention before the first link

Consent up front, encryption throughout, deletion on schedule. Then send the first flow.

Live in 10 minutes. Stuck? Book a free setup call and we build your first flow together.