Privacy Notice
LAST UPDATED OCTOBER 18, 2026
1. Scope and controller
This Privacy Notice explains how Intrigued.me, LLC ("Intrigued.me," "we," "us," or "our"), based in Colorado, United States, handles personal information through awkwardpixels.studio and related AwkwardPixels Studio features (the "Service"). Intrigued.me is the controller of information handled for its own purposes. The Service is primarily intended for a United States audience; mandatory rights that apply where you live are not waived by this notice.
2. Audience age
The Service is intended for a general audience age 13 and older. We do not knowingly collect personal information from children under 13. A person under 13 must not sign in, submit a message, or make a payment. If you believe a child provided personal information, contact us so we can investigate and delete it as appropriate.
3. Information we collect
- Public viewing data: request time, approximate network information, coarse device and orientation category, pages or assets requested, episode identifier, completed-play count, share, YouTube-link, and ElevenLabs affiliate-link actions, referrer hostname, sanitized campaign labels, error and security events, and similar server telemetry. Stage metrics do not include a user identifier, message text, full referrer URL, or arbitrary browser-provided properties.
- Optional Google Analytics data: after you allow analytics, Google Analytics may receive page and interaction information, referrer information, browser and device characteristics, and network information needed to deliver the request. We do not send Viewer Content or our account identifier to Google Analytics, and advertising storage, ad user data, ad personalization, and Google signals remain disabled in our tag configuration.
- Browser storage: local or session values that remember whether a performance played or was counted, avoid duplicate page and completed-play reports, rotate prerecorded scenes, remember your analytics choice, preserve a pending payment order and random guest payment key, cache site assets, and support reliability. The guest payment key is kept in the initiating tab's session storage and used to authorize only that guest's checkout. Losing it may prevent automatic completion checks; contact us with transaction details rather than sending us the key.
- Account data, if sign-in is enabled: an authentication provider may provide a stable account identifier and account details such as email or display name. Our interaction system keys daily limits to a one-way keyed hash of the stable identifier rather than storing that raw identifier in interaction records.
- External media: opening a YouTube link or choosing to play an external embed sends requests to that provider. We do not currently request access to your YouTube account or verify your subscriptions.
- Viewer Content: the one-sentence statement or question you submit, your 13+ attestation, the safety result, the generated response, delivery status, and related timestamps.
- Payment data, if tips are enabled: payment order, capture, request and webhook-event identifiers, amount, currency or environment, date, status, and either a pseudonymous account key or a domain-separated keyed hash for a guest payment key. We also store recent checkout-attempt times and hashed owners to enforce shared and per-owner limits. These hashes are pseudonymous, not a promise of anonymity. The website does not collect full card details or payment-provider passwords. PayPal processes payment information under its Privacy Statement; refund and dispute communications may provide additional transaction information.
- Communications: information you send when requesting support, privacy help, or permission to use an asset.
4. How we use information
We use information to deliver and personalize the requested performance; authenticate users; enforce daily limits; run safety checks; detect prompt injection, fraud, and abuse; process and reconcile tips; create share links; measure page visits, performance completion, sharing, and channel interest; decide whether audience demand warrants another generated episode; maintain and secure the Service; measure reliability and provider costs; comply with law; and respond to requests.
5. AI and safety processing
When you submit Viewer Content, it may be sent to Microsoft Azure content-safety and Azure AI services and, depending on the active feature, OpenAI API services to check safety and generate a character response. Generated dialogue is sent to ElevenLabs to synthesize speech and may include details from your message. We may detect concerning language to present safety resources or reject unsafe content. Winston and Asher are AI characters, not human advisers; this is automated safety routing, not diagnosis, therapy, monitoring, emergency response, or a decision with legal or similarly significant effects.
We do not intentionally use Viewer Content to train public or general-purpose AI models. Provider retention and model-improvement practices depend on the provider, contract, plan, and account settings; we do not promise that all providers exclude training by default or offer zero retention. See ElevenLabs' Privacy Policy for its practices. Provider abuse monitoring and legally required processing may also apply. Do not submit sensitive or confidential information, and review generated results before sharing them.
6. When we disclose information
We may disclose the minimum necessary information to service providers operating on our behalf, including Microsoft Azure, Azure AI services, OpenAI, ElevenLabs, authentication providers such as Google, payment providers such as PayPal, operational monitoring vendors, and professional advisers. We may also disclose information when required by law, to protect safety or rights, during a business transaction, or with your direction.
If you choose to open an embedded YouTube surprise or another external link, the third party may receive network, device, and interaction information under its own privacy policy.
7. No sale or behavioral advertising
We do not sell personal information. We do not share personal information for cross-context behavioral advertising and do not currently use third-party behavioral advertising trackers. Affiliate links may let the linked provider attribute a purchase after you choose to leave the Service; a compensation disclosure will appear near such links.
8. Cookies and local storage
The public stage uses browser storage and a service-worker cache for playback state, metric deduplication, performance rotation, offline resilience, analytics preferences, and pending payment flow. Stage events are sent to our own API and recorded in Microsoft Azure Application Insights separately from optional Google Analytics; declining Google Analytics does not disable operational or security requests. If you allow optional analytics, the Service loads the Google Analytics tag and it may set analytics cookies such as _ga. The tag remains blocked when you decline. We do not enable advertising storage or advertising personalization through the tag. AdSense ownership verification metadata is not an ad-serving integration or consent to advertising.
9. Google sign-in
If you choose Google sign-in, Google provides the basic account information presented during consent, such as an account identifier, name, or email address. We use it to authenticate you, enforce daily message limits, prevent abuse, and associate account-backed completed shares or tips with your access for that day. Guest tips do not require Google and are not reassigned if you sign in later. We do not receive your Google password.
You can sign out through the Service and review or revoke Google access through Google security settings. Google's handling of information is described in the Google Privacy Policy.
10. Retention
Raw message text in the interaction table becomes eligible for scheduled removal after 24 hours; maintenance timing or failures may delay the cleanup. This does not automatically erase generated dialogue, audio, provider copies, backups, or content already shared. Our deployment configuration specifies 30-day Application Insights retention. Episode completion totals, pseudonymous usage counters, safety and delivery status, generated-response references, payment and refund records, security logs, and provider accounting may be kept longer when reasonably necessary to operate the Service, prevent abuse, resolve payments, maintain records, or comply with law. Share links expire after 24 hours; expiry of a link is not deletion of the underlying content or copies posted elsewhere.
Checkout admission uses one bounded record of recent hashed owners and attempt times. Older entries are removed when that admission state is updated, not by a promise that every entry is physically erased as soon as its rate-limit window expires. Transaction records are retained separately for payment reconciliation, refunds, and legal recordkeeping.
We delete or de-identify information when it is no longer reasonably needed, subject to backups, legal holds, fraud prevention, and technical constraints.
11. Security
We use measures intended to protect information, including encrypted transport, access controls, private storage for non-public media, pseudonymous account keys, content limits, provider circuit breakers, and security monitoring. No system is perfectly secure, and we cannot guarantee absolute security.
12. Your choices and rights
You may watch without signing in, decline interactive features, avoid making a tip, choose not to open YouTube, clear browser storage, and close external embeds. You can also review or change your analytics choice at any time; withdrawing analytics consent updates the tag state and removes the Google Analytics cookies available to the Service. Clearing browser storage does not delete server records. Depending on applicable law, you may have rights to access, correct, delete, restrict, object to, or obtain a copy of personal information, withdraw consent, or appeal a denied privacy request.
To make a request, email legal@intrigued.me and describe the request. We may need to verify your authority using proportionate information; never email passwords, full card numbers, or guest payment keys. We respond within applicable legal deadlines. To appeal a denial where applicable, reply to our decision and state that you are appealing, or email the same address with "Privacy appeal" in the subject. You may also complain to your local privacy authority, including the Colorado Attorney General. We will not discriminate against you for exercising applicable privacy rights.
13. International processing
Intrigued.me and its providers may process information in the United States and other locations where they operate. Those locations may have different privacy laws. Where required, we use contractual or other recognized safeguards for transfers.
For visitors in the EEA, United Kingdom, or Switzerland, processing may rely on performance of a requested service, legitimate interests in security and reliable operation, consent where requested, and compliance with legal obligations.
14. Changes and contact
We may update this Notice as the Service changes. We will post the new effective date and provide additional notice for material changes when appropriate.
Privacy questions and requests may be sent to legal@intrigued.me.