VETO Run one file with Sebastian

Privacy Policy

What Veto collects, why we use it, who receives it, and when we delete it. This policy covers the public website, Veto accounts, Transaction Links, Review Records, customer-care messages, field-program applications, and support.

Effective August 13, 2026

1. Who we are

Heyneman Company, a Delaware corporation doing business as Veto (“Veto,” “we,” “us,” or “our”) operates the services covered by this policy.

1111b S Governors Avenue, STE 29920
Dover, DE 19904 US
Privacy requests: support@tryveto.com · +1 (818) 533-4120

2. Our role depends on the data

For transaction and participant information that an escrow office or other customer submits to or collects through Veto, the customer is the business or controller and Veto is its service provider or processor. We process that Customer Data for the customer under its instructions and written agreement.

Veto is the business or controller for information we collect for our own website, account administration, billing, security, direct support, field-program applications, and legal compliance. If a signed Customer Services Agreement or data-processing addendum conflicts with this policy, the signed agreement controls for that Customer Data.

3. Notice at collection

The table below describes the categories of personal information we may collect. We do not sell any category of personal information. We do not share personal information for cross-context behavioral advertising.

Category and examples Source and purpose Retention Sold or shared for advertising
Identifiers and contact details. Name, business email, phone, office, mailing address, IP address, account ID. From you, your office, or automatically from your device; used for accounts, requests, support, security, communications, and service delivery. While needed for the request or relationship, then only as needed for legal, tax, security, or dispute purposes. No
Account, professional, and commercial information. Employer, role, permissions, order, billing, application, and service-use records. From you and your office; used to evaluate applications, administer accounts, bill, support, and improve service reliability. Applications: evaluation period plus 24 months. Account and billing records: for the relationship and applicable legal or tax periods. No
Transaction and file information. Party names, property or file references, instructions, responses, source documents, exceptions, and Review Records. From the customer, Transaction Participants, integrations, and service providers; used only for the selected workflow, support, security, export, and deletion. Under the customer’s signed agreement and active data schedule. Veto’s standard schedule is described in Section 8. No
Financial and other sensitive information. Account and routing details, wire or disbursement instructions, bank-account signals, and related nonpublic personal information. From the customer, participant, or enabled provider; used to carry out the selected transaction-review workflow and protect against fraud or misuse. The transaction-data schedule above. We do not keep it longer for advertising, profiling, or general product training. No
Identity-verification information. Government-ID data, selfie or video, provider inquiry ID, result, and supporting signals. A provider may derive face geometry or other biometric information. From you and Persona when an office enables an identity workflow; used only to perform the requested check, prevent fraud, and give the office limited source evidence. Under the transaction schedule and the earlier deadline in our Identity and Biometric Information Notice. No
Communications. Email, SMS, support messages, call metadata, consent records, and recordings when all required consent is obtained. From you, your office, and communications providers; used to deliver service messages, provide support, document consent, and protect the service. While needed for the communication, consent proof, support, security, or legal purpose. Transaction content follows the transaction-data schedule. No
Internet, device, and usage information. Browser and device type, pages viewed, typed funnel events, request IDs, timestamps, HTTP status, and security logs. Automatically from your device and infrastructure providers; used for delivery, security, troubleshooting, aggregate analytics, and service reliability. Operational logs: generally 90 days, then deleted or aggregated. Plausible aggregate website statistics: rolling 24 months. No
Fraud and security indicators. Hashes, tokens, repeated-device or instruction signals, risk indicators, and related inferences. Derived from authorized service use and providers; used only to prevent, detect, or investigate security incidents or malicious, deceptive, fraudulent, or illegal activity. Deleted with transaction data unless a documented, lawful fraud or security schedule permits a minimized indicator to be kept longer. No

4. Where information comes from

  • directly from you when you visit, apply, contact us, create an account, or respond;
  • from the escrow office or other customer that asks us to support its workflow;
  • from integrations and providers you or the customer choose to use; and
  • automatically from browsers, devices, and infrastructure when you use the Services.

5. How we use information

We use personal information to:

  • provide the website, accounts, Transaction Links, checks, messages, exports, and Review Records;
  • follow a customer’s documented instructions and support its selected workflow;
  • authenticate access, separate customers, prevent abuse, and investigate security or fraud;
  • provide support, billing, service notices, and field-program or sales responses;
  • monitor reliability and understand aggregate website use;
  • comply with law, enforce agreements, and establish or defend legal claims; and
  • create properly aggregated or de-identified statistics that cannot reasonably be linked back to a customer, transaction, or person.

The office decides. Veto records the review.

A Veto check, signal, or automated tool supports the office’s review. Veto does not use Customer Data to make a final decision about moving funds, credit, employment, insurance, housing, or another legally significant outcome.

6. AI and model training

Veto may use automated tools to provide a feature that a customer selects. We do not use Customer Data—including transaction content, nonpublic personal information, identity materials, communications, or Review Records—to train, fine-tune, or improve a general-purpose artificial-intelligence or machine-learning model. We do not permit a provider to do so for its own purposes.

A future customer-specific training program would require the customer’s prior written opt-in and an update to the applicable notice and agreement. We may use properly aggregated or de-identified information that cannot reasonably be linked to a customer, transaction, or individual to operate, secure, analyze, and improve the Services. We do not try to reidentify it.

7. Fraud and security signals across customers

Where a customer agreement and law permit it, Veto may compare minimized signals across customers only to prevent, detect, or investigate security incidents or malicious, deceptive, fraudulent, or illegal activity. We reduce identifiability where reasonably practical and do not expose one customer’s raw data, nonpublic personal information, or transaction details to another customer.

We do not use these signals for advertising, data brokerage, general model training, credit or eligibility decisions, or unrelated commercial purposes. A signal is evidence for the office to review—not a verification, denial, or instruction to move or withhold funds.

8. Close, export, retention, and deletion

The customer’s signed agreement and active data schedule control retention of Customer Data. Unless an Order Form states another schedule, Veto uses the standard schedule below. Veto does not start the standard deletion clock until both Close and successful export delivery or download are recorded.

Promptly after the customer records a transaction as finally disbursed, completed, or cancelled (“Close”), Veto will generate a final export of then-existing transaction-specific Customer Data and finalized Review Records. We will deliver it to the customer-controlled destination in the Order Form or make it available for authenticated download, then record successful delivery or download.

Under the standard schedule, thirty days after the later of Close and recorded successful delivery or download, Veto deletes transaction-specific Customer Data from active Veto systems and requests deletion from direct service providers where the provider supports or is required to perform that deletion. If Veto has not recorded successful delivery or download, we will not knowingly delete the only copy available through the Services and will notify the customer.

Routine backups may retain deleted data until they cycle out under the backup schedule. Backups are used only for disaster recovery, and deletion records are reapplied before restored data becomes available for ordinary use. Veto may retain transaction data longer only when required by law, a documented legal hold or active claim, an active security-incident investigation, or a lawful limited fraud or security schedule.

Veto may keep a minimal non-content deletion receipt: an opaque record identifier, deletion date, policy version, export-delivery receipt, and non-reversible digest. The receipt does not contain account or routing values, participant identity, property address, or the Review Record.

The customer is responsible for keeping its exported records for the period required by its regulator, license, escrow instructions, contracts, and policies. Veto’s export is not the customer’s regulatory archive unless a signed Order Form expressly says so.

9. When we disclose information

We disclose personal information only:

  • to the customer that controls the transaction workflow;
  • to service providers needed to host, secure, communicate, support, or provide a selected feature;
  • on the customer’s documented instruction or with your direction;
  • when law, subpoena, court order, or a valid government demand requires it;
  • to protect users, investigate fraud or security, or enforce our agreements; or
  • as part of a financing, merger, acquisition, reorganization, or sale, subject to appropriate confidentiality and privacy protections.

See the current Subprocessor List. Service providers must use the information only for specified services and protect it under written terms.

10. Website analytics, cookies, and tracking

Veto uses Plausible to count page views and typed funnel events with allowlisted properties. We do not send free-text form values, Transaction Link content, or raw AI demo transcripts to marketing analytics. Plausible does not use advertising cookies on our site.

We do not use cross-context behavioral advertising. Because of that, we do not respond differently to a legacy browser “Do Not Track” signal. Where legally required, we treat a recognized Global Privacy Control signal as a request not to sell or share personal information; Veto does neither. Third parties may collect information only when you choose to open their service, such as scheduling, identity, or bank-connection tools.

Read the Cookie and Local Storage Notice for details.

11. AI website demo

If a Veto website demo lets you submit voice or text, the demo processes only what you choose to send for that session. Do not submit real transaction data, wire instructions, account information, or another person’s private information. Demo sessions are educational and are not part of an office’s live review process.

12. Field-program applications

The field-program form collects name, work email, office, and phone. We keep an application while evaluating participation plus 24 months unless you request deletion sooner or a legal need requires retention. If you choose browser recovery, the form may hold draft answers in your browser’s sessionStorage for up to 24 hours; Veto does not receive them until you submit.

See the Field Program Terms.

SMS customer care

When a buyer verbally opts in to Veto customer-care SMS during an active escrow transaction, Heyneman Company, doing business as Veto, collects and uses the buyer’s mobile number to send non-promotional messages about a review-request link for an active escrow file, reminders while the response is open, and notice when Veto records the response. A participating escrow office introduces the program and assists Veto with collecting and recording consent; Veto is the sender. Reply STOP to opt out or HELP for help. See the SMS program page.

We will not share mobile numbers, mobile opt-in information, or consent with third parties or affiliates for promotional or marketing purposes. We use this information to deliver the consented messages, operate STOP/HELP support, document consent, and provide related transactional customer care only.

14. Your privacy rights

Depending on where you live and which law applies, you may have the right to request access to, correction of, deletion of, or a portable copy of personal information; to know the categories, sources, purposes, and recipients; to limit certain uses of sensitive information; to opt out of sale, sharing, or certain profiling; to appeal a decision; and to receive equal service without unlawful discrimination.

Veto does not sell personal information, share it for cross-context behavioral advertising, or use sensitive personal information for purposes that create a right to limit under California law.

For transaction data controlled by an escrow office, contact that office first. We will help the office respond. For information Veto controls, email support@tryveto.com. State what you want and how we can identify the relevant account or interaction. We may verify your identity and an authorized agent’s authority before completing a request.

15. Security

Veto uses reasonable administrative, technical, and physical safeguards appropriate to the sensitivity of the information, including access restrictions, customer-separation controls, encryption in transit, risk-based multi-factor authentication for designated high-risk actions, and incident-handling procedures. No system is completely secure.

Report a suspected security issue to security@tryveto.com. Do not include account numbers, credentials, or other sensitive transaction content in the first message.

16. Children

Veto is for business and adult transaction use. It is not directed to children under 13, and we do not knowingly collect personal information from them. Contact us if you believe a child submitted information to Veto.

17. United States processing

Veto is based in the United States. If you use Veto from another country, information may be processed in the United States and other locations where listed service providers operate, subject to the customer agreement and applicable law.

18. Changes to this policy

We will post updates here and change the effective date. We will provide additional notice before using personal information for a materially different, incompatible purpose where law requires it. A signed customer agreement controls changes to Veto’s obligations for Customer Data.

19. Contact

Privacy questions or requests: support@tryveto.com or +1 (818) 533-4120.