Trust
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.
Community safety records may include reports, report reasons, moderation decisions, and account-to-account blocks. A block hides the blocked member's community content and leaderboard entries from the blocking account; operators may retain the block record for the life of the account or until it is removed.
Professional-directory inquiries may include experience, preferred schedule, pricing range, contact preference, and the purpose of a requested one-to-one session. No professional booking payment is collected during the founding-introduction phase.
Image URLs should use signed storage URLs in production when targets are private or tenant-specific.
Analytics
Go Remote Viewing measures how the website and app are used with its own first-party analytics so we can see which pages help people and fix what does not. Analytics events are stored on our own servers and are not sold or shared with advertisers.
What we record: the pages you open; clicks on buttons and links, identified by the element type, a short label we assign, or the destination path, never the visible text you clicked; approximate time on page; search terms you enter in site search, with anything that looks like an email address removed; client-side errors; device type and browser family; and the referring site and campaign (UTM) tags of the link that brought you here.
What we never put in analytics: passwords, the contents of form fields, email addresses, or password-reset and verification tokens. Links that carry a token have their query string removed before anything is recorded.
IP addresses are not stored in analytics events. Each event keeps only a salted one-way hash of the IP, which lets us spot automated abuse and count unique visitors without keeping the address itself.
A random identifier in your browser's local storage groups page views into visits. If you create an account, the same browser's page views from up to 7 days before signup may be linked to the new account so we can learn which pages help people join. That link is first-party only and is never made across browsers or devices.
Analytics events are kept for a limited period, about 13 months by default, and then deleted. Account security records described above follow their own retention.
iOS app: when you are signed in, the app's normal requests to our servers (opening the app and syncing, saving practice, and posting in the community) are recorded as usage of your account, in the same way as the website. Guest mode on iOS stays on your device and sends nothing to our servers.
Third-party analytics is off by default. If we enable a provider, we prefer cookieless services such as Plausible or Umami. Cookie-based tools such as Google Analytics will not be enabled for visitors in regions that require consent until a consent banner is in place.
Service providers we use
Go Remote Viewing runs on a small set of third-party services. Each one receives only the data its job requires, and none of them receives data to sell or to advertise to you. The providers are:
Railway — application hosting and the managed PostgreSQL database. All account, content, and platform data is processed and stored there on our behalf.
Stripe, including Stripe Connect — subscription billing, checkout, Hire-a-Viewer escrow payments, and viewer payouts. Stripe receives your name, email, and payment details; card numbers go directly to Stripe and are never seen or stored by GRV.
Resend — transactional email delivery (verification, password reset, receipts, and notifications). Resend receives the recipient email address and the message content.
Google Workspace — our support and operations mailbox, and one of the sending paths for account email. If you email us, Google processes the address and content of that correspondence.
Cloudflare R2 and S3-compatible object storage — uploaded and generated media files (target images, avatars, attachments) and their file metadata.
OpenAI — AI session judging and image generation when those features are enabled. Session text and image prompts are sent for processing.
Pollinations, AI Horde, and Cloudflare Workers AI — additional image-generation providers used when enabled. They receive image prompts only.
Inngest — background job processing (scheduled reveals, reminders, digests). Job payloads contain the account and content identifiers the job needs.
Plausible and Umami — optional cookieless website analytics, if enabled. They receive aggregate page-view data without cookies; see the Analytics section above.
Google Analytics, Google Tag Manager, and Microsoft Clarity — optional cookie-based analytics and session-replay tools. They are off unless the operator enables them AND you allow them in the cookie banner; see the Cookies section below.
Apple — distribution of the iOS app through the App Store. Apple's handling of App Store data is governed by Apple's privacy policy; the app itself communicates only with GRV servers.
Polymarket — a public market-data source for associative-remote-viewing missions. GRV reads public data from it; no personal data is sent.
IndexNow (Bing and Yandex) and Google Search Console — search indexing of public pages and operator-side search-performance statistics. These receive public page URLs, not personal data.
Cookies
Essential cookies keep you signed in, protect forms, and remember operator gates. They are required for the site to work and are not used for advertising.
The member signal-invitation attribution cookie described above is first-party, lasts up to 30 days, and contains a signed inviter reference only.
A first-party consent cookie remembers your analytics choice for 180 days. Cookie-based analytics (Google Analytics, Google Tag Manager, Microsoft Clarity) load only if you choose Allow in the cookie banner; the banner appears until you choose, and the Cookie Settings control in the site footer clears your choice so you can decide again.
Cookieless measurement — our own first-party analytics and, when enabled, Plausible or Umami — does not set cookies and is covered in the Analytics section above.
Your rights: access, export, and deletion
You can edit your profile at any time in Settings. To receive an export of your account data, email support@goremoteviewing.com from your account address and we will prepare it.
You can delete your account yourself at any time: on the web, Settings → Delete your account; in the iOS app, the Delete Account screen. Deletion is permanent: it removes your profile and your owned tenant labs and signs you out everywhere. You can also ask the support desk to delete your account by email.
Some records outlive an account by design, as described above: anonymized score-ledger and audit hashes kept for protocol integrity, payment records Stripe and GRV must retain for tax and accounting, and moderation or safety records needed to enforce bans. These are not used to identify you after deletion beyond what the law requires.
We respond to privacy requests within 30 days. For any privacy question or request, contact support@goremoteviewing.com or the Contact & Safety page — both reach the operator responsible for privacy at Go Remote Viewing.