Effective September 23, 2026
Privacy policy
Asterlo is an outreach workspace that researches companies, drafts email for human review, and — only after you approve an exact message — creates a Gmail Draft for you to edit and send in Gmail. It synchronizes related conversations so outreach can be held for review. It processes only the data needed to do that.
Who we are and how to reach us
Asterlo operates this workspace at asterlo.io. For privacy questions, access requests, or deletion requests, contact privacy@asterlo.io. We respond to verified requests from the account holder.
Data we process
Account and workspace data: your Google account identifier, email address and display name; your organization, memberships and invitations; campaign settings; contacts you enter or import; research gathered from official company pages; generated message versions, approvals and audit events.
Google user data: if — and only if — you separately connect a mailbox, we process identifiers and approved text for Gmail Drafts created at your request, actual sent text (including Gmail-side edits), related incoming replies, delivery notices, and manual conversation activity. We retain identifiers, relevant threading metadata, addresses, timestamps, subject/body text, classification reviews, reports, and approved writing preferences derived from this activity. Messages without a trace to Asterlo outreach are discarded after inspection rather than stored or analyzed by a model. OAuth refresh tokens are encrypted at rest with tenant-bound keys and are never written to application logs.
How we use data
Data is used to authenticate you, isolate your organization from every other organization, validate and manage contact imports, research official company sites, generate outreach that a human reviews, create the exact approved version as a Gmail Draft, deliver approved outreach, and synchronize replies and delivery notices so that future follow-ups stop. Asterlo does not sell personal information, does not use Google user data for advertising, and does not use Google user data to train generalized AI or machine-learning models.
Limited Use of Google user data
Asterlo’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements. Specifically:
- Google user data is used only to provide or improve the user-facing features described above, and only in ways users can see.
- Google user data is not transferred to others except as necessary to provide or improve those features, to comply with applicable law, or as part of a merger, acquisition or sale of assets with user notice and consent.
- Google user data is not used for advertising, and is not sold to anyone.
- No human reads Google user data, except with your explicit consent for a specific message, where necessary for security purposes such as investigating abuse, to comply with applicable law, or where the data has been aggregated and anonymized for internal operations.
Service providers who process data on our behalf
We do not sell or rent data. We use a small number of processors, each bound to process data only on our instructions:
- Vercel — application hosting and request handling (US East). Processes data in transit.
- Neon — managed PostgreSQL storage and encrypted backups (US East). Stores all workspace data, including retained reply content.
- Anthropic and OpenAI — the configured model provider generates outreach and, when requested, classifies tracked replies and reviews related email content and outcomes. For optional AI review, related sent/reply excerpts, preceding conversation context, task content and observed metrics are sent to the configured provider. Approved personal or task writing preferences may also be supplied when drafting within their authorized scope. Synchronization and manual label review do not require a model call. Gmail-derived suggestions remain inactive until separately approved; approving a message or draft is not preference approval. We do not use this data for generalized or cross-customer learning. These providers are used under their commercial API terms rather than consumer products, response storage is disabled where the provider exposes that control, and this data is not used to train their models.
- Sentry — error monitoring. Receives error type, code and stack information only. OAuth tokens, complete message bodies and customer-sensitive data are excluded from logs and error reports by design.
Retention and deletion
Disconnecting a mailbox: disconnect Gmail at any time from Workspace settings → Mailbox. This immediately revokes and erases the stored credential and stops all further Gmail operations. Stored conversations, reports and preferences remain until workspace deletion; retire preferences in the workspace to stop future use. You can also revoke Asterlo from your Google Account permissions.
Deleting your workspace and all of its data: a workspace owner can request deletion from Workspace settings → Data and deletion. The request follows a fixed, automated schedule:
- Immediately: sending pauses, queued work is cancelled, mailbox credentials are erased and pending invitations expire.
- 7 days — a cancellation window during which the owner can reverse the request. Access stays suspended throughout.
- By day 30 — all workspace content is purged: contacts, research, generated messages, approvals, stored draft records, retained conversations, outcome reports and writing preferences. Messages already in Gmail are managed in Gmail. Accounts with no remaining membership are anonymized.
- 90 days after purge — the minimal deletion audit record itself expires. Encrypted backups roll off within 30 days of the purge.
If you cannot use the in-product controls, email privacy@asterlo.io and we will action a verified request on the same schedule. Campaign history, approvals and audit events are retained until the workspace is deleted, because they record who approved which exact message before it was sent.
Security
Asterlo uses tenant-scoped server queries with the organization derived from a trusted server-side session, hashed session and invitation tokens, AES-GCM encryption of OAuth refresh tokens with key versioning, least-privilege scopes, mandatory human approval of the exact immutable message before any Draft or send, and audit logging. No security control eliminates every risk.
Children
Asterlo is a business tool and is not directed to children. We do not knowingly collect data from anyone under 16.
Changes
Material changes to this policy will be reflected in the effective date above and, where the change affects how Google user data is handled, surfaced in the product before it takes effect.