Website visits
The website measures its own visits, with no third-party analytics or advertising scripts. It sets a first-party cookie, sr_vid: a random visitor id used for site statistics and for attribution. It lasts 13 months and is set only when your browser does not already have one. It is never sold. It uses HttpOnly, Secure and SameSite=Lax protections.
When you sign in, sign up, accept an invitation or request a demo in that browser, screenRIG links the visitor id to your account so our team can see which pages, referring sites and campaigns brought each customer. Only screenRIG staff see that link; it is never shown to other customers or shared with advertisers. Staff sign-in sets a first-party marker cookie, sr_staff, so internal browser traffic is excluded from website analytics. This cookie contains a constant marker, has no account identifier, and lasts 400 days.
When you arrive from an ad, the ad's click identifier is kept for 90 days so screenRIG can report to that ad network which clicks led to a new account; no name, email or other account details go with it.
Our edge servers log request details, including your IP address, for operations, security and debugging. Website visitor logs keep the visitor id, the IP address, the path, the whole query string (credentials removed), the referring page (host and path), the browser user-agent and the kind of request for 30 days.
When you copy or select an install prompt, a first-party request to /cta records which prompt you used. Demo buttons, form starts, outcomes and video playback use the same first-party measurement. Saved requests and confirmed bookings are counted from their successful responses. This measurement uses the same visitor cookie and creates no additional analytics cookie.
Demo requests
When you request a demo, we collect your email, country, intended screen count, organization category, annual budget bracket and timezone. We use these details to choose a live or on-demand demo and respond to your request. AI services help qualify the rollout and research publicly available company information from your email domain; the full email address is not sent to these services. Our team handles request details and updates in its Slack workspace.
Live demos use Google Calendar and Google Meet. Your email is used for the meeting invitation, confirmation and reminders. A separate protected demo session cookie lets your browser return to the saved request and booking; it expires after seven days. Private invitation links let you open the request in another browser. Keep those links to yourself.
Anonymous flow identifiers connect the demo funnel steps in visit logs. Your email and qualification answers are not included in measurement URLs or stored in browser storage.
Credentials
The plugin keeps its account credential in a file restricted to your user account, outside its replaceable installation directory. Player authorization is separate from the public website. Keep credentials and private setup links out of public posts and feedback reports.
Customer content
Media, application packages and runtime state are not public website assets. Players receive protected content under their current screen authorization. Each immutable application release runs on its own isolated release origin. See the technical reference for authentication and data formats.
Questions and corrections
Use the product-feedback options on Contact. If reporting a defect through the plugin, describe the issue without including credentials or private customer content.