DRAFT - not yet approved by the site owner or reviewed by a lawyer. The statements below describe how the software behaves today; bracketed items are open decisions. Not legal advice.
Privacy Policy
Who we are
Last updated: [DATE - set when the owner approves this text]. Mathematricks - F.Z.E, a Free Zone Establishment with limited liability in the Ajman Free Zone, United Arab Emirates (licence and registration no. 47839, first issued 23 July 2025; authorized capital AED 100,000), with its premises at Office C1-1F-SF11592, Ajman Free Zone C1 Building, Ajman, United Arab Emirates ("dazl", "we"), operates dazl.ai. Privacy questions and requests: privacy@dazl.ai.
What we collect about you (customers)
Account details: your name, email address, optional business name, and a salted scrypt hash of your password (never the password itself). If you sign in with Google, the email address and account identifier Google returns.
Session records: a hash of each sign-in token, a coarse device label such as "Chrome on macOS" (the raw browser header is not stored), and when the session was last used.
Credentials you give us: AI provider keys, enrichment and CRM keys, and your Gmail authorization. These are stored encrypted (AES-256-GCM, with a key held only in the server environment); the secrets themselves are never included in a data export.
Your business profile, the prospects your searches find, the drafts and messages you send, and replies dazl reads (see Gmail below).
What we hold about prospects
dazl finds businesses and business contacts from public sources: company websites, job boards, SEC filings, official business registers, GitHub, news and community sites. Each lead keeps the link to the page it came from.
Where you connect your own Apollo and People Data Labs account, contact details those providers return under your key are added to your leads. With the optional advanced connector, results from LinkedIn and social sites (X, Reddit, Instagram, Facebook, Xiaohongshu, Bilibili) come through your own signed-in session.
When EMAIL_GUESS_ENABLED is turned on, dazl works out a company's address format from personal addresses it publishes on its own site and prepares candidate addresses for people listed there. Those candidates are stored apart from your leads, marked unverified, and are never emailed or used as a recipient. A format is also learned from addresses your own workspace already holds as confirmed (published on a company's own site, or found on your own key), and only for a buyer whose own address the company's site does not print is an address built from it shown to you, labelled "guessed, unverified" (or "guessed, verified" after a successful mailbox check), with the confirmed addresses it was learned from. When a ZeroBounce key is configured, a candidate for a company whose own site states a US address may be sent to ZeroBounce to check whether the mailbox accepts mail (no email is sent to it); only an explicit "valid" answer is recorded as verified, and a catch-all domain never is. The same check may run on a work address that Apollo or People Data Labs found for a US person on your own key but did not verify, when you click Find work email; it is then shown as checked only on an explicit "valid". An address dazl worked out from the pattern in addresses your workspace already holds has not been checked: we never send to it, and we do not offer it for copying until a mailbox check has verified it. Guessed addresses are for US companies only.
When dazl could not read a page itself and verified a lead against a copy of its text, that copy is kept with the lead and expires after 90 days.
Prospect records your searches find - leads, enrichments, drafts and scans - belong to the customer whose search found them: tenant scoping, pinned by the isolation tests, serves them only to that workspace, and no route serves one customer's leads to another. Separately, when an email address becomes a verified dazl signup, activation or payment, dazl processes that exact address across workspaces: it drops the address from every customer's autopilot candidates, stops that address's pending automated sequences, follow-ups and held first touches in every customer's workspace, starts the contacting customer's own onboarding path for it where that customer has opted in, and refuses automated sends to it. The contacting customer sees only a generic policy stop: the conversion kind (signup, activation or payment) does not appear in their stop reasons, lists or data exports. Proof previews emailed to a prospect are bound to the recipient address until claimed. No prospect names, companies or leads cross workspaces. [NEEDS COUNSEL: whether dazl acts as controller or processor for prospect data, and the lawful basis for each jurisdiction.]
How we use it
To run your account, find and score prospects, draft outreach, send the messages you approve (or that autopilot sends under the limits you turned on), keep the service secure, and bill you.
Page text about prospects and your business profile are sent to the AI model provider (Anthropic and OpenAI) whose key the request runs on to score leads and write drafts. If the free trial is enabled, trial scans run on dazl's own Anthropic key; everything else runs on the key you saved.
Gmail
Outreach is sent from your own Gmail account. Connecting it grants send access only (gmail.send).
Reading replies is a separate, optional grant (gmail.readonly). With it, dazl reads the new text of replies in threads it started for you (quoted history is dropped), classifies each reply by rules, and stores the sender, the Gmail message and thread identifiers, a 200-character excerpt, the classification and the received time, shown in your Inbox. It also searches a bounded, consent-disclosed window of mailer-daemon and postmaster delivery-failure notices beyond its own threads and keeps only notices matched to a recorded send; an unmatched notice leaves only its message and thread identifiers, received time and classification. Stored reply records are not deleted automatically today; turning reading off stops future reads and follow-ups but does not delete what is already stored, and deleting your account deletes them with your other workspace data, unless the deletion request asks to keep named tables (sign-in and payment credentials are always erased; the append-only audit records listed under Retention always stay). [NEEDS OWNER: retention period for stored reply records.] dazl reads nothing without this consent. [NEEDS OWNER: Google API Services User Data Policy / Limited Use statement wording.]
Service providers
Google (sign-in and Gmail), Stripe (payments; card details are entered at Stripe, not on dazl), Anthropic (AI models, and the free trial when it is enabled), TinyFish (web search and page fetching), Jina AI Reader (reading public pages), OpenRouter (a free decision model that screens public search results for relevance: only the titles, snippets and addresses of public pages are sent, never your contacts or account data; only when the research lead engine is turned on) [NEEDS OWNER: confirm OpenRouter as a provider before LEAD_ENGINE=research is turned on], and ZeroBounce (checking whether a prepared work address accepts mail; only while the address-format feature below is on and an operator key is set, at most its free monthly allowance for this dazl service). Hosting: AWS (EC2, region us-east-2) at the current deployment [NEEDS OWNER: re-check at launch]. Account emails such as password resets: [SYSTEM EMAIL PROVIDER - NEEDS OWNER]. Unless a system email provider is configured (none is by default), account emails are not sent and are held on the host. The 24-hour deletion under Retention applies only once ACCOUNT_RETENTION_ENABLED is turned on (off by default). [NEEDS OWNER: choose the provider before account emails are enabled, turn retention on with it, and confirm both at launch.]
Providers you choose and connect with your own account or key: Anthropic and OpenAI (AI models), Apollo and People Data Labs (contact enrichment), and HubSpot, Pipedrive and an HTTPS webhook you control (lead export to your CRM). Their use of the data is governed by your agreement with them.
Public sources dazl queries receive the search terms it sends - a company or industry name, for the Norwegian business register and UK Companies House a place and industry filter, for SEC EDGAR a city, state and date range, and for the city open-data portals a business category and date range and, for Vancouver, the business names and street addresses of licences already found there (a term can be personal data when it names a person, such as the name or address of a sole trader) - and no account data: company websites and public pages, GitHub, job boards (Greenhouse, Lever, Ashby), the GDELT news index, Hacker News search, SEC EDGAR, city open-data portals (City of Austin building permits, City of Vancouver business licences), the Norwegian business register (Brønnøysundregistrene), careers pages on company websites, Companies House (UK), RSS/Atom feeds you supply, YouTube (through the YouTube Data API), V2EX topics (read directly and through the sov2ex search service), and public job feeds such as We Work Remotely.
Error reports, if an error-monitoring service or an operator alert channel (for example a Telegram bot the operator owns) is configured, carry only the error type, code locations and a request id: never messages, account identifiers, request bodies or personal data. The server's own error log keeps the fuller scrubbed record, including the scrubbed message.
[NEEDS COUNSEL: the sale/share statement privacy laws such as CCPA/CPRA require; no assertion is made until then.]
Retention
Signed-out and expired sessions are kept for 30 days (to show who signed a device out, and when), then deleted. Undelivered account emails held while email sending is not configured are deleted after 24 hours. [NEEDS OWNER: both deletions run only once ACCOUNT_RETENTION_ENABLED=1 is set in production; confirm before publishing.]
Your workspace's audit trail (security, billing, sending and consent actions) is kept until a retention period is chosen; no audit record is deleted automatically today. [NEEDS OWNER: set AUDIT_RETENTION_DAYS, at least 30 days.]
Debug copies of scan inputs and outputs are recorded only if trace capture is turned on, and deleted only under a retention period someone chose. [NEEDS OWNER: confirm DAZL_TRACE_CAPTURE is off in production, or disclose its period.]
Other account and lead data is kept while your account exists. [NEEDS OWNER: retention for an active account's leads and messages, and for backups (not yet implemented).]
Deleting your account
You can download an export of your workspace data in Settings (it asks you to confirm it is you). To delete your data, ask us at privacy@dazl.ai: self-service deletion is not switched on in the current service configuration. The Settings page shows whether deletion is available, and where it is switched on it offers the control, which asks for the workspace id as confirmation and a decision on the opt-out list. A deletion removes credentials and sign-in state first, then queued work, then the rest of your workspace data, except what the deletion request names to keep (never credentials) and the records listed below. It deletes dazl's stored Gmail tokens; the grant in your Google account is separate, and you can remove dazl's access there at any time.
Some records survive deletion because they contain no message content: the audit trail, the record of evidence purges, and consent records. A consent record holds the internal account ID, the action and its time; while your account exists it also holds a short note (the consent policy version or the conversion type). Blanking that note is part of the deletion's final step: the deletion is not marked complete until the note is blank. If that final step fails, the earlier erasure is not undone and completion must be retried (a retry can fail again). Records from before this safeguard are blanked by a scheduled cleanup job when it runs - if a run is delayed or fails, their note stays until a later successful run, so for those older records there is no guaranteed moment by which it is gone. Once 2 years have passed since the deletion completed, the same scheduled cleanup job deletes the consent records in batches on its successful runs, so the last record can go later than that. [NEEDS COUNSEL: confirm the 2-year period, chosen by the owner as a practical window, not from a statute.]
[NEEDS OWNER: whether opt-out (unsubscribe) lists are kept or erased on deletion, billing-record retention, and a grace period before erasure (docs/TENANT-LIFECYCLE.md decisions 1, 2 and 5).]
Your rights
You can ask to access, correct or delete your data at privacy@dazl.ai. [NEEDS COUNSEL: which rights apply by jurisdiction (GDPR, UK GDPR, CCPA/CPRA, PIPEDA) and response times.]
Outbound email and opting out
Every outreach message dazl sends to a prospect (first touch, sequence step, follow-up or re-open) ends with the sender's name, a mailing address and an unsubscribe link, and carries a one-click List-Unsubscribe header. dazl refuses to send to a prospect until the sender has saved a name and a mailing address.
An unsubscribe works at once, with no login: the address is added to that sender's opt-out list, any drafts or approved messages to it are skipped, and follow-up sequences to it stop. It is never emailed again by that sender through dazl. A bounce is handled the same way.
If you received a message through dazl and want your data removed from the sender's workspace, ask the sender, or contact us at privacy@dazl.ai.
[NEEDS COUNSEL: CASL / CAN-SPAM / PECR / GDPR applicability. These features are not a claim that any particular message complies.]