Privacy Notice 11786229 Canada Inc. operates RippleEnd from Toronto, Canada. The operator is the initial privacy contact. Email support@rippleend.com for access, correction, deletion, a privacy concern or assistance with the account tools. We may verify your authority proportionately, but will not ask you to send passwords, authentication codes, recovery secrets or card security codes to support. Information and purposes We process your account email, profile, confirmation and authentication records to provide sign-in, maintain account continuity, recover access and prevent abuse. Email/password and email codes use the same account when verified for that account. Staff additionally require password and authenticator evidence and current permissions. We record the adult-eligibility declaration and responses to particular policy versions to apply the service's audience rules and document real choices. Email confirmation and an age declaration do not independently prove identity or age. Optional marketing consent is not bundled with policy acknowledgement, and this release does not offer marketing subscriptions, SMS sign-in, social sign-in or file uploads. Request titles, descriptions, categories and active deadlines support public publication and sharing. Public content can appear in external previews. Optional name, contact, address and up to two new custom private fields support the sharing you choose. Existing unchanged legacy values may remain. Private details are permission-controlled by field and recipient; they are not included in public request previews. Account owners can view their saved records. Authorized operational access remains subject to its role and case-specific controls. Access requests, approvals, revocations, request lifecycle records and restrictions enforce who may view information and when access ends. Support correspondence, safety reports, moderation decisions, reconsideration or appeal requests and necessary internal notes support assistance, investigation and accountability. They are not public request content. We review information concerning other people before deciding what can be disclosed in an access request or export. Necessary session and verification cookies support authentication, safe return paths, code-entry flows and abuse prevention. Verification state is separate from proof of identity. Operational and security records help diagnose faults and investigate misuse. Do not put credentials or unnecessary private information into public text, support cases or request fields. Providers and international processing Our current providers include Cloudflare for application delivery and Turnstile security checks; Supabase for database and authentication; Resend for transactional email; and Google Workspace for human correspondence. The database projects are configured in Canada Central. Transactional sending domains use Resend's US East region. Providers can process information in other countries through their infrastructure and subprocessors. Canadian database location does not mean all information stays in Canada. Contact support@rippleend.com for information about the providers and safeguards relevant to your information. Public copies and ending access Expiry, completion or withdrawal ends public display of original request details and further private access under the request's rules. Your saved history can remain until deleted. Deleting request content removes its application content and access records; a minimal reserved public reference remains unavailable to prevent reuse. Account deletion is separate and can require review of linked support, safety or other retained records. Ending access prevents further access through RippleEnd. It cannot erase information someone has already copied, downloaded, photographed, screenshotted or shared elsewhere. Retention and deletion Our retention targets are: - Private built-in and custom fields: 30 days after the earlier of request closure or expiry. - Ended owner-history content and associated access records: 90 days after the earlier of closure or expiry. - Resolved routine support cases, replies and notes: 90 days after resolution. Reopening stops that clock; mailbox copies require separate review. - Necessary reports, decisions and review requests: while active, then review and disposal 12 calendar months after final resolution. Active restrictions and unresolved appeals prevent premature disposal. - Routine operational logs: up to 30 days after the event; security logs: up to 90 days. Provider expiry settings and necessary incident records require separate review. - Minimal deletion completion receipts: 90 days after confirmed completion, with any necessary scoped exception recorded. - Restricted deletion replay identifiers: until every affected restorable backup or other recovery copy has expired, so a restore does not revive deleted data. These periods guide manual review and deletion. Records are not automatically erased when a period ends. Provider logs and recovery copies require separate retention review. A necessary hold must identify the record, reason and next review date; it does not justify retaining everything indefinitely. Policy responses and account settings are deleted with the account. Live deletion is not immediate removal from backups. Recovery copies expire through the actual provider rotation and necessary reviewed disposal. Restored data must remain isolated until completed deletions and restrictions are replayed. A request awaiting review is not a completed deletion; we distinguish confirmed completion from a pending request. See the Retention and deletion page for the current procedure. Your requests and choices Use Account and privacy to export supported own records or request account deletion after fresh verification. The automated export is not a promise that every record concerning you is included or that another person's confidential information will be disclosed. Contact support@rippleend.com for assistance with access, correction, deletion, a concern or an applicable privacy right. We may need to verify authority and review records involving other people, unresolved matters or a documented obligation. We do not ask you to waive applicable rights. You may also use an applicable external complaint route. Policy changes have distinct versions, effective dates and change summaries. Significant changes use the appropriate notice and response process. Acknowledging this notice is separate from agreeing to Terms and Acceptable Use and is not blanket consent to unrelated future processing.

Privacy Notice

What changed