Security and customer control

Verify Presence combines product controls with disclosed assisted delivery while keeping customer authority explicit.

Account protection

Google provides authentication. Customer data access is checked again in the server-side data layer and database row policies using organisation membership.

Approval boundary

AI may diagnose and draft, but cannot approve its own work. Only an owner or approver can decide. Every decision is bound to one immutable version; changing the wording requires a new decision.

Controlled execution

Approved work enters an idempotent, leased queue. Publishing is limited to configured HTTPS destinations on a server allowlist. Secrets stay in the host environment, not the customer browser or database destination record.

Evidence and recovery

Successful connectors must return before and after snapshots plus a rollback reference. Execution, failure, actor, destination, and remeasurement events are recorded for review.

Measurement privacy

AI measurement is a Business service and does not begin merely because someone signs in or creates a Free profile. Before a named provider receives the approved public-business scope, the organisation must have the required authority and service state. Answer generation is kept separate from target classification.

Billing boundary

Production Business Checkout is available to an eligible signed-in organisation owner who accepts the current Business terms and B2B confirmation. Checkout and the Customer Portal are hosted by Stripe. Card details are entered directly into Stripe and are not stored by Verify Presence. Server-only keys and signed webhooks bind each subscription event to the configured product, environment and organisation; duplicate or older events cannot silently broaden access. No charge is created by signing in, creating a Free profile or viewing Pricing.

Platform separation

Recommendation information cannot alter Atlas Eligibility or Verified Dispatch. Verified Delivery observations are quarantined for review and cannot automatically change trust or verification.

Report a concern

Report suspected unauthorised access, unsafe publishing, or data exposure to hello@verifypresence.com. Do not include passwords or private keys in email.