Privacy

Go Remote Viewing stores account, profile, submission, mission, tenant, billing, revenue inquiry, merchandise preorder, forum, live-chat, case-intake, media-reference, audit, and analytics data required to operate the platform.

For security, abuse prevention, account recovery, and platform operations, restricted operator records may include email address, username, profile fields, signup referrer, signup IP address, login IP address, last-seen IP address, user agent, device/browser classification, hashed activity IP, page paths, clicks, form submissions, and rate-limit events.

Member signal-invitation links may set a first-party attribution cookie for up to 30 days. The cookie contains a signed inviter reference, not the recipient's notes or contact details. If the recipient creates an account, GRV may store the inviter account ID and the date the referral first completes saved practice so rewards are granted once and abuse can be reviewed.

Account recovery and verification records include one-way token hashes, expiration times, requested IP address, user agent, success/failure security events, disabled-account state, and safety lock/unlock history.

Private tenant lab results are isolated by tenant membership and role-based permissions.

Case-intake media is stored as submitted URLs, reference hashes, MIME hints, scan state, and metadata until a production storage pipeline is enabled. Do not submit private, illegal, emergency, or non-consensual material.

Generated target assets may store prompt fingerprints, duplicate-review status, provider payloads, public image URLs, and future perceptual hashes so the platform can reduce repeated targets and preserve auditability.

Payment-related records may include Stripe customer, subscription, checkout, webhook, merchandise preorder, and support-payment metadata. Paid access should be granted only after verified provider webhooks.

Immutable ledger records store score hashes, folder hashes, internal anchor roots, and optional public timestamp/blockchain references. These records are designed for protocol audit and may be retained long-term.

Live-chat data is retained for safety, moderation, protocol review, and abuse prevention. Future audio/video conferencing should add explicit recording consent, retention windows, and deletion controls before those features are enabled.

Image URLs should use signed storage URLs in production when targets are private or tenant-specific.