Encryption in transit and at rest
Every page of the app, every API call and every connection between our servers uses TLS. Plain HTTP requests are redirected to HTTPS, so nothing you type travels in the clear.
Data at rest sits on encrypted disks in a data center in the EU. Backups are encrypted as well and are kept for a short rolling window, so an old copy cannot linger for years.
Sensitive fields get a second layer. Mailbox credentials, access tokens and API secrets are encrypted at the application level before they reach the database, so a database copy alone does not reveal them.
- Passwords are stored only as salted hashes. We cannot read them, and support never asks for them.
- New accounts confirm their email address with a one time code before the workspace opens.
- Credentials you save are never shown again in the app, never written to logs and never sent by email.
What the agent can do with your mailbox
The Buy Agent and the Sell Agent send outreach from your own work mailbox, so replies come back to you and your sender reputation stays yours. That is also why mailbox access is the most sensitive thing you give us, and we treat it with least privilege.
- The agent sends only the messages in a sequence you approved, under the DomainAgent buyer or seller identity.
- The agent reads only the threads that belong to a deal, matched by the message it sent. It does not index, store or summarize the rest of your mailbox.
- Mailbox credentials are encrypted at rest and decrypted only inside the job that sends or checks replies.
- You can disconnect a mailbox at any time in settings. The stored credentials are deleted at that moment, and you can also revoke the access from your mail provider's side.
We suggest a dedicated mailbox for deal work, such as deals@ on your own domain. It keeps outreach apart from your daily inbox and makes the access boundary easy to see.
Approval gates on every binding step
An AI agent that negotiates on your behalf has to be fenced in. DomainAgent negotiates only inside the band you set for each deal: the opening offer, the step size and the ceiling (or the floor, when you sell).
Anything that would bind you needs your explicit click in the deal room. That covers a binding offer, the acceptance of a price and the start of escrow. Until you click, the button stays amber with the words "awaiting your approval", and the agent waits.
- The agent cannot raise its own ceiling or lower its own floor.
- A counter-offer outside your band is shown to you, not answered.
- Every approval is stored with the user, the time, the amount and the deal.
Read more about how the agent works a counter-offer on the domain negotiation page.
An audit log of every agent action
Every deal has a timeline: research results, each email sent and received, each offer and counter-offer, each approval and the escrow status. You can see what happened and when, in order, without asking anyone.
On the Agency plan the audit log covers the whole workspace. It records every agent action and every approval across all users and client workspaces, so an agency can show a client exactly who approved a price and when.
Roles, seats and single sign-on
Each plan includes a set number of seats, from 1 on Investor to 25 on Agency. You decide who joins your workspace, and you can remove a person at any time.
Agency adds roles, so you can let a colleague research and draft without letting them approve binding offers. It also adds single sign-on with SAML and OIDC, so access follows your own identity system, and client workspaces that keep each client's deals, portfolio and mailbox apart.
We never hold funds
DomainAgent is software. It does not take custody of the money for any domain, and it never asks a buyer or a seller to send money to us.
When a price is agreed and you approve, the deal moves to a licensed escrow partner. The buyer pays the escrow partner, the seller transfers the domain, the buyer confirms receipt and the partner releases the funds. The partner works under its own terms and charges its own fee, set by the partner. The deal room shows the escrow status so you can follow the transfer.
Your subscription is paid by card at checkout through a payment processor, with 3D Secure confirmation. Card numbers go straight to the processor and never touch our servers. We store only what we need to show your billing history, such as the plan, the amount and the last four digits of the card.
Protecting the people we contact
Security also means treating domain owners and prospects fairly. The agent uses only contact data from public sources, and every outreach email carries a clear sender identity and a one-click opt-out.
- Opt-outs go to a global suppression list shared by all accounts, so a person who says stop is not contacted again by any DomainAgent user.
- The suppression list keeps a one way hash of the address and the domain name, not a readable contact record.
- Each connected mailbox has a daily send cap and a gradual warm-up, and each plan has a monthly ceiling for new contacts and outreach emails.
The full set of rules is on how the agent stays inside the rules.
Data retention and deletion
We keep data for as long as it serves your account and no longer.
- Deal data, messages and the audit log stay while your workspace is active, so the history of each deal is there when you need it.
- When you close your account, workspace data is deleted within 30 days, and encrypted backups roll over shortly after.
- Billing records are kept for as long as tax and accounting law requires.
- Anonymous demo checks from the homepage are deleted after 30 days unless you create an account and keep the report.
- You can ask for deletion of a single deal, a mailbox connection or your whole account by writing to support@domainagent.ai.
Details on categories, legal bases and your rights are in the privacy policy.
Responsible disclosure
If you find a security issue in DomainAgent, write to support@domainagent.ai with the subject "Security report". Describe the issue, the steps to reproduce it and the impact you see.
We confirm receipt, look into every report and tell you what we changed. Please give us a fair chance to fix the issue before you share it publicly, test only with your own account and data, and do not access or change data that is not yours. We do not take legal action against good faith research that follows these rules.