Your work stays under your control.

Information we collect

We collect account details, workspace records, client information, agreement text, client requests, form submissions, review actions, form connection settings, destination recipient addresses and endpoint URLs, delivery attempts, connection health, usage records, support messages, client approval evidence, invoice status, and billing identifiers needed to provide the service. Approval evidence can include the approved version, comment, timestamp, and hashes derived from network and browser information. Stripe receives payment details directly. We do not store raw card numbers, bank details, or Stripe passwords.

How we use information

We use this information to authenticate users, operate Scope Guard and Form Guard, produce requested assessments, maintain review and audit history, process subscriptions, prevent abuse, support customers, deliver approval requests, attribute change order value, detect replay or abuse, and improve reliability.

Client approvals and connected Stripe accounts

An agency can send a protected change order approval link to a client. We retain the exact version presented, the decision, optional comment, time, and limited hashed technical evidence. An approval does not create a payment. After approval, an authorized agency user can create and send an invoice inside the agency's connected Stripe account. The agency remains the merchant of record and Stripe hosts payment collection.

Form Guard delivery

Observation copy records and assesses a server supplied copy while the website's existing delivery remains active. Managed delivery sends approved or safely routed submissions to email recipients or signed webhook endpoints configured and verified by an authorized workspace user. These deliveries can include the sender name, email, message, decision status, source, and timestamps. Delivery history and failures remain available for review and retry.

Source keys are stored as hashes. Retained signing credentials are encrypted. Email destinations receive a confirmation request before use. Form Guard does not accept form attachments in this version.

Removing a delivery destination erases its saved address, endpoint, signing credential and verification material while preserving delivery history. Disconnecting a protected site invalidates its installation key and erases retained platform signing material.

Service providers

We use service providers for hosting, database and authentication, payment processing, email delivery, and AI processing. These currently include Vercel, Supabase, Stripe, Resend, Microsoft, and the AI services described on our data handling page. They process information for the functions we request from them.

AI processing and human review

Scope Guard and Form Guard send the minimum available context needed for an assessment. Outputs can be uncertain or incorrect. The product keeps decisions reviewable and does not replace legal, professional, or business judgment. Do not submit passwords, payment details, or unnecessary sensitive information.

Retention and deletion

Workspace records remain available while an account is active and while reasonably needed for service, security, billing, or legal obligations. Automatic retention cleanup is not currently enabled. You can request an export, correction, or deletion by contacting support. Provider backups can remain until their normal backup cycle completes.

Google account and Gmail data

If you connect Gmail, Agency Guardrail receives your Google email address and read only access to Gmail messages so it can identify client requests for Scope Guard. We use Google user data only to provide features you request. We do not sell it, use it for advertising, or use it to train general AI models. OAuth credentials are encrypted. The product is designed to retain derived client records and limited supporting evidence instead of permanent copies of entire mailboxes. You can disconnect access and request deletion by contacting support.

Agency Guardrail's use and transfer of information received from Google APIs follows the Google API Services User Data Policy, including its Limited Use requirements.

Security and account choices

We use organization scoped access controls, protected credentials, encrypted transport, and provider security controls. No system can guarantee absolute security. Keep your account credentials private and contact us if you suspect unauthorized access.

Contact

For privacy questions, exports, corrections, or deletion requests, email support@agencyguardrail.com. We may update this policy as the product changes and will publish the current effective date here.