Privacy & Cookie Policy

DaGaMa Intelligence L.L.C. ("we", "us", "our"), a Wyoming limited liability company at 30 N Gould St Ste N, Sheridan WY 82801, operates the website at hidagama.com and the DaGaMa family of bots — BoothBot, SourceBot, ExpenseBot, DemoBot, and Gaspar (our email outreach platform at gaspar.hidagama.com) — across Telegram, WhatsApp, WeChat, and web. ExpenseBot currently ships on Telegram + web only; the other bots ship on all four channels. The data controller for personal data collected through these services is DaGaMa Intelligence L.L.C. For all inquiries — general or privacy / data-rights — please use our contact form and select the appropriate topic.

• Account data — email, name, hashed password, role.
• Trade-show capture — business cards you scan, names, companies, phone numbers, emails, voice notes, photos. Stored in a Google Sheet and Google Drive folder that DaGaMa creates and shares with you.
• Communication metadata — Telegram chat ID, WhatsApp phone (E.164), WeChat OpenID — bound to your account so messages reach the right inbox.
• Gmail OAuth tokens — when you connect a Gmail or Google Workspace account to Gaspar (our outreach tool), we store an encrypted OAuth refresh token. We request the scopes needed for outbound sending, alias resolution, label management, and bounce tracking. On paid plans, we additionally request gmail.modify — used exclusively to read Mailer-Daemon Delivery Status Notifications (DSN bounce messages) from your inbox and label them out, so we can detect bounced campaign emails and update your suppression list. We never read or scan any other email. You can revoke access at any time from your Google Account security settings or from your Gaspar accounts page.
• Outreach email data — recipient addresses and merge-field values you upload for Gaspar campaigns. Open events (pixel loads), click events (link redirects), reply events (inbound email to our tracking address), and bounce events (undeliverable addresses) are stored and associated with each campaign.
• Usage analytics (only with consent) — page views, scroll depth, error events. No personal identifiers; aggregated.
• Advertising signals (only with consent) — anonymous browser cookie used by Meta Pixel, Google Ads, and LinkedIn Insight Tag to build retargeting audiences.
• Consent records — your cookie choices + a session id + a daily-rotated hashed IP, kept as proof of consent (GDPR Art 7).

• Provide the service — log you in, deliver bot replies, attach scans to your Sheet.
• Gmail sending (Gaspar) — your OAuth token is used exclusively to send outreach emails that you configure. We never read, search, or modify your Gmail mailbox.
• Outreach tracking — a 1×1 pixel image embedded in sent emails detects opens (with noise filtering for Apple Mail Privacy Protection and Gmail prefetch). Links are rewritten through our redirect endpoint to count clicks. A dedicated reply address on replies.hidagama.com receives replies so we can log them without reading your inbox. Bounced addresses are suppressed automatically to protect your sender reputation.
• Security — fraud prevention, rate limiting, token rotation.
• Analytics & product improvement — only if you consent.
• Advertising — only if you consent to advertising cookies (see Section 4). We share hashed (SHA-256) emails / phone numbers with Meta, Google, and LinkedIn to build retargeting audiences. They cannot reverse the hash to recover your raw email or phone.
• Outlook OAuth tokens — when you connect a Microsoft Outlook / Microsoft 365 account to Gaspar, we store an encrypted OAuth refresh token. We request only the minimum scopes needed to send email on your behalf (Mail.Send + offline_access). We cannot read, modify, or delete any email in your mailbox. Revoke access at any time from your Microsoft account settings (account.microsoft.com) or from your Gaspar accounts page.
• Push-to-Meta audiences (opt-in per campaign) — when you click "Push to Meta" on a Gaspar campaign, we send hashed (SHA-256) versions of the recipient list to Meta Platforms to build a Custom Audience inside your own Meta Ads account. This feature is opt-in per campaign and only available to users with a connected Meta Ads OAuth grant. You can revoke the Meta connection at any time from your Gaspar accounts page, from Facebook Settings → Business Integrations, or by submitting a privacy request via our contact form. See the data-deletion status page.
• Business-card contacts captured via BoothBot — when a DaGaMa user scans your business card at a trade show using BoothBot, your name, email, company, and other card details are stored in the user's private DaGaMa workspace so they can follow up with you. In addition, hashed (SHA-256) versions of those email addresses may be uploaded to DaGaMa's own retargeting audience on Meta Ads so we can show you ads about DaGaMa's products (you are, by handing your card to a trade-show exhibitor, a likely fit for our platform yourself). This processing is performed under legitimate interest (Article 6(1)(f) GDPR) and the U.S. CAN-SPAM business-card exception. Contacts based in the EU, EEA, Switzerland, and the UK are excluded from this audience. You can opt out at any time via our contact form or by clicking the unsubscribe link in any DaGaMa email you receive.
• Legal compliance — tax records, fraud reports, regulator requests.

DaGaMa's use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements. The following is a complete account of what Google user data we access, how we use it, who we share it with, how it is stored and protected, and how long we keep it.

Data Accessed

When you authorize Gaspar via Google OAuth, we request the following scopes (paid plans receive the additional gmail.modify scope for bounce tracking — see Data Usage below):

• https://www.googleapis.com/auth/gmail.send — permission to send email as you from your Gmail / Google Workspace account.
• https://www.googleapis.com/auth/gmail.labels — permission to create + manage Gmail labels we use to organize Gaspar-related messages (the Gaspar/Warmup label for warmup peer mail, and the Gaspar/Reports/Bounces label for processed bounce notifications).
• https://www.googleapis.com/auth/gmail.settings.basic — permission to read your "Send mail as" aliases so the Gaspar compose UI offers them as sender options.
• https://www.googleapis.com/auth/gmail.modify (paid plans only) — permission to read Mailer-Daemon Delivery Status Notifications (DSNs) from your inbox so we can detect bounced campaign emails and auto-suppress those addresses, and to label processed DSNs out of your INBOX into Gaspar/Reports/Bounces. We do not read, scan, or process any other email content. The Gmail messages.list query is hard-coded to from:mailer-daemon OR subject:"Delivery Status Notification" with a 30-day window.
• https://www.googleapis.com/auth/spreadsheets.readonly — permission to read a Google Sheet you explicitly select in the Gaspar contact-import flow. Write, modify, and delete APIs on Sheets are NOT requested.
• https://www.googleapis.com/auth/analytics.readonly — when you connect your Google Analytics 4 property to Gaspar, permission to fetch campaign-attributed sessions, conversions, and behavior metrics. Read-only; we never write to or modify your GA account.
• https://www.googleapis.com/auth/userinfo.email — permission to read the email address of the Google account you're connecting, used as the verified "From" address on outbound campaigns.

Data Usage

• Gmail send token — used exclusively to dispatch outbound emails composed by you (or by you with AI assistance) inside the Gaspar campaign builder. Every send is initiated by an explicit user action in our web app. We do not, and cannot, autonomously send email or trigger sends from anywhere other than the Gaspar UI / scheduled campaigns you created.
• Gmail bounce-tracking (gmail.modify, paid plans) — a background process polls your inbox every 2 minutes for Mailer-Daemon Delivery Status Notifications using the hard-coded query (from:mailer-daemon@googlemail.com OR from:postmaster) (subject:"Delivery Status Notification" OR subject:"Address not found" OR ...) restricted to messages from the last 30 days. For each match, we extract only the bounced recipient email address and the SMTP status code; the body of the DSN is not stored. The DSN message is then labeled with Gaspar/Reports/Bounces and removed from your INBOX label. The bounced recipient is added to your account's auto-suppression list to prevent future campaign sends to that address. No other emails in your inbox are read, scanned, indexed, or accessed.
• Gmail label management (gmail.labels) — used to create/locate the Gaspar/Warmup and Gaspar/Reports/Bounces labels. No message content is read by this scope.
• Gmail send-as aliases (gmail.settings.basic) — used to fetch your verified "Send mail as" alias list once at account connect time, then refreshed on demand when you click Refresh aliases in the Gaspar UI. We never modify your Gmail settings; this scope is read-only against your alias list.
• Google Analytics 4 (analytics.readonly) — when you connect a GA4 property, our 15-minute cron pulls campaign-attributed metrics (sessions, conversions, page views, engaged sessions, bounce rate) filtered by the campaign's UTM parameter via the GA Data API. Aggregated reporting data only — never raw user-level events. We never write to or modify your GA account.
• Sheets read token — used only when you click "Import contacts from Google Sheets" inside Gaspar and explicitly pick a spreadsheet from your Drive picker. We pull only the rows from the sheet you select, parse them into Gaspar's contact format, and discard the access token usage immediately after.
• User email — stored on the connected account record so the campaign sender label matches the connected mailbox.
• No human reading — DaGaMa employees do not read, view, copy, or otherwise access Google user data tied to any individual user account except (a) with that user's explicit consent in a support ticket, (b) when required for security investigations under a legal hold, or (c) when required to comply with applicable law.
• No AI / ML training — Google user data is never used to train, retrain, fine-tune, or evaluate generalized AI or machine-learning models. Per-user campaign AI drafts (e.g. follow-up email body) are generated by DaGaMa Intelligence using only the prospect record you provided and never include the contents of any Google mailbox.

Data Sharing

Google user data is shared only with the third-party subprocessors strictly necessary to deliver the service you requested:

• Cloudflare — hosts our backend (Workers + D1 SQLite). Your encrypted refresh token and Sheet-import rows are stored in our Cloudflare D1 database located in the closest data center to your tenant.
• Google itself — the Gmail send API and Sheets read API are called directly by us using your token to fulfill the request you initiated.
• Resend — when you opt to send via your own custom domain (an alternative to Gmail), Resend handles message delivery. Resend is never used to send through a connected Gmail account; Gmail sends always go directly through the Gmail API.
• We do not sell, rent, or share Google user data with any advertising network, data broker, or other third party.

Data Storage & Protection

• OAuth refresh tokens are encrypted at rest using AES-256-GCM with a per-tenant key wrapped by an envelope master key stored in Cloudflare Secrets. They are never logged, never sent over a non-TLS connection, and never exposed to client-side JavaScript.
• In transit — all traffic between your browser, our Workers, and Google APIs uses TLS 1.2+. Cloudflare's edge network terminates TLS and re-establishes a fresh TLS connection to Google.
• Access control — production database access is restricted to a small number of engineers using Cloudflare Access (zero-trust with Google SSO + hardware key). Production deploys require GitHub branch protection + signed commits.
• Audit logging — every Gmail send and every Sheets read is logged with timestamp, account ID, recipient address (for sends), and Worker version; logs are retained for 90 days for security investigations.

Data Retention & Deletion

• OAuth tokens — kept until you disconnect the account from Gaspar's "Connected accounts" page, or until you revoke the grant directly at myaccount.google.com/permissions. Disconnecting in either place purges the token from our database within 5 minutes.
• Imported Sheet contacts — kept until you delete the audience or the campaign in Gaspar (the contact rows are then hard-deleted from D1 within 24 hours).
• Send / open / click / reply event logs — kept for 13 months for analytics, then auto-purged.
• Right to deletion — submit a request via our contact form with subject "Google data deletion request" and we will purge all data derived from Google APIs tied to your account within 30 days and confirm in writing.
• Account closure — closing your DaGaMa account triggers the same Google-data purge automatically.

Limited Use disclosure

DaGaMa's use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. Specifically:

• We use Google user data only to provide and improve user-facing features that are prominent in the requesting application's user interface.
• We do not transfer Google user data to others unless necessary to provide or improve these features, comply with applicable law, or as part of a merger / acquisition / sale of assets (with users notified in advance).
• We do not use Google user data for serving advertisements.
• Humans do not read Google user data unless we have obtained the user's affirmative consent for specific messages, doing so is necessary for security purposes (such as investigating a bug or abuse), to comply with applicable law, or our use is limited to internal operations and the data (including derivations) has been aggregated and anonymized.

We use four categories of cookies:

• Strictly necessary — login session, CSRF token, load balancing. Always on; cannot be rejected because the site won't work without them.
• Analytics — anonymous usage tracking. Off by default.
• Advertising — Meta Pixel, Google Ads tag, LinkedIn Insight Tag. Off by default.
• Functional — remember language, region, channel choice. Off by default.

You can change your choice anytime using the controls below.

• Cloudflare — hosting, edge compute (Workers), CDN, bot mitigation (Turnstile).
• Google — Drive + Sheets storage (with your authorization), Gemini AI for card extraction.
• Resend — transactional email delivery (verification, retargeting).
• Stripe — payment processing for paid plans.
• Meta, Google Ads, LinkedIn — only if you consent to advertising cookies.
• Telegram, WhatsApp, WeChat — message delivery on the channels you choose.

Your data may be processed outside your country, including in the United States and the European Union. Where required, we use Standard Contractual Clauses (SCCs) approved by the European Commission and equivalent safeguards.

Account data: while your account is active, plus 90 days after deletion. Trade-show captures: kept indefinitely in your own Google Drive (we don't control deletion there). Consent records: 3 years from last update. Logs & analytics: 13 months max.

Depending on your jurisdiction, you have the right to:

• Access a copy of your personal data.
• Correct inaccurate data.
• Delete your account and data ("right to be forgotten").
• Restrict or object to processing for marketing.
• Port your data in a machine-readable format.
• Withdraw consent anytime — see Section 4.
• Lodge a complaint with your local data protection authority.

To exercise any of these rights, submit a request via our contact form.

California residents may opt out of the "sale" or "sharing" of personal information. We treat advertising-cookie use as "sharing" under CPRA. Use the "Reject all" button above, or click "Do Not Sell or Share My Personal Information" in the footer (same effect).

DaGaMa is a B2B service. We do not knowingly collect data from anyone under 16. If you believe a child has shared data with us, tell us via our contact form and we will delete it.

When we make material changes, we bump the policy version and re-prompt you for consent on your next visit. The current version is shown at the top of this page.