Guides
Messenger privacy and data lifecycle
This guide describes the behavior implemented in Ridgetop today: when the widget creates identity, what consent controls, which browser and network surfaces it uses, how announcements are measured, and how workspace retention and rights workflows operate.
Current regional availability
Hosting boundary
Data regions and hostnames
A data-plane label is an isolation boundary for the application, database, private Storage, widget APIs, scheduled jobs, and operational credentials—not a statement that every optional provider is EU-only.
Current service
The attached production environment is documented in us-east-1. Workspaces use the hostname and credentials of that deployment.
Planned EU service
The planned employee hostname is app.eu.ridgetop.io, with regional widget, API, help, operator, and optional time-tracker hosts. Those production surfaces are not live yet.
Regional accounts
The first regional design uses separate sign-ins and sessions. Direct invitations and recovery links must stay on their regional host; a future region picker must not query by email or create a global identity directory.
A future EU-core-hosting scope may cover the regional application runtime and primary Supabase data plane while naming global CDN, billing, email, connected services, AI, logs, control-plane, and support-access exclusions. “Strict EU residency” is a different claim and is unavailable unless every enabled path has verified EU-only storage and processing.
Messenger identity
Email-free signed users and anonymous visitors
Messenger needs a stable signed user ID for an authenticated customer. Email and name are optional profile fields, not identity requirements.
Signed-in customer
- The customer server signs the exact JSON payload with HMAC-SHA256. Required fields are
id, the exact pageorigin, and a freshiatin whole seconds. - Leaving
emailornameout preserves the stored value. Sending a non-empty value updates it; sendingnullclears it. - The identity response is not cached, is valid for five minutes, and never exposes the signing secret to browser code.
Anonymous visitor and lead
- A dormant page load creates no visitor record or support session. Once the workspace policy permits activation, the host page creates a random visitor bearer key.
- The visitor can read help, receive eligible announcements, and start a conversation without supplying an email. Starting support creates a lead associated with that visitor.
- When the same browser later supplies a signed identity, Ridgetop claims the anonymous history for that customer and retires the old browser key.
Collection controls
Activation profiles and consent
Administrators choose a baseline profile and can override each feature to run right away, after engagement, with consent, or not at all.
| Profile | Messenger | Guide and announcement display | Guide and announcement measurement | Product analytics | Session replay |
|---|---|---|---|---|---|
| Customer managed | Right away | Right away | Right away | Right away | Right away |
| After engagement | After engagement | Right away | After engagement | After engagement | After engagement |
| Consent manager | After engagement | Right away | With consent | With consent | With consent |
Four separate permissions
The support, analytics, replay, and marketing purposes are mapped independently. Messenger and announcement display do not silently grant measurement, analytics, or replay.
Messenger → support
Starts support identity, conversations, and message delivery.
Guide and announcement display → marketing
Shows eligible guides, banners and Messenger posts without recording that they were seen.
Guide and announcement measurement → analytics
Records when guides and posts are shown, completed, dismissed or clicked.
Product analytics → analytics
Collects configured product events and page activity.
Session replay → replay
Captures a masked visual replay of an eligible session.
Provider behavior
Available provider modes are nonecustomonetrustcookiebot. OneTrust and Cookiebot are read in the customer page with workspace-configured category mapping; Ridgetop receives normalized booleans, not a raw consent string.
For a custom provider, call Ridgetop.setConsent() with the current values and again on every change. Omitted permissions keep their prior browser value; sending false withdraws one.
Missing or mismatched providers fail closed for consent-controlled features. Withdrawal stops future collection without a reload, stops replay, and discards queued or pre-consent events rather than uploading them later.
Browser surface
Local storage, cookies, and network requests
The embedded Messenger code does not use cookies for visitor identity, analytics joining, or drafts. It uses the following local-storage records when the relevant behavior is active.
| Key | Location | Purpose | Lifecycle |
|---|---|---|---|
ridgetop:visitor:<publicKey> | Customer page origin · local storage | A random bearer key that lets an activated anonymous visitor return to their conversations. | Created only after policy activation. It is retired after the history is claimed by a signed-in identity; clearing it makes the next activation a new anonymous visitor and removes browser access to the old anonymous history. |
ridgetop:analytics:<publicKey> | Customer page origin · local storage | A random analytics-session key and last-seen time used to join allowed events within a visit. | Written only when analytics identifiers are activated. It is reused for up to 30 minutes of inactivity; blocked storage falls back to an in-memory page identifier. |
ridgetop:draft:<owner>:<conversation> | Ridgetop widget origin · local storage | The current unsent message body and formatted HTML for a customer or anonymous visitor. | Removed when the draft is emptied or sent. Clearing Ridgetop widget site data also removes it. |
Ridgetop employee authentication and a customer’s own consent manager may use cookies separately; those are outside the embedded Messenger storage records above.
| Phase | Ridgetop requests | Behavior |
|---|---|---|
| Page load | widget.js, /widget, /api/widget/config, and optionally GET /api/widget/guides/public | Loads the client, resolves the workspace policy, and may retrieve a non-confidential manifest of public banners. It does not create a visitor, lead, session, or guide progress. |
| Activation | /api/widget/consent and /api/widget/session | Runs after the configured engagement or consent trigger. The session exchange receives either a signed identity or the anonymous visitor key and returns an opaque, expiring widget session. |
| Support use | /api/widget/help, /api/widget/conversations, and /api/widget/messages | Loads help content and the visitor's own support history, then sends or polls messages after activation. |
| Allowed measurement | /api/widget/events, /api/widget/replay, /api/widget/guides, /api/widget/guides/events, and /api/widget/checklists/tasks | Receives product events, masked replay chunks, and measured guide and post actions only when the resolved policy permits the corresponding feature. Checklist progress is kept with each person's guide history, like a dismissed guide, so the Messenger shows the same progress on every device. |
| Surveys and ratings | /api/widget/surveys/answers, /api/widget/csat, /api/widget/csat/answer, /api/public/csat/{token}, and /api/public/surveys/{id}/answers | Records answers a person chooses to give to a survey shown under the guide display setting, CSAT ratings for their own closed conversations in the Messenger or from the link in a CSAT email, and answers on a hosted survey page opened from a survey email or a survey's public link. Answers are kept even when measurement is off because the person submitted them; an anonymous survey, or one answered by public link, stores no identity with its answers. |
| Feedback and ideas | /api/widget/feedback, /api/widget/ideas, /api/widget/ideas/vote, /api/widget/ideas/comments, /api/widget/ideas/suggest, and /api/widget/ideas/updates | Sends feedback a person chooses to give from the Messenger or a guide button: their text, a category, the page path and title without its query string, and an image only if they attach one. It's kept with the signed-in person or the anonymous visitor, follows the feedback retention period, and is never written for someone whose processing is restricted. Signed-in people the workspace shows its idea board to can read published ideas, vote, comment and suggest ideas; other people see vote counts and comments, with first names only when the workspace allows them and never companies. Ideas a person backed that shipped are shown once until dismissed. |
Guides
Guide and announcement delivery is separate from measurement
Banners, Messenger posts and other guides are shown under the display setting and measured only under the measurement setting. An eligible public banner can be useful before the visitor consents to measurement or activates Messenger.
Public unmeasured delivery
No receiptFor a banner marked for public pages, the browser may fetch a non-confidential manifest and display it by page. That path uses no identity credentials and creates no widget session, visitor row, lead, guide progress, or event, and personal details in the banner fall back to their default text.
Measured delivery
Policy controlledAfter the resolved activation permits a session, Ridgetop evaluates each guide’s audience on its servers and keeps each person’s progress, so a dismissed guide stays dismissed. When measurement is permitted it also records when guides are shown, completed, clicked, and dismissed. Guide results count only measured events.
Survey answers and CSAT ratings
Given by the personA survey is a guide, so it is shown under the display setting. Its answers are kept even when measurement is off, because the person chose to submit them; an anonymous survey stores no identity with its answers. CSAT ratings after support conversations come from the Messenger or from a one-time link in a CSAT email, and the rating page saves nothing until a score is picked. A survey sent in a marketing email gives each recipient a signed link of their own; a survey can also be opened to anyone with its public link, and those answers carry no identity. Answers follow the survey-response retention period and are included in access exports, erasure, and restriction. A workspace on the Scale plan can send survey alerts to its own Slack.
Workspace lifecycle
Retention by data category
Workspace administrators set seven application-data periods in Data & privacy. A daily regional job deletes eligible records in bounded batches and removes queued attachment and replay objects through the regional Storage API.
| Category | Default | Allowed range | Scope |
|---|---|---|---|
| Support conversations | 2 years | 30–3,650 days | Closed and spam conversations, messages, delivery payloads, and attachments. |
| Anonymous visitors | 90 days | 1–365 days | Unclaimed visitor identities that have no support lead or signed-in customer. |
| Product analytics | 365 days | 30–1,095 days | Analytics sessions, product events (including the structure and visible labels of clicked buttons and links, except in masked areas), and automatically discovered unnamed pages. |
| Session replay | 14 days | 1–365 days | Replay metadata, queued chunks, and private regional Storage objects. |
| Guide and announcement history | 365 days | 30–1,095 days | Each person's guide and checklist progress and the measured events: shown, completed, clicked, and dismissed. |
| Audit history | 7 years | 365–3,650 days | Workspace audit records; data-subject case evidence follows its own lifecycle. |
| Survey responses | 3 years | 30–3,650 days | NPS, CSAT and other survey answers and comments, including ratings after support conversations. |
| Feedback | 3 years | 30–3,650 days | Feedback people send from the Messenger or a guide button, with any image they attached. Ideas, votes and comments stay while the idea does and leave with the person on erasure. |
Backups and preservation holds are separate
Data-subject requests
Access, correction, restriction, and erasure
The organization that operates a Ridgetop workspace is the first contact for a request about that workspace. Ridgetop supplies authorized staff with a workspace-scoped, regional workflow.
Locate
Authorized privacy staff can search within one workspace and data plane by signed external ID, current or historical email, typed secondary identifier, or an anonymous visitor key supplied by the requester.
Access and export
After identity verification, staff can produce a JSON export of the supported customer, support, analytics, replay, guide and announcement, identifier, audit, and integration records associated with the match.
Correct
Verified staff can change or clear optional name and email data without creating a second customer identity.
Restrict
Restriction freezes supported processing, revokes active Messenger sessions, and acts as a preservation hold for scheduled retention.
Erase
Verified erasure removes eligible regional relational records and private attachment or replay objects. A redacted case timeline and aggregate completion evidence remain.
Exceptions
A documented legal, contractual, fraud-prevention, or accounting exception can delay restriction or erasure until its review date; the case records that the data was not deleted.
Verification, downstream systems, and workspace termination
A match alone does not permit disclosure or mutation: authorized staff record identity verification first. The product workflow covers its inventoried regional database and private Storage objects. Connected-provider deletion and workspace termination are coordinated through the workspace’s support or contractual contact, then checked against provider deletion, backup, legal-hold, and account-termination procedures. There is no current self-service workspace-erasure control that should be represented as immediate deletion from every processor or backup.
Processing chain
Provider paths, DPA, and international transfers
Enabling a feature can add a provider path outside the primary application data plane. The categories below describe the paths present in the current implementation; exact availability depends on workspace configuration.
| Category | Provider paths | Data and purpose |
|---|---|---|
| Core hosting | Vercel and Supabase | Application requests, authentication, database records, private object storage, logs, and backups. |
| Email and billing | Resend and Stripe | Transactional or support email and the minimum billing, tax, invoice, and subscription data needed for those services. |
| Connected services | GitHub, Google, Microsoft, and Slack | Only data for integrations a workspace chooses to connect, subject to the provider path and account configuration. Workflow notifications and survey alerts sent to Slack can include a respondent's name, answers, and comments. |
| Customer webhooks | Destinations the workspace registers | Workflow events sent, signed, to https addresses that people who manage workflows add under Connected apps, by workflows with a Send webhook step. A delivery carries the workflow's values for the event, which can include a ticket's customer name, email and message or a survey answer and comment. Nothing is sent for people whose processing is restricted; deliveries, with what they sent, are kept 30 days and are deleted with the person or survey response. |
| AI processing | Customer-selected Anthropic or OpenAI, or the Ridgetop private AI path | Prompts and bounded workspace context for enabled AI features. Current AI paths are not part of an EU-core or strict-EU claim. |
| Public edge and abuse protection | Cloudflare | Public-site HTTP metadata, security signals, and Turnstile verification when that protection is enabled. |
Contract evidence is still a launch gate
This technical guide describes product behavior and is not legal advice. The Ridgetop Privacy Policy describes Ridgetop’s general privacy practices.