Privacy Policy

Unspyn builds private digital tools that turn emotional static into clearer signal.

This Privacy Policy explains how Unspyn collects, uses, stores, and protects information through our website, beta forms, private beta products, and related operations. It also explains how privacy works inside The Receipt by Unspyn private beta. The short version: The Receipt private beta is designed to be private and pseudonymous by default. Raw private stings and generated Receipt outputs are handled inside protected product-layer systems. Our internal operating dashboard and operations mirror are designed to review sanitized signals and product-quality metrics, not raw private content.

1. Who we are

"Unspyn," "we," "us," and "our" refer to Unspyn and the digital products operated under the Unspyn brand, including The Receipt by Unspyn.

You can contact us about privacy at: support@unspyn.com

2. What this policy covers

This policy applies to: the Unspyn website; Unspyn landing pages and forms; The Receipt by Unspyn private beta; beta access-code flows; in-app feedback forms; operational systems used to run, secure, and improve the beta.

This policy does not apply to websites, platforms, or services that we do not control.

3. The Receipt private beta

The Receipt by Unspyn is a private, real-time beta tool. A beta user submits one emotionally charged "sting" — for example, a comparison, envy, longing, resentment, shame, visibility fear, disappointment, or another moment that hit harder than expected — and receives a structured Receipt output. The Receipt is not a medical, mental health, therapy, crisis, legal, financial, or professional-advice service. Do not use The Receipt for emergencies or crisis situations. If you believe you may be in danger or need urgent support, contact local emergency services or a qualified professional resource.

4. Information we collect

Depending on how you interact with Unspyn, we may collect the following categories of information. Website and form information: if you submit a form, join a waitlist, request access, or contact us, we may collect name or display name, email address, message content, product interest, signup source, and form metadata. Beta access information: we may collect the beta access code used, validation status, usage count, timestamp, and tester assignment status. Access codes help us manage a small private beta — for that reason the beta is private and pseudonymous by default, not fully anonymous. Private Receipt submission information: we may collect submitted sting/input text, optional context, category selections, the generated Receipt output, prompt or engine version used, timestamps, and technical request metadata. Because the beta is designed for private emotional inputs, avoid including unnecessary identifying details you do not want in a private beta record. Feedback information: we may collect accuracy or usefulness rating, selected feedback options, whether you want another Receipt, price or payment-interest response if asked, optional written feedback, and consent choices. Sanitized quality signals: to improve product quality without exposing raw private content, we may create sanitized records that include anonymous submission references, product area, prompt version, input category labels, sting type and desire type labels, quality and confidence scores, brand-fit and specificity scores, flags for generic output, out-of-scope content, safety scope, and therapy/wellness/manifestation language, feedback rating, and aggregate metrics by day, prompt version, or beta cohort. These records are designed not to contain raw sting text, full Receipt outputs, access codes, email addresses, tester names, or user-generated private prose. Technical and usage information: we may collect browser and device information, IP address or approximate location, pages visited, timestamps, error logs, and security signals. We design operational logging to avoid capturing raw private stings or Receipt outputs.

5. How we use information

We use information to: operate the Unspyn website; provide access to The Receipt private beta; validate beta access codes; generate Receipt outputs; collect and interpret beta feedback; evaluate product quality and prompt performance; identify bugs, abuse, misuse, or safety issues; improve product reliability and brand consistency; manage beta operations and tester follow-up; communicate with you if you contact us or join a list; maintain security and prevent unauthorized access; comply with legal, security, or operational obligations. We do not use private beta submissions to create public examples, marketing quotes, testimonials, or case studies unless you have given consent.

6. Privacy architecture for The Receipt beta

The Receipt beta is designed around a privacy firewall. Raw private stings, optional context, and generated Receipt outputs may be stored in protected product-layer systems so the app can generate and return the Receipt, support debugging, and operate the beta. These private records are not intended for general browsing or public display. Unspyn may use an internal operating dashboard to review product health, quality, prompt performance, safety flags, usefulness, and aggregate beta metrics. The Internal OS is designed to see sanitized signals and aggregate metrics — not raw private stings, raw emotional messages, full generated Receipt outputs, tester names, emails, phone numbers, or raw access codes by default. Unspyn may use Airtable or a similar operations system to manage beta operations. Airtable is designed to receive status and operations signals only — such as beta activity status, feedback completion status, high-level non-private tags, and quality metrics. Airtable should not receive raw private stings, raw generated Receipt outputs, private emotional messages, raw feedback quotes, or tester-linked emotional content.

7. Consent for review and anonymous use

By default, private beta submissions are used to provide the beta product and generate sanitized quality signals. You may be offered an option to allow anonymous review for product improvement. If you choose that option, we may review the submission or output for product-quality purposes after stripping or separating identity wherever practical. Suggested consent language may appear as: "I allow this anonymous submission to be reviewed to improve The Receipt." Even with consent, we do not intend to show your identity next to a private Receipt submission in the Internal OS or Airtable operations mirror. If you separately consent to anonymous quote or testimonial use, we may use selected feedback or language in a non-identifying way.

8. How we share information

We do not sell your private beta submissions. We do not post your private Receipt submissions publicly. We do not share raw private stings or generated Receipt outputs with advertisers. We may share information with service providers that help us operate Unspyn and The Receipt, such as hosting and deployment providers, database and storage providers, AI infrastructure or model providers used to generate outputs, email and form providers, analytics, security, and debugging providers, and operations tools used to manage the beta. These service providers may process information only as needed to provide services to us, operate the app, maintain security, or comply with applicable obligations. We may also disclose information if required to comply with law, enforce our terms, protect the security of our services, prevent misuse, or protect the rights, safety, or property of Unspyn, users, or others.

9. Data retention

The Receipt private beta is designed around data minimization and delete-by-default principles. Raw sting or message input is generally retained no longer than 14 days unless needed for security, debugging, consented review, legal obligations, or future account functionality you choose. Generated Receipt output is similarly retained no longer than 14 days. Raw written feedback is generally retained no longer than 30 days unless you consent to review or anonymous use. Sanitized quality signals, scores, flags, and aggregate metrics may be kept longer — generally 12 to 24 months — because they are designed not to contain raw private content. Access-code usage records may be kept during the beta and for a reasonable period afterward to manage beta operations. Tester identity or assignment records may be kept only as needed for beta administration, follow-up, access management, or consent tracking. We may retain information longer if needed for security, legal compliance, dispute resolution, abuse prevention, or business records.

10. Your choices

You may choose not to submit a sting or use The Receipt beta. You may use initials, aliases, or no names at all when submitting a sting. You may avoid including third-party names or identifying details. You may decline optional review or quote consent. You may contact us to request access, correction, or deletion of information associated with you, subject to our ability to verify the request and any legal, security, or operational retention needs. For privacy requests, contact: support@unspyn.com

11. Security

We use reasonable administrative, technical, and operational safeguards designed to protect information from unauthorized access, misuse, loss, or disclosure. These safeguards may include server-side access controls, protected database access, row-level security where applicable, service-role keys kept server-side, limited operational access, sanitized internal reporting, and avoiding raw private content in operations mirrors by default. No internet-based service can be guaranteed to be perfectly secure. Please avoid submitting information you are not comfortable placing into a private beta product.

12. Children

Unspyn and The Receipt are intended for adults. The Receipt private beta is not directed to children under 13, and we do not knowingly collect personal information from children under 13. If you believe a child has provided personal information to us, contact support@unspyn.com and we will review the request.

13. Email communications

If you join an email list, request beta access, or contact us, we may use your email address to respond, provide beta information, send product updates, or manage your participation. You can unsubscribe from marketing emails using the unsubscribe link in the email or by contacting us. Service-related or beta-operational messages may still be sent when necessary to operate the beta or respond to your request.

14. Third-party links

Our website or beta app may link to third-party websites, platforms, or tools. We are not responsible for the privacy practices of third parties we do not control. Review the privacy policies of any third-party services you choose to use.

15. Changes to this policy

We may update this Privacy Policy as Unspyn, The Receipt, and related products evolve. When we update it, we will revise the "Last updated" date above. If changes are material, we may provide additional notice where appropriate.

16. Contact

For privacy questions or requests, contact: support@unspyn.com