Skip to content
  • Product
  • How it works
  • FAQ
  • About
  • Contact
  • Privacy
  • Terms
Sign inCreate an account
  • Product
  • How it works
  • FAQ
  • About
  • Contact
  • Privacy
  • Terms
Sign inCreate an account

Legal

Privacy Policy

Last updated: 15 November 2026

This policy explains what information Sendavio collects, why, where it is kept, for how long, and the choices you have. It describes how the service works today. Sendavio is in early access, and some features described here (Google Sign-In, Slack notifications and mailbox placement tests) are switched on only when they become available.

Contents

  1. Who we are
  2. What this policy covers
  3. Account and sign-in information
  4. Google Sign-In
  5. Sessions, recognised browsers and security records
  6. Organisations, workspaces and teams
  7. Domains and DNS diagnostics
  8. Message tests (uploaded email files)
  9. Mailbox placement tests
  10. Notifications, email and Slack
  11. Connected services and stored credentials
  12. How we use information
  13. Legal bases
  14. Service providers
  15. Cookies and browser storage
  16. Retention and deletion
  17. Security
  18. International processing
  19. Your rights and choices
  20. Children
  21. Changes to this policy
  22. Contact

See also: Terms of Service

1. Who we are

Sendavio is an email infrastructure service available at sendavio.com and app.sendavio.com. Sendavio is operated by Naveed Tabassum, an individual doing business as Event Horizon Growth, based in Pakistan ("Sendavio", "we", "us"). Event Horizon Growth is a business name, not a registered company. The operator is responsible for the personal information described in this policy.

For anything about this policy or your information, write to support@sendavio.com.

2. What this policy covers

This policy covers the Sendavio website (sendavio.com), the Sendavio application (app.sendavio.com) and the emails Sendavio sends. It does not cover websites or services run by others, including the services you connect to Sendavio, which have their own policies.

Sendavio is used by organisations. When an organisation adds people, domains, files or settings to Sendavio, that organisation decides what it adds. Some of that content can include personal information about other people, for example email addresses in an uploaded message. We handle that content on the organisation's behalf, to provide the service.

3. Account and sign-in information

When you create an account and sign in, we collect and store:

  • your name and email address;
  • your password, stored only as a one-way hash (we cannot read it), if you sign up with email and password. A new account must confirm its email address; confirmation and password reset links work for one hour;
  • two-factor authentication details if you turn it on (it is required for some roles and actions): the authenticator secret and your backup codes, both stored encrypted;
  • an optional profile photo you upload, which is cropped and re-encoded in your browser and checked on our server so that no hidden metadata (such as location) is kept;
  • the dates your account was created and last updated, and whether your email address is confirmed.

We use this information to create and secure your account, sign you in and contact you about it. We send account emails such as email confirmation, password reset, sign-in codes and security notices; these are part of the service and are not marketing.

4. Google Sign-In

You can choose to create an account or sign in with your Google account. Sendavio asks Google only for the basic sign-in permissions openid, email and profile. With them, Google tells us your Google account identifier, your email address and whether Google has confirmed it, and your name. Google also offers a profile photo address, which we do not keep.

  • We use this information only to create your Sendavio account, to recognise you when you sign in, and to show your name and email address in your account.
  • We do not request or receive access to your Gmail, contacts, calendar, Drive or any other Google data. We do not keep the tokens Google issues during sign-in: they are discarded once your identity is confirmed.
  • If your Sendavio account uses two-factor authentication, Sendavio still asks for your code after Google confirms your identity.
  • On the sign-in and sign-up pages, Google's sign-in button is loaded from Google. If you are signed in to Google in that browser, Google may show your Google name or photo inside its own button. Sendavio receives nothing from Google until you choose to continue with Google.
  • We do not sell information received from Google, use it for advertising, or share it with anyone except as needed to run Sendavio as described in this policy.

Sendavio's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. You can remove Sendavio's access at any time in your Google account settings, under third-party connections. Google's handling of your information is described in Google's Privacy Policy.

5. Sessions, recognised browsers and security records

  • Sessions. When you sign in, we create a session and record the IP address and the browser's user agent string with it. You can see your active sessions in Settings and sign any of them out. A session ends when you sign out, when you revoke it, after a password reset, or seven days after it was last renewed (it is renewed at most once a day while you use Sendavio).
  • Recognised browsers. To warn you about sign-ins from a browser you have not used before, we place a random identifier in a cookie in your browser and store only a one-way hash of it, together with a short label (browser family and operating system, such as "Chrome on Windows"), the number of sign-ins and when it was first and last used. A sign-in from an unrecognised browser triggers a security email (at most three a day). You can remove recognised browsers in Settings.
  • Abuse prevention. We keep a request counter for each IP address and action (for example sign-in attempts) to stop password guessing and other abuse.
  • Audit log. Security-relevant actions inside an organisation (for example adding a domain, changing a member's role, or a refused action) are recorded with who acted, what they did, the outcome, the time and the IP address. Owners and Admins can review it, as can workspace members whose role includes the workspace's audit log. The audit log cannot be edited.
  • Hosting logs. Our hosting provider records technical request logs (such as IP address, time, the address requested and the response) and keeps them for a short period for security and troubleshooting.

6. Organisations, workspaces and teams

We store the names of your organisations and workspaces, an optional organisation logo (checked and stripped of metadata), members and their roles, and which workspaces and resources each member can access.

When an Owner or Admin invites someone, we store the invited email address, the role offered, who invited them and the invitation's status, and we send the invitation email. We store only a hash of the invitation link's secret; the link stops working after seven days or when it is withdrawn. Only invite people you are permitted to share an email address with.

7. Domains and DNS diagnostics

When you add a domain, we store its name and a unique verification value for the _sendavio-verification TXT record that proves you control it. Unverified claims expire after 14 days.

Sendavio then reads public DNS records for the domain (such as SPF, DKIM, DMARC, MX, MTA-STS, TLS reporting, CAA, DNSSEC and BIMI) and, for MTA-STS, the domain's public policy file over HTTPS. We store the results, findings, the records they were based on, change history, incidents and monitoring settings, so that we can show evidence, detect changes and alert you. These checks read only information that is already public; Sendavio does not scan ports, log in to servers or change DNS records.

DNS lookups are made through public resolvers operated by Cloudflare (1.1.1.1 and cloudflare-dns.com), Google Public DNS (8.8.8.8) and Quad9 (9.9.9.9). Those operators, and the DNS servers of the domain itself, can see which domain names are looked up.

8. Message tests (uploaded email files)

You can upload a sent email as an .eml file (up to 2 MB) to have its authentication, headers, structure, links, HTML and attachments checked. The file is analysed in memory while the upload is processed and is not stored. Attachments are not opened, and links are not visited.

We keep only the resulting report, which contains:

  • the file name, its size and a SHA-256 fingerprint of the file;
  • the subject and the sender's domain;
  • authentication results (DKIM, DMARC and ARC, and the SPF result reported in the message's headers) and the findings;
  • an outline of the message structure and shortened header details, with recipient lists reduced to a count;
  • the host names of links (without paths and query strings that could identify people) and attachment names, types and sizes.

The report contains no body text and no attachment content. Checking signatures requires DNS lookups for the domains in the message (see section 7). Reports are deleted automatically after 30 days, and you can delete one earlier. Upload only messages you are entitled to share.

9. Mailbox placement tests

A placement test shows where a real message you send lands at mailbox providers. When you start a test, Sendavio gives you a test code and a list of test mailboxes that Sendavio owns at Gmail and Outlook ("seed mailboxes"). You send your message, with the code in the subject, to those addresses.

  • Sendavio connects to its own seed mailboxes with read-only permissions (Gmail's metadata permission and Microsoft's Mail.ReadBasic permission). It reads only the labels or folder and the subject line of recent messages, to find the test code. It never reads message bodies or attachments.
  • For each seed mailbox we store where the message was found (inbox, a tab such as Promotions, spam or junk, another folder, or not observed), when it arrived, and when each check ran. We do not store the subject line or the providers' message identifiers.
  • Test results are deleted automatically 30 days after a test is created, and you can delete a finished or cancelled test earlier.
  • The messages you send are delivered to Sendavio's seed mailboxes at Google and Microsoft and stored there under those providers' terms. The seed mailboxes are used for nothing else and only Sendavio can access them. Sendavio's access to them is read-only, so it does not delete messages automatically; messages stay there until they are removed.

Sendavio never connects to your own mailboxes for placement tests.

10. Notifications, email and Slack

Sendavio sends email notifications to members of an organisation, for example about domain changes, monitoring incidents, invitations and security events. You can choose which notifications you receive in Settings; security emails cannot be turned off. For each email we keep a delivery record (recipient, type, status, attempts and the email provider's message identifier). An email that cannot be sent within 48 hours is cancelled instead of being sent late.

An Owner or Admin can connect a Slack incoming webhook so that the organisation's notifications are posted to a Slack channel. The webhook address is stored encrypted and is used only for that purpose. Messages posted to Slack are handled by Slack under its own terms. Slack posting is not switched on yet: a webhook can be saved, but nothing is posted to Slack until it is.

11. Connected services and stored credentials

Sendavio stores few credentials, and each is encrypted with a key that is kept separately from the database: Slack webhook addresses (section 10) and the access tokens of Sendavio's own seed mailboxes (section 9). Sendavio does not ask for your DNS provider, email provider or mailbox passwords or tokens, and does not change your DNS records; any change it suggests is one you make yourself.

12. How we use information

We use the information described above to:

  • provide, operate and maintain Sendavio, including the checks, tests and notifications you ask for;
  • keep accounts and organisations secure, separate each organisation's data, detect abuse and investigate incidents;
  • send account, security and service emails;
  • apply plan and fair use limits;
  • fix problems and improve the service;
  • meet legal obligations and enforce our Terms of Service.

We do not sell personal information, we do not share it for advertising, and we do not use it to build advertising profiles. The Sendavio website and application do not use third-party analytics or advertising trackers, and our fonts are served from our own servers.

13. Legal bases

Where data protection law requires a legal basis (for example in the European Economic Area and the United Kingdom), we rely on:

  • performance of a contract: to provide the service you signed up for;
  • legitimate interests: to keep Sendavio secure, prevent abuse, and maintain and improve the service, balanced against your rights;
  • legal obligation: where we must keep or disclose information by law.

14. Service providers

We use these providers to run Sendavio. They process information for us under their own terms and security controls:

ProviderWhat they do for SendavioLocation
VercelHosts the website, the application and the background workerUnited States (Washington, D.C. region)
NeonDatabase hosting for all stored informationUnited States (AWS us-east-1)
ResendSends Sendavio's emailsUnited States
GoogleGoogle Sign-In, if you use it; Gmail API access to Sendavio's own seed mailboxes; Google Public DNS lookupsGlobal
MicrosoftMicrosoft Graph access to Sendavio's own Outlook seed mailboxesGlobal
CloudflareDNS for Sendavio's domains, routing of email sent to Sendavio addresses, and public DNS lookupsGlobal
Quad9Public DNS lookupsGlobal
SlackReceives notifications only if your organisation connects a Slack webhookGlobal

We may also disclose information if the law requires it, to protect the rights, property or safety of Sendavio, our users or others, or as part of a merger, acquisition or sale of the business, in which case this policy continues to apply to the information transferred.

15. Cookies and browser storage

The Sendavio website (sendavio.com) does not set cookies. The application (app.sendavio.com) uses only first-party cookies that it needs to work. None are used for advertising or analytics.

NamePurposeDuration
sendavio.session_tokenKeeps you signed in (the session itself is stored on our server)Up to 7 days, renewed while you use Sendavio
sendavio.two_factor, sendavio.state and similarCarry a sign-in in progress (the second step of two-factor sign-in, or the return from Google)Minutes
sendavio.step_upRecords that you recently confirmed a sensitive action with your authenticator code10 minutes
sv_browserRecognises this browser so that we can warn you about sign-ins from new ones (section 5)400 days
sendavio.org, sendavio.wsRemember the organisation and workspace you last opened1 year
sendavio.theme, sendavio.onboarding-hiddenRemember display choices (light or dark theme, a dismissed setup guide)1 year

In Production some names carry a security prefix such as __Secure- or __Host-. When you open an invitation link before signing in, the invitation is kept in your browser's local storage until you accept it. Google sets its own cookies when its sign-in button is shown or used; see Google's Privacy Policy. If you block cookies, you cannot sign in to the application.

16. Retention and deletion

InformationHow long we keep it
Account informationWhile your account exists
Email confirmation and password reset linksValid for 1 hour
SessionsUntil sign-out, revocation, a password reset, or 7 days without use
Invitation linksValid for 7 days; the invitation record stays with the organisation's records
Domains and their checks, findings, history, incidents and monitoring settingsUntil the domain is deleted from Sendavio, which deletes them with it
Message test reports30 days, or earlier if you delete them
Placement test results30 days after the test is created, or earlier if you delete them
Queued notification emailsCancelled if not sent within 48 hours
NotificationsUntil the domain or workspace they concern is deleted
Email delivery recordsUntil the recipient's account is deleted
Audit logWhile the organisation exists. Entries cannot be edited or removed through the application and have no fixed retention period yet. They are not removed automatically when an organisation is deleted; we handle them as part of the deletion request (see below).
Database backupsDeleted information can remain in the restore history and backups that our database provider manages until they expire. How long that is depends on our plan with the provider; Neon publishes restore windows of between 6 hours and 30 days for its standard plans. We do not restore deleted information except to recover from an incident.

You can delete domains, message test reports, placement tests, recognised browsers, sessions, Slack connections, logos and profile photos yourself in the application. Owners and Admins can remove members. To delete your account or an organisation, email support@sendavio.com from the address on the account. We first confirm that the request is genuine and that you are authorised to make it (an organisation can be deleted only at the request of one of its Owners). We aim to complete a verified request within 30 days. Deleting an organisation removes its workspaces, members, domains, reports, tests, invitations, connected services and settings. Deleting an account removes your sign-in details, sessions, recognised browsers and memberships; if you are the only Owner of an organisation, ownership must first be transferred or the organisation deleted. Audit log entries are deleted or de-identified as part of the request unless we need to keep them for security, to meet a legal obligation, or to resolve a dispute. Deletion is not immediate in every system: copies can remain in provider-managed backups until they expire, as described above.

17. Security

We protect information with measures that include:

  • encrypted connections (HTTPS) for the website, the application and our providers;
  • hashed passwords, two-factor authentication, and a fresh authenticator code for sensitive actions such as changing members' access;
  • database-level separation of each organisation's data, with restricted database roles for each part of the service;
  • encryption of stored credentials (Slack webhook addresses and seed mailbox tokens) with a key kept outside the database;
  • alerts for sign-ins from new browsers, rate limits on sign-in and other sensitive actions, and an audit log.

No service can guarantee complete security. If you believe your account or Sendavio has a security problem, write to support@sendavio.com. If a breach affects your personal information, we will notify you and the authorities where the law requires it.

18. International processing

Sendavio is operated from Pakistan, and the operator accesses information from Pakistan to run and support the service. Sendavio's servers and database are in the United States, and our providers may process information in other countries. If you use Sendavio from outside those countries, your information is transferred to them. Our hosting (Vercel), database (Neon) and email (Resend) providers process this information under data processing terms that include the European Commission's Standard Contractual Clauses for transfers from the European Economic Area; Vercel's and Resend's terms also cover transfers from the United Kingdom and Switzerland. Static pages are delivered through our hosting provider's global network.

19. Your rights and choices

Depending on where you live, you may have the right to:

  • access the personal information we hold about you and receive a copy;
  • correct inaccurate information (you can change your name and photo in Settings);
  • delete your information;
  • object to or restrict some processing;
  • receive your information in a portable format;
  • withdraw consent where we rely on it.

To make a request, email support@sendavio.com. We may need to confirm that the request comes from you. We will answer within the time the law requires. If your information is part of an organisation's content (for example a domain or a report), we may pass your request to that organisation. You also have the right to complain to your data protection authority.

We do not sell personal information or share it for cross-context behavioural advertising, as those terms are used in California law.

20. Children

Sendavio is a business service and is not intended for children. You must be at least 18 years old to create an account, and we do not knowingly collect information from children. If you believe a child has given us information, contact us and we will delete it.

21. Changes to this policy

We will update this policy when Sendavio changes how it handles information, and change the "Last updated" date at the top. For material changes we will give notice by email or in the application before they take effect, where reasonably practicable.

22. Contact

Questions, requests and complaints about privacy: support@sendavio.com.

Read our Terms of Service.

OwnershipSPFDKIMDMARCMXTransport

Every signal.
One clear answer.

Understand your sending infrastructure, investigate with evidence, and stay in control of every change.

Create an account

Platform

  • Features
  • AI Engineer
  • Inbox placement
  • Monitoring
  • Integrations

Explore

  • How it works
  • Free tools
  • Pricing
  • FAQ
  • Available today

Account

  • Create an account
  • Sign in

Company

  • About Sendavio
  • Contact
  • Support

Sendavio is operated by Naveed Tabassum, doing business as Event Horizon Growth, based in Pakistan.

© 2026 Event Horizon GrowthPrivacy PolicyTerms of Servicesupport@sendavio.comEarly access