Skip to main content
Legal

Security at AngelSend

Last updated: August 11, 2026

Our Approach to Security

AngelSend, operated by AW3 Technology, Inc., handles data that matters to your business: your contact lists, your email content, your connected mailboxes, and the conversations your outreach generates. This page describes the technical and organizational measures we use to protect that data. It is written to answer the questions security reviewers actually ask, and we keep it honest — where a control is provided by an infrastructure partner rather than by us directly, or where a certification is not yet in place, we say so.

Related documents: our Privacy Policy, Data Processing Agreement, Subprocessor List, and Acceptable Use & Anti-Spam Policy.

Infrastructure and Hosting

  • Cloud-native: AngelSend runs entirely on managed cloud infrastructure. Our database, authentication, file storage, and serverless backend run on Supabase, hosted on Amazon Web Services in the United States (us-east-2). We do not operate our own physical servers.
  • Provider certifications: Our infrastructure providers maintain independently audited security programs, including SOC 2 Type II and ISO 27001 for AWS and SOC 2 Type II for Supabase. Physical security, network security, and hardware lifecycle controls for the underlying platform are covered by those programs.
  • Serverless backend: All backend logic runs in isolated serverless functions with short-lived execution environments. Secrets (API keys for our providers, signing keys) are stored in the platform's secret manager, never in source code or client-side bundles.

Encryption

  • In transit: All traffic between your browser, our APIs, and our backend is encrypted with TLS 1.2 or higher. There are no unencrypted endpoints.
  • At rest: Databases, file storage, and backups are encrypted at rest with AES-256 by our infrastructure provider.
  • Application-layer protections: Platform API keys are never stored in recoverable form — we keep only a SHA-256 hash and display the key once at creation. Outbound webhooks are signed with HMAC-SHA256 so your systems can verify payloads came from us. Unsubscribe links are HMAC-signed to prevent tampering.

Tenant Isolation and Access Control

  • Row-level security: Customer data is isolated at the database layer using Postgres row-level security (RLS) policies on customer-facing tables — not just application code. A query authenticated as one workspace cannot read another workspace's rows.
  • Workspaces and roles: Data is scoped to projects (workspaces). Team features use role-based permissions, so account owners control what each team member can see and do.
  • Least privilege internally: Administrative access to production data is limited to the small set of people who operate the service, is credential-protected, and is used for support and operations only.

Authentication and Connected Accounts

  • Platform sign-in: Authentication is handled by Supabase Auth. Passwords are hashed with an industry-standard algorithm; we never store or see plaintext passwords.
  • Mailbox connections via OAuth 2.0: Gmail and Microsoft 365 accounts are connected through Google and Microsoft's own OAuth consent flows. We never see or store your email password. We request only the scopes needed for the features you use.
  • Token handling: OAuth tokens are stored server-side, encrypted at rest, and are never exposed to the browser or other users. Disconnecting an integration in your settings revokes our access and removes the stored tokens.

API and Webhook Security

  • Scoped API keys: Every API key carries an explicit scope list, so a key can be limited to exactly the resources an integration needs. Keys are stored only as SHA-256 hashes.
  • Rate limiting: API surfaces are rate-limited to protect the platform and connected mailboxes from abuse.
  • Signed webhooks: Outbound webhooks include an HMAC-SHA256 signature header computed with a per-endpoint secret, so receivers can verify authenticity and integrity.

Email Sending Safeguards

Because AngelSend sends email on your behalf, protecting your sender reputation is a security concern in its own right. The platform enforces:

  • Per-account sending quotas and rate limits, tuned to provider guidance for connected mailboxes
  • Automated bounce monitoring that pauses sending when bounce rates indicate a list or deliverability problem
  • Automated content screening that blocks messages matching known abuse patterns before they are sent
  • Unsubscribe links in marketing sends, with opt-outs recorded and enforced against future sends
  • Compliance footers (sender identification) on campaign email

Our rules for what may be sent through AngelSend are in the Acceptable Use & Anti-Spam Policy.

AI Data Handling

  • Model providers: AI features (drafting, personalization, the assistant, enrichment research) call third-party model APIs — primarily Anthropic, with OpenAI and others as listed on our Subprocessor List. We send only the data needed to fulfill the specific request.
  • No foundation-model training: We use these providers under API terms that do not permit them to train their foundation models on our customers' data.
  • Customer separation: Your business data, knowledge base documents, and AI memory are scoped to your account. We do not use one customer's data to generate content for another.
  • Google user data: Google user data (Gmail content, calendar data) is handled under the Google API Services User Data Policy, including its Limited Use requirements — it is never used to train AI models. See the Privacy Policy for the full disclosure.

Data Retention, Export, and Deletion

  • You can export your contacts, campaigns, and activity data at any time through the app or API.
  • Disconnecting an integration removes the stored OAuth tokens and revokes our access.
  • On account closure or verified request, we delete your personal data, except where law requires retention. Deletion requests go to will.schulz@aw3.tech.
  • Database backups are managed by our infrastructure provider on a rolling window and age out automatically.

Compliance Status

We answer this section the way we would want a vendor to answer it for us:

  • GDPR / CCPA: We support customers' obligations as a processor: we offer a Data Processing Agreement incorporating the EU Standard Contractual Clauses, maintain a public subprocessor list, and provide export and deletion tooling.
  • SOC 2: AngelSend has not yet completed its own SOC 2 audit. The infrastructure providers that store and process our data (Supabase, AWS) maintain SOC 2 Type II and ISO 27001 programs. If your review requires our own attestation, contact us — we can walk through our controls directly.
  • Security questionnaires: We complete customer security questionnaires and vendor reviews. Send them to will.schulz@aw3.tech.

Vulnerability Disclosure

We welcome good-faith security research. If you believe you have found a vulnerability in AngelSend, email will.schulz@aw3.tech with enough detail to reproduce the issue. A machine-readable contact is published at /.well-known/security.txt.

  • We will acknowledge your report within 3 business days and keep you informed as we investigate and fix.
  • We will not pursue legal action against research conducted in good faith that respects the rules below.
  • Do not access, modify, or delete data belonging to other users; use test accounts you control.
  • Do not run automated scans or tests that degrade the service, and do not use social engineering, phishing, or physical attacks.
  • Give us a reasonable opportunity to remediate before any public disclosure.

We do not currently operate a paid bug bounty program.

Incident Response

If we become aware of a security incident affecting customer data, we triage and contain it, investigate scope and root cause, and notify affected customers without undue delay — including, where personal data is involved and GDPR applies, within the timelines set out in our Data Processing Agreement so you can meet your own 72-hour obligations. Notifications include what happened, what data was involved, and what we are doing about it.

Contact

Security is a conversation we are glad to have directly:

AW3 Technology, Inc.

Email (security reports, questionnaires, privacy and data subject requests, legal and DPA execution): will.schulz@aw3.tech