1. Who is responsible for your information
Crank personally operates DewCaps, a game he originally built for his daughter. He is the operator responsible for the account, game, and support information described here. Contact admin@dewcaps.com for privacy questions or requests, including without a game login.
This notice covers the beta and public DewCaps service. The private ChatGPT-linked prototype and development environments are separate testing environments. Public DewCaps accounts do not require a ChatGPT account.
Signup asks only for a username, password, and email address. Choose a fictional username that does not reveal your real name, age, birth date, school, address, phone number, email address, or other personal information. Please do not volunteer these details in the game or send them to support. Enter your email only in account email fields and your password only in password fields; for a support request, share only the minimum account details needed for help. Email addresses, account identifiers, and some technical records are personal information; this notice describes the data we still need to run the service.
2. What we collect and why
| Information | Source and purpose |
|---|---|
| Account and contact information | Login name, account/player identifiers, required email address, verification status, role/status, and account creation time. Used for accounts, recovery, support, and important service communications. |
| Agreements | The terms version accepted and the acceptance time. No age or birth date is requested. Previously collected age bands have been cleared from the active game database; restricted older recovery copies are handled under our backup and deletion procedures. |
| Authentication and security | Password and recovery-key hashes, session records, verification/reset records, access/admin events, and rate-limit identifiers. Used for authentication, security, abuse prevention, and incident review. Passwords are processed when used, but stored as hashes rather than readable passwords. |
| Game activity | Gardener/mushroom names, creatures, inventories, currencies, ancestry, market/breeding activity, rewards, Pro expiry, preferences, notifications, and timestamps. Used to save and deliver the game and resolve errors. |
| Support and feedback | Fixed-choice game reports, any optional description you provide, and the relevant account/screen/release, plus private support correspondence and necessary case records. Do not volunteer additional personal information. Account locators and minimal verification may be necessary to resolve a private request. |
| Payments, when enabled | Package, price/currency, order/provider references, payment/refund/dispute status, and credited game benefits. Used for fulfillment, reconciliation, disputes, and necessary financial records. Payment-card details are entered with Stripe, not stored in our game database. |
| Connection/device information | Infrastructure providers receive IP addresses and request/browser details needed to serve and protect the site. We use edge rate limiting and hashed account/IP rate buckets. Hashing does not necessarily make information anonymous. |
| Usage analytics | HeyCatch receives page visits, interaction events, campaign/referral information, browser/device and connection information, a stable player identifier, account email and fictional name when known, signup date, Pro plan, and successful signup, purchase and guide-completion events. Used to understand visits, signup and purchase outcomes and improve the game. Automatic capture masks page text and element attributes, and removes verification/reset fragments and private query parameters. We do not send passwords, recovery keys, payment-card details or input contents to analytics. |
| Meta advertising measurement (paused) | No new events are sent. Before the pause, visitors who opted in could send page visits and successful signups, page/campaign URLs, cookie or advertising identifiers, and connection/browser details to Meta for ad measurement, optimization and targeting. We did not attach DewCaps account IDs, usernames, email, passwords, payment information or game inventory. |
| ChatGPT advertising measurement (paused) | No new events are sent. Before the pause, visitors who opted in could send page visits, successful registrations, live Glowstone checkout starts and confirmed purchases, public page/package identifiers, USD subtotals, transaction event identifiers, attribution/browser references, and connection/device information to OpenAI. We did not manually attach email, name, phone, account ID, payment-card details or game inventory. |
3. What other players can see
Other players may see public gardener names, mushroom names, listings, and fictional breeding/family histories. Your account email, credentials, support correspondence, and private purchase records are not displayed in ordinary player views.
Custom mushroom name entry is disabled. Feedback descriptions are optional and should contain game details only, without personal information or passwords. Public gardener names can be changed; use a fictional name and do not share personal information. Contact support to remove an identifying existing name or record. We address copies we control, but cannot promise removal from someone else’s device after they have viewed or copied it. Fictional mushroom ancestry is game data, not biological information about you.
4. Service providers and disclosures
Optional Glowstone purchases fund the game. We do not sell account information for money. We use HeyCatch for site and product analytics. Meta and OpenAI advertising measurement is currently paused, including for browsers that previously opted in. Neither advertising Pixel loads or sends new events. These analytics services do not subscribe you to marketing emails.
Providers process information needed for their services. Their systems may operate in multiple countries; we do not promise U.S.-only storage. We limit access to what is reasonably needed and apply any required safeguards for the service and locations involved.
| Recipient | Why they receive information |
|---|---|
| Cloudflare | Website/Worker hosting, database storage and recovery, request protection, transactional email delivery, and administrator access verification. |
| HeyCatch | Processes the usage and outcome information described above on our behalf to show site analytics, signup/purchase funnels and campaign performance. See HeyCatch’s privacy notice at https://heycatch.ai/privacy. Privacy requests for DewCaps analytics should be sent to admin@dewcaps.com. |
| Meta (Facebook and Instagram), previous opt-in activity | No new Pixel activity is sent while measurement is paused. Previously sent activity may be linked to Meta accounts and handled under Meta’s policies. Privacy information: https://www.facebook.com/privacy/policy/. Contact admin@dewcaps.com for help with data already sent. |
| GitHub | Private development issues, release operations, and encrypted independent database backups. Feedback copies omit account identifiers and redact common sensitive patterns, but free text still needs care. |
| GoDaddy / Microsoft 365 | The admin@dewcaps.com mailbox and support correspondence. Account messages are sent through Cloudflare; replies reach this mailbox. |
| Stripe, when purchases are enabled | Checkout, payments, fraud controls, receipts, refunds, and disputes. Stripe receives payment details and relevant account/order references and also provides its own privacy information. |
| Authorized helpers and advisers | Limited access necessary for support, security, accounting, or professional advice, with appropriate restrictions. |
| Authorities or a successor operator | Where necessary and lawful for legal obligations, protection of rights or safety, or a genuine transfer of the service with appropriate safeguards and notices. |
| ChatGPT / Sites, private prototype only | The private prototype uses platform identity and hosting arrangements separately from public DewCaps accounts. |
| OpenAI, previous opt-in activity | No new advertising measurement events are sent while measurement is paused. Previously sent activity is handled under OpenAI’s privacy information: https://openai.com/policies/privacy-policy/. Contact admin@dewcaps.com for help with applicable requests concerning data already sent. |
5. Service messages and optional newsletters
We use your email for verification, password recovery, security, purchases, support, and important service or policy notices. These messages are connected to your account and are separate from optional marketing.
We may offer promotional emails or a newsletter in the future. If offered, enrollment will be a separate, voluntary opt-in, never a condition of playing or accepting the terms. Signing up for DewCaps does not subscribe you. Marketing messages will identify the sender, provide an unsubscribe route, and stop when you opt out. No newsletter is currently operating.
7. How long we keep information
We keep information for the purposes below and remove or minimize it when it is no longer needed. A specific incident, dispute, or legal obligation may require limited records to remain longer with restricted access and a documented reason. A financial record does not justify retaining an entire playable account indefinitely.
Deletion normally removes account access, credentials, and private game data. Shared fictional mushroom histories may remain where identifying references have been removed and other players’ progress depends on them. Older backups are restricted to recovery; completed deletions and relevant restrictions must be reapplied before a restored system is reopened. Snapshot expiry is measured from each backup, separately from active-system deletion.
| Record | Retention or review period |
|---|---|
| Active account and saved progress | While needed to provide the account. We review accounts after 24 months of inactivity and give at least 30 days’ email notice before any inactivity deletion. Unused purchased benefits receive separate review. This process is manually reviewed; inactivity does not currently trigger an automatic wipe. |
| Support and identifiable feedback | Up to 12 months after resolution; remove identifiers sooner when no longer needed. Nonidentifying bug descriptions may remain. |
| Routine security and administrator logs | Normally up to 90 days, with limited documented extensions for specific incidents or legal obligations. |
| Minimal privacy-request records | 24 months after resolution, unless a different period is legally required. Unneeded verification material and working exports are removed sooner. |
| Session/rate-limit and email records | Sessions expire after seven days or one day without activity. Expired session/rate records are removed within seven days; expired reset/verification records within one day; account-email delivery records within 30 days. |
| Agreement receipts | Version and acceptance time while needed to administer the account or establish a specific agreement or claim. Previous age bands are cleared from active records. No new age information is requested or retained. |
| Financial/payment records | Only records needed for applicable tax, accounting, fraud, refund, and dispute obligations, for the periods those purposes require. Access is restricted and reviewed separately from game progress. |
| Independent encrypted backups | Normally expire 30 days after creation. Native database recovery follows the provider’s recovery window. Necessary recovery/suppression records prevent a completed deletion being undone by restoration. |
| HeyCatch analytics | HeyCatch retains end-user analytics while our service subscription is active and for up to two months after it ends, then deletes or irreversibly anonymizes it unless we reactivate or request earlier deletion. We include this provider when handling applicable account/data deletion requests. |
| Meta advertising activity and local choice | Previous browser choices may remain in local storage until cleared and do not enable tracking during the pause. Data already sent to Meta is handled under Meta’s privacy policy and controls; pausing tracking does not delete it. Contact admin@dewcaps.com for assistance with applicable data requests. |
| ChatGPT advertising activity and local choice | Previous browser choices and transaction deduplication records may remain in local storage until cleared and are unused during the pause. Cookie lifetimes are described above and are separate from provider retention. Already-transmitted data is handled under OpenAI’s privacy information; pausing tracking does not delete it. |
8. Access, correction, deletion, and appeals
Email admin@dewcaps.com or use Support → Privacy requests to prepare an email from fixed choices. You may request access, a copy, correction, account deletion, removal of identifying content, a parent/guardian review, or an appeal. The page has no personal-information fields and does not submit a case or delete an account automatically; you must send the email.
Share only the username or account email needed to locate the account and a concise description of the request. Do not volunteer other personal information. We may verify using existing account/contact information or a proportionate check of representative authority. Never email passwords, recovery keys, sign-in codes, full card details, identity documents, or birth dates.
We aim to acknowledge requests within five business days and complete privacy requests within 30 calendar days of receipt. Applicable legal deadlines take priority. We will explain any permitted extension, refusal, or narrowly retained records. Ordinary requests are free, and exercising applicable privacy rights will not disadvantage you.
Depending on the law that applies, you may have additional rights to portability, restriction, objection, withdrawal of consent, or complaint to a regulator. To appeal, reply with “Privacy appeal,” the case reference, and your concern. We will review it and explain the available complaint route. A garden export alone is not a complete personal-data response.
9. Children and families
DewCaps is intended for a general audience ages 13 and older, not for children under 13. You must be at least 13 to create or use an account. We do not ask for your age or date of birth, use an age-verification service, or offer under-13 accounts or parental-consent enrollment.
Report an under-13 account privately to admin@dewcaps.com; “Parent privacy request” is a helpful subject but is not required. Include only the username or account email needed to locate the account and say that it concerns a player under 13. Do not send an exact age, birth date, real name, school, address, identity document, password, recovery key, or card details. We may make a limited check to identify the right account and prevent malicious deletion; we verify authority before sharing any private records. Credible reports receive prompt protective action while that review takes place.
If we learn that an account belongs to a child under 13, including through a parent’s report or another credible source, we will promptly disable access, stop further collection, use, and disclosure for gameplay, and promptly delete the child’s account and associated personal information from systems we control. We do not wait for the ordinary privacy-request response period to take protective action, and we do not offer continued under-13 play with parental permission.
Deletion includes review of support messages, development-tracker copies, service-provider records, and recovery copies. We remove or de-identify information where we control it, request provider action where needed, and prevent deleted accounts or information from returning during restoration. Recovery copies may require expiry or provider action; they are restricted from ordinary use. Any legally required retention must be narrowly justified and restricted, and we explain any remaining steps or lawful limits. A deletion request does not waive a purchase claim.
Not asking for age does not remove protections that apply when we learn a user is under 13. We act on credible information received through any channel, not only messages with a particular subject line. Teen players retain applicable privacy protections.
10. Security and changes
We use restricted access, hashed credentials, secure transport, protected administrator actions, and encrypted independent backups. No service can guarantee absolute security. Report suspected unauthorized access to support without posting other players’ information or a working exploit in ordinary feedback.
We will publish a new version and effective date when this notice changes. Material changes will be explained through the game or account contact, and additional consent will be requested where required.