Privacy Policy

This Privacy Policy describes how Deep Layer handles information when you use askdeeplayer.com. Deep Layer is an AI sports intelligence platform for evidence-backed sports research.

When you research, you may submit questions, follow-ups, images or text you upload to a specialized surface, feedback, and — if you create an account — an email address and password. If you publish research, you choose the title, question, answer, citations, and research date that become public.

Account sign-in uses our authentication provider. We store the account identifiers needed to keep you signed in and to attach Intelligence Library and durable Sports Intelligence to that account when those features apply.

We also keep an account identity index of email, display name, and account ID so authorized operators can look up a customer after fail-closed operations authentication. That index is not a public directory and is not an authentication shortcut. Named support actions may be audited.

Signed-in sessions use first-party authentication and session cookies. First-party product analytics may also store a visitor cookie, as described below.

When the complimentary research allowance is being measured, Deep Layer may set a first-party dl_anon cookie containing a signed anonymous identifier and keep a server-side count of successful anonymous investigations associated with that identifier. That identifier is not your name or email. It is used to enforce the complimentary allowance and to show an account-creation handoff. It does not enroll you in a paid plan or collect billing information.

To generate an answer, Deep Layer sends your prompt and relevant conversation context to the AI and research providers used by the product. Do not submit information you would not want processed by those services.

Research you start here is saved in this browser on this device. Sign in to keep Intelligence Library and durable research with your account. Publishing creates a public page that stays available until you unpublish it.

Device-local research lives in your browser. Account-backed Library items and durable Sports Intelligence are stored so you can return to them when signed in. An explicit Publish & share action stores a public snapshot. Unpublished and private research are not advertised as public pages.

First-party product analytics may store a visitor cookie, landing path, referrer host category, standard UTM parameters, and research start / success / failure counts. Telemetry may include workflow IDs, sport or league categories, counts, durations, booleans, latency, approximate cost estimates, and opaque session identifiers. Raw research questions, answers, passwords, and payment data are not captured by that analytics path by default.

We also keep operational logs needed to run and secure the service. We do not claim that we never store IP addresses in infrastructure logs.

Deep Layer does not currently offer Product checkout or collect payment-card details through the Product. Describing a future paid service in our Terms does not activate payment collection.

When checkout is later enabled, a payment provider will process payment-card details. Deep Layer will not store full card numbers, security codes, or equivalent raw payment credentials. We may receive a billing address or location so tax can be determined where required. Location-specific tax rules can differ, and we do not assume that one home-state software-tax treatment applies everywhere.

Before external billing is enabled, we will review this Policy against the actual payment-provider and data flow and update it as needed to describe the billing information that provider processes and the information Deep Layer receives or stores.

We use categories of providers to operate Deep Layer: hosting, authentication, AI inference, and research/source retrieval. Those providers process information on our behalf to deliver the product. A payment provider is not included in this current Product-data-flow description because Product checkout is not active.

We do not sell your personal information. We share information with service providers as needed to operate Deep Layer, or when required by law. If you publish research, that snapshot is public and may be indexed or copied by others.

Device-local research remains until you clear it or the browser removes it. Account-backed research remains while the account and those records exist. Anonymous usage counts remain as needed to operate the complimentary allowance and prevent abuse. Unpublishing hides a public snapshot from the public page and sitemap listing. We do not promise instant or complete deletion from every backup or cached copy.

We use reasonable administrative and technical measures to protect the service. No method of transmission or storage is completely secure.

Deep Layer is not directed to children under 13, and we do not knowingly collect personal information from them. Paid offerings, when available, are for people 18 or older.

You may ask us to access, correct, or delete personal information we hold. Contact us to make a request. We will honor reasonable requests. This Policy does not claim that Deep Layer is currently a covered CCPA “business,” a GDPR controller certification, or any similar certification. If a later threshold makes a specific statute apply, we will update this Policy.

We may update this Policy. The “Last updated” date will change when we do.

Privacy questions and requests: privacy@askdeeplayer.com.