Skip to main content
Updated October 21, 2026. For service, billing or privacy questions, use Support in your Datalayer dashboard. If you cannot sign in, open the support chat on the Datalayer homepage.

Information used to provide the service

  • Account and access: your sign-in name, email and authentication identifiers; account membership; encrypted session cookies; API-key labels, hashes and creation/revocation metadata; connected-client and authorization metadata.
  • Research requests and saved results: the inputs needed to fulfil a search or lookup; requested normalized company or professional-profile details, including work email when explicitly requested and returned; retrieval times and account-scoped saved copies.
  • Usage and billing: request identifiers, input fingerprints, profile identifiers, allowance deductions, rate counters, and payment/subscription references and adjustment records. Stripe handles payment entry; Datalayer’s account ledger does not store full card numbers.
  • Email preferences: setup and upgrade reminder choices, opt-out records and generic delivery status. Reminder emails can be turned off in Settings or through their unsubscribe link.
  • Support and account requests: messages and replies, their status and timestamps, and deletion-review records. Do not include passwords, API keys or private profile payloads in support messages.
This information supports authentication, requested research, saved history, accounting, service protection, payment handling and support. Restricted operator tools let the service operator review account, billing and support information.

Services and connected apps

Cloudflare hosts the dashboard, API and account database. Manufact hosts MCP; WorkOS handles sign-in and authorization; Stripe handles checkout and billing; Resend sends account emails and, where enabled, optional setup and upgrade reminders; Mintlify hosts documentation. The public website and signed-in dashboard load Intercom’s support messenger, which can process account identity, support messages, visitor, device and interaction information under its service settings. Customer.io stores selected account information for customer management and, where separately enabled, optional onboarding messages. Messaging is currently disabled. It receives an account identifier, verified contact email, name, first name, last name, the account’s company when that is known, signup method (for example Google or email), signup and trial-expiry dates, first successful lookup time, paid-access status and reminder preferences. A one-time signup event shares that same name, first name, last name, company when known, and signup method. It does not receive search inputs, retrieved company/person records, API keys or authentication credentials. You can turn off onboarding reminders in dashboard Settings or through an email unsubscribe link. Relevant search inputs, profile identifiers and requested email-check inputs are used to fulfil the lookup. Your selected AI app or API client receives the returned data and may retain its own copy. Review that app’s settings and privacy terms. Viewing an available company logo may make a browser request to an approved image host; Datalayer does not fetch arbitrary image URLs on your behalf.

Optional website analytics

The public homepage at datalayer.so offers optional Google Analytics. It stays unloaded until you choose Allow analytics. If allowed, Google receives visit and interaction information such as page views, browser/device details and approximate location derived from your connection. Analytics uses cookies scoped to datalayer.so; advertising signals and ad personalization are disabled. We do not send account IDs, profile research, or arbitrary URL queries or fragments in the page view. Google may process this information outside your country. Your choice is saved in this browser. Use Analytics preferences in the website footer to change it. Declining stops Google Analytics and removes the cookies created by this stream. Browser storage restrictions may cause the website to ask again. This installation does not add Google Analytics to the dashboard or docs. Cloudflare Web Analytics remains configured separately.

Saved results and retention

Saved profile details are available for 90 days from retrieval. Expired saved details are removed by scheduled retention cleanup. The cleanup runs separately from expiry; temporary delays do not make expired details available again. You can view saved details while signed in even after your credit allowance expires. You can export unexpired saved details and delete an individual saved copy. Viewing or exporting a saved result does not run another lookup or consume a credit. Older lookups without a saved copy show that details were not recorded. Deleting or expiring a saved copy does not erase usage receipts, payment records or information already held by your AI app or exports. Account, access, usage, billing, support and infrastructure records have separate retention needs for operating the service, resolving disputes and meeting applicable obligations; the 90-day profile-detail period is not a promise to delete those records.

Your controls

The dashboard lets you revoke API keys, disconnect agents, export account records and submit an account-deletion request. Export excludes secret credentials and transient authentication state. A paginated export can be marked partial if it cannot finish; it is not an export of every indexed record. An account-deletion request is reviewed before action. Submitting it does not immediately delete records or cancel billing. Contact support to discuss account access, correction, deletion or a supplied professional profile. Deleting your saved copy does not remove that profile from later indexed results. The dashboard uses HttpOnly authentication-attempt and encrypted session cookies; HTTPS cookies are host-restricted and Secure. A session cookie can be renewed during sign-in refresh. Its browser lifetime does not determine database retention.