Legal
Privacy Policy
How Engramn collects, uses, and protects data — for the dealerships that use our product, and for the people whose Google reviews pass through it.
- Last updated
- 2026-08-07
- Effective
- 2026-08-07
Who this applies to, and in what role
- When you are our customer (dealership staff with an Engramn account) — Engramn is the controller of your account, billing, and usage data.
- When we handle your locations' review data— Engramn is a service provider / processor acting on the dealership's documented instructions. The dealership decides what is collected and how long it is kept. Our handling is governed by the customer agreement and the Data Processing Addendum, which control over this policy in the event of a conflict.
- If you wrote a review — you are not our customer and never signed up with us. We hold the review for the dealership, and a request about it can be sent to legal@watchgridstudio.com or to the dealership directly.
How your Google Business Profile connection works
Engramn does not connect to Google directly. We use Zernio, our Google Business Profile connectivity provider, as our sole integration path. When you connect a location, you are taken to a Google consent screen and you authorize Zernio's Google application to access the Google Business Profile you select. Engramn never receives, stores, or has access to your Google account password or your Google OAuth tokens.
Once connected, Zernio sends us new and updated reviews for that location and posts your approved replies back to Google on your behalf. You can disconnect a location at any time from Settings, and you can revoke access directly in your Google Account security settings.
AI processing
To draft a reply, we send the review's text, the reviewer's display name, and your location's brand-voice settings to our AI provider, Anthropic, over its business API. We also run periodic batch classification (sentiment and theme) the same way. Our current and authorized AI providers are always listed on our Subprocessors page.
Drafts are made to sound like your store by retrieving examples from your own location's previously sent replies. Those examples never leave your organization and are never used to generate drafts for any other Engramn customer.
We keep records of AI usage — model, token counts, cost, latency, success or failure — for billing and reliability. These records do not contain the review text or the generated reply.
What we collect and why
| Group | What | Source | Why | Retention |
|---|---|---|---|---|
| Account & workspace | Staff email, name, role | You, when you accept an invite and sign in | Account access and workspace membership | Life of the account |
| Location name, connection status, last synced time | Configured when you connect a location | Operate the review-reply workflow for that location | Life of the account | |
| Review & reply data | Reviewer display name, review text, star rating, review date, external review ID, plus the sentiment and theme our AI derives from the review | Synced from Google Business Profile via Zernio | So your team can read, organize, and reply to reviews | Life of the account |
| AI-drafted reply text, final sent text, confidence score, policy flags, who sent it | Generated by our AI; edited and sent by your team | Draft, approve, and audit every reply | Retained as audit evidence after account deletion — see Retention and deletion | |
| Brand-voice tone, phrases, and sign-off settings | Written by you | Make drafts sound like your dealership | Life of the account | |
| AI usage metadata — provider, model, token counts, cost, latency, outcome | Generated automatically for every AI request | Billing and reliability | 24 months | |
| Billing & technical | Stripe customer and subscription IDs, connected-location counts | Stripe, and your own connect/disconnect actions | Calculate and process your subscription | 7 years — tax and accounting obligation |
| IP address, request metadata | Automatically, from your use of the site | Operate and secure the service | 30 days |
We do not collect: advertising identifiers, cross-site tracking data, data from data brokers, biometric data, precise geolocation, or data we know to be a child's.
Who can see your data
- Your own organization's members, per role. Enforced at the database layer by row-level security, not only in application code.
- Our subprocessors, for the purposes listed there.
- Engramn support and engineering staff, under least-privilege access, only to operate the service, investigate a problem, or respond to your request — and access is logged.
- Legal process, with notice to you where we are permitted to give it.
- A successor in a merger or acquisition, subject to this policy.
Subprocessors
We use a small number of subprocessors to run Engramn. The full list, what each one handles, and its status — active or merely authorized — is on our Subprocessors page. We give 30 days' notice before adding a new subprocessor and you may object on reasonable data-protection grounds.
Retention and deletion
| Data | Retained | On termination |
|---|---|---|
| Account & workspace | Life of account | Available for export for 30 days after termination, then deleted at the end of that window |
| Reviews & replies | Life of account | Available for export for 30 days after termination, then deleted at the end of that window; sent-reply records are retained as denormalized audit evidence and disassociated |
| AI usage metadata | 24 months | Retained (contains no content) |
| Billing records | 7 years | Retained — tax and accounting obligation |
| Request logs | 30 days | Rolls off |
A reply already published to Google lives on Google. Deleting Engramn's copy does not unpublish it — the unsend path in the product is a separate action.
Security
- Encryption in transit and at rest
- Database-level tenant isolation via row-level security
- Secrets are never shipped to the client bundle
- Signature-verified webhooks
- Scoped, per-tenant API keys
- Least-privilege staff access
Your privacy rights (US)
Depending on where you live, you may have the right to know what personal information we hold about you, access it, correct it, delete it, receive a portable copy, opt out of sale or sharing or targeted advertising, limit use of sensitive personal information, appeal a denied request, and not be retaliated against for exercising any of these rights. We offer one combined process for all US states rather than a separate one per state.
To exercise a right, email legal@watchgridstudio.com. We respond within 45 days, extendable by another 45 when needed, and we verify your identity in proportion to the sensitivity of the request. If a request concerns review data we hold for a dealership, we route it to that dealership and confirm with you.
Cookies
We use Supabase authentication cookies to keep you signed in, plus Vercel's operational request handling. We do not use advertising cookies, analytics cookies, or third-party trackers. There is no consent banner, because there is nothing to consent to.
Where your data is processed
We store your data in the United States. Some of our service providers operate outside the United States.
If you are in the EEA or UK, we handle your data as described in this policy. Where GDPR applies to a dealership's use of Engramn, the dealership is the controller and Engramn is the processor. Contact legal@watchgridstudio.com to exercise your rights.
Children
Engramn is not directed to children under 13, and we do not knowingly collect personal information from anyone under 13. If you believe a child under 13 has provided us with personal information, contact legal@watchgridstudio.com and we will delete it.
Changes to this policy
We will give at least 30 days' notice of any material change to this policy, both here and inside the product. The date at the top of this page always reflects when the text was last written.
Contact
WatchGrid Studio LLC, a Texas limited liability company doing business as Engramn. Privacy questions, and requests to exercise any right described above: legal@watchgridstudio.com. We answer every request that reaches that address.