Cookie Policy

1. Essential cookies

These are required for authentication and for security. Blocking them prevents you from signing in or completing an integration connection.

2. Preference cookies

These remember a choice you made so the product behaves the way you expect. They are functional, they hold no identifier, and clearing them costs you nothing but the preference.

3. Analytics cookie

This cookie is not required for the product to work. It lets VERA's product analytics and session replay group the pages you view into one visit and one browser, as described in the Analytics section below.

4. Browser storage that is not a cookie

VERA stores your light or dark theme choice in your browser's local storage under the key vera-theme. It is read before the first paint so the interface does not flash the wrong theme. It never leaves your browser and is not a cookie.

PostHog keeps a copy of its analytics cookie, and the state of a session replay in progress, in local and session storage. These are cleared with the rest of the site's data.

5. Analytics

Our public marketing pages use Vercel Web Analytics and Vercel Speed Insights. These products are designed to measure traffic and page performance without setting cookies and without building a cross-site profile of visitors, which is why they do not appear in the tables above. The custom events VERA sends to them carry only a closed set of values: an industry slug, which surface a click came from, a numeric position, a dwell time in seconds, and a search term trimmed to 60 characters.

VERA also uses PostHog for product analytics and session replay, on the website, in the app, and on the pages your customers open from a link a business sends. Its scripts load from VERA's own domain and its data is sent through VERA's own domain. It records pages viewed, clicks (including the visible text of what was clicked), the referring page, browser and device type, an approximate location derived from the IP address, and errors. When you are signed in it is linked to your business account, with your name and email address. We use it to find bugs, see which features are used, and improve the product, and for nothing else: it is not used for advertising or shared with ad networks.

A session replay reconstructs the page as you saw it, with clicks, scrolling and page changes. Everything typed into a form field is masked in your browser before it is sent, embedded payment fields are blocked entirely, and inside the app all on-screen text is masked too. Replays are never recorded on the customer pages opened from a link a business sends (payments, estimates, portals, bookings, visits, reviews, document requests and invites), and the secret token in those links, along with secret values such as a password reset token, is removed from every address before it is sent.

6. Third-party cookies

VERA does not embed third-party advertising, retargeting, or social scripts, and does not use Google Analytics, so no third party sets a cookie on our pages. PostHog's cookie is set on VERA's own domain and is listed above.

When you are redirected to a third party to complete a task, that party sets its own cookies on its own domain under its own policy. This happens when you sign in with Google, when you authorize an integration on a provider's consent screen, and inside the card fields on VERA's checkout page, which are served by our payment processor from its own domain. Those cookies are outside VERA's control.

7. Your controls

Every browser lets you view, block, and delete cookies, usually under privacy or site settings. Blocking essential cookies will break sign-in, which is a limitation of how session authentication works rather than a choice we made.

You can turn off product analytics and session replay without affecting how VERA works: block or clear the PostHog cookie and site storage for VERA's domains, or turn on Global Privacy Control in your browser. When your browser sends a Global Privacy Control signal, VERA's pages do not capture product analytics, record a replay, or store the PostHog identifier for that browser.

If you visit from the EU, the EEA, the UK or Switzerland, VERA asks before using analytics: a banner offers Accept and Reject, and until you accept, PostHog is not loaded at all, so it sets no cookie and stores nothing. Rejecting changes nothing about how VERA works. Your answer is kept for 12 months, after which you are asked again.

Anyone, wherever they are, can open Cookie settings (in the website footer, and under Privacy and legal on the Account settings tab) to accept, reject, or withdraw an earlier acceptance. Withdrawing stops capture and replay at once and removes the PostHog identifier from your browser.

VERA does not currently respond to the Do Not Track browser header, which lacks a common interpretation. Because we do not sell or share personal information, a Global Privacy Control signal has nothing further to opt you out of under California law; it is honored as an analytics opt-out regardless.

8. Changes

If VERA introduces another cookie that is not strictly necessary, we will add it to this page before setting it.