Chi'llywood Public Policy
Account Deletion and Data Deletion Policy
This policy explains how users can request account deletion, what may be deleted or de-identified, what may be retained, and how deletion interacts with subscriptions, backups, legal holds, and Google Play requirements.
Plain-English Summary
Users can request deletion of a Chi'llwood account through the in-app Settings legal/support surface or the public web account deletion page when available. Chi'llwood may need to verify the request, identify the correct account, review subscriptions, check safety/legal holds, and run an approved backend deletion or de-identification process. Deletion is not a magic instant wipe of every backup, log, legal, moderation, billing, or evidence record.
Public content should stop being displayed according to product and legal rules when deletion is processed, but Chi'llwood may retain information where necessary for backups, fraud prevention, security, legal compliance, tax, accounting, audit records, legal holds, evidence exports, moderation records, dispute handling, law-enforcement requests, already-created thumbnails, previews, service artifacts, or content already shared, embedded, clipped, cached, or distributed through service features where allowed.
How to Request Deletion In App
Signed-in users should open Settings, find the Legal & Support launcher, and choose the account deletion action or Account Deletion policy. If the app has a self-serve deletion button in a later release, use that flow and follow its verification prompts. If self-serve deletion is not available, contact [email protected] from the email connected to the account or through signed-in support feedback, and state that you are requesting account deletion.
Include the account email, user id if visible, profile/channel identifiers, and any context needed to identify the account. Do not send passwords or reset tokens. Chi'llwood may reply to verify account ownership, ask follow-up questions, explain subscription cancellation, confirm whether legal holds exist, or provide timing expectations. Requests made from an unrelated email may require extra verification or may be denied.
How to Request Deletion on the Web
Chi'llwood should maintain a public account deletion page at a reachable URL such as https://chillywoodstream.com/account-deletion. That page should explain the app name, developer identity, deletion request path, what data may be deleted, what data may be retained, and how users can contact support. This is important for app-store and Google Play compliance and for users who cannot access the app.
If the public web deletion URL is unavailable, the bundled in-app policy and support email remain the fallback notice, but the owner should fix the public URL before launch. Public deletion pages must not require login just to read instructions. Actual deletion may still require identity verification before data is changed. Entering a public URL in a store console does not by itself delete data.
What May Be Deleted or De-Identified
Deletion may remove or de-identify account identity information, profile and channel display information, public bio fields, avatars, creator uploads, creator video metadata, thumbnails, public channel listing rows, notification preferences, audience relationships, draft or public content, and certain support or social records where legally and technically allowed. De-identification may replace account identifiers with deleted-user markers when full removal would break another user's context or an audit trail.
The exact result depends on product architecture, relationships between records, storage objects, public sharing, legal obligations, and support runbooks. If a user has public creator uploads, live replays, chat messages, watch-party records, or reports involving other users, some records may be hidden, detached, de-identified, retained in limited form, or preserved under legal/safety rules rather than fully erased immediately.
What May Be Retained
Chi'llwood may retain information needed for fraud prevention, security, abuse prevention, account-integrity review, blocked-account enforcement, legal compliance, lawful requests, copyright, DMCA, takedown history, repeat-violation handling, moderation, safety reports, admin actions, legal holds, evidence exports, support history, billing, subscriptions, refunds, chargebacks, accounting, tax, dispute resolution, logs, diagnostics, backups, and service integrity.
Backups may retain data for a limited period until normal backup rotation. Logs and diagnostic data may contain identifiers or activity details needed for security and reliability. Legal holds can pause deletion of relevant data. Account deletion does not require Chi'llwood to delete another user's messages, private evidence records, legal process records, audit rows, or records that the law or a legitimate safety need requires Chi'llwood to keep.
Subscriptions and App-Store Cancellation
Deleting a Chi'llwood account does not automatically cancel a subscription managed by Google Play, Apple, RevenueCat, or another billing provider. Users may need to cancel through the store account used for purchase. If a subscription remains active at the store, billing may continue even if the Chi'llwood account is deleted or de-identified. Users should follow store cancellation instructions and keep proof of cancellation.
Support can help explain restore and entitlement status but may not be able to issue store refunds directly. Refunds may be controlled by the app store or payment provider. Deletion requests do not create a guaranteed refund or guarantee immediate termination of paid access. Billing records may be retained for accounting, tax, fraud, chargeback, and legal reasons.
Timing, Verification, and Third-Party Processors
Deletion timing depends on identity verification, support queue capacity, account complexity, legal holds, safety reports, copyright records, billing status, backups, technical runbooks, and third-party processors. Chi'llwood may provide an estimated timing window but cannot guarantee every processor will complete every related action at exactly the same time. Users should keep copies of important content before requesting deletion.
Third-party providers such as Supabase, Firebase, RevenueCat, app stores, LiveKit, Expo/EAS, email providers, and hosting providers may hold records as processors or independent providers according to their roles and policies. Chi'llwood may instruct processors to delete or de-identify data where appropriate, but some provider-managed billing, fraud, security, or legal records may follow provider retention rules.
Legal Holds, Evidence, and Safety Exceptions
Chi'llwood may place a legal hold when data is relevant to law enforcement, legal request, court order, subpoena, preservation request, safety incident, copyright dispute, moderation case, fraud investigation, billing dispute, or other legal obligation. A legal hold can delay deletion of relevant records. Users may be told where appropriate, but notice may be limited by law, safety, or investigation needs.
The Legal Evidence tool is read-only for evidence packages and should not delete evidence. Deletion requests should not be used to destroy evidence, evade moderation, hide infringement, avoid chargebacks, or frustrate lawful process. Chi'llwood may preserve audit rows and evidence export records even after account deletion.
Google Play Compliance Checklist
Owner checklist before public launch: maintain a public web deletion page; include the app name; explain how to request deletion; explain what data is deleted; explain what data may be retained; ensure in-app Settings points to deletion help; confirm support email works; enter the public deletion URL in Google Play Console; keep the page reachable without login; and update Google Play Data Safety disclosures to match actual data collection, sharing, deletion, and retention practices.
This checklist is a compliance aid, not proof of store approval. Google Play may require changes to wording, location, processing, response timing, or disclosure. Chi'llwood should keep screenshots or timestamped proof of the page and store configuration outside the repo if needed for launch review.
What Users and Creators Are Responsible For
Users and creators are responsible for what they do with their accounts and what they upload, stream, publish, message, save, display, report, purchase, or share. That responsibility includes account security, truthful profile information, lawful conduct, respect for other people, accurate support requests, and compliance with the Terms, Community Guidelines, Creator Terms, Live and Chat Rules, Copyright Policy, Premium Terms, and feature-specific prompts.
Creators are also responsible for owning or having permission for all video footage, audio, music, beats, samples, images, logos, trademarks, names, likenesses, voices, performances, locations, third-party clips, collaborative material, people appearing in content, livestream guests, speakers, chat or comment attachments, replays, and saved live material. No upload, publish, live, replay, or playback success means Chi'llwood has verified those rights.
What Chi'llwood May Do
Chi'llwood may operate, host, store, cache, back up, stream, reproduce, display, publicly perform, distribute, publish, transmit, transcode, compress, resize, crop, format-shift, make thumbnails, make previews, make snippets, create captions or metadata where applicable, review, moderate, restrict, remove, preserve, investigate, and otherwise process content and account activity as reasonably needed to provide, improve, protect, promote, monetize, secure, troubleshoot, and legally operate the service.
Chi'llwood may remove, restrict, block, disable, demonetize, age-restrict, geoblock, preserve, or review content and accounts for copyright or IP complaints, DMCA notices, legal requests, court orders, law enforcement, safety, community rules, fraud, security, child safety, harassment, threats, platform integrity, account violations, repeat infringement, spam, scams, impersonation, privacy complaints, publicity complaints, or operational reliability.
What Chi'llwood Is Not Responsible For
Chi'llwood is not responsible for user-generated content, user conduct, creator claims, third-party links, off-platform arrangements, unsupported devices, network failures, app-store billing decisions, user mistakes, unlawful uploads, unauthorized music, unauthorized likenesses, inaccurate support submissions, or promises made by users, creators, advertisers, sponsors, guests, viewers, moderators, or third parties except where applicable law says otherwise.
Chi'llwood does not promise uninterrupted service, permanent feature availability, a guaranteed audience, guaranteed views, guaranteed revenue, guaranteed monetization, guaranteed support timing, legal outcome, content restoration, account restoration, refund outside provider rules, or that every harmful item will be found before users see it. Nothing in these policies limits rights that cannot legally be limited.
How to Contact Chi'llwood
For privacy, copyright, support, account, Premium, creator, moderation, law-enforcement, or legal questions, contact Chi'llwood Support at [email protected] unless a policy gives a more specific path. Include the account email or user id if you are asking about your own account, enough information to locate the content or room at issue, and a clear description of what happened. Do not send passwords, one-time codes, payment card numbers, private keys, service-role credentials, or other secrets.
Support can receive requests, route them to the correct owner/admin/legal workflow, ask for verification, and provide status where appropriate. Support is not an emergency service, cannot promise immediate resolution, cannot provide legal advice, cannot guarantee restoration or payment, and cannot override app-store billing rules, court orders, safety restrictions, copyright removals, or lawful preservation requirements.
How This Policy Connects to the App
This policy connects to Chi'llwood accounts, Profile, Channel, creator uploads, Studio, Player, Watch-Party Live, Live Watch-Party, Chi'lly Chat, audio/video calls, notifications, Premium, support, reporting, moderation, owner/admin tools, Live Ops, legal holds, and evidence workflows. Feature names may change, but the same rules apply to equivalent surfaces that let users create, upload, stream, share, view, message, report, pay, subscribe, moderate, preserve, or request help.
If a screen shows a shorter in-app summary, the summary is only a launcher. The full policy text controls subject to applicable law and any later written agreement signed by Chi'llwood. If a public web link is unavailable, Chi'llwood may use the bundled in-app policy page as the current policy source until the public page is updated.
Owner and Admin Support Notes
Owner and approved admin tools may show operational notes so the team can apply this policy consistently. Those notes are for workflow and safety operations; they do not give public users hidden rights and they do not remove the need to follow applicable law. Sensitive admin/legal actions require the scoped permissions, reasons, audit records, and legal-hold rules implemented elsewhere in Chi'llwood.
These policies are operational notice documents, not legal advice to users and not a promise that any single workflow protects against every claim or risk. The goal is clear user notice, consistent operations, evidence preservation, and reasonable risk reduction while Chi'llwood follows the law and keeps internal review records current.