Public Preview Privacy Notice

Information currently needed to operate the service

RSG Alpha uses account authentication and may store account identifiers, session information, language preferences, and user-created workspace records such as journal, replay, governance, or saved analysis data. The service also processes technical request information necessary to operate and secure a web application.

Why information is used

Information is used to authenticate users, provide requested platform functions, maintain user workspace records, operate and secure the service, troubleshoot failures, and improve reliability.

Early-access list

If you voluntarily join the RSG Alpha early-access list, RSG Alpha stores the email address you submit, your selected language, the signup time, and limited referral or campaign parameters such as source, medium, and campaign when present. This information is used to manage the pre-launch list, understand where signups come from, and send launch, product-availability, and important RSG Alpha updates. Joining the list is optional and is not required to view the public preview. The early-access database is configured so public visitors can submit an entry but cannot read the list.

Service providers

The current architecture uses third-party infrastructure and data services, including hosting, authentication/database, source-control/deployment, and market-data providers. Their processing is subject to their applicable agreements and privacy terms. A final notice should list the production providers and purposes after the data inventory is verified.

Cookies and local storage

The service uses browser storage and cookies for functions such as authentication, language preference, and account-scoped application state. Final launch review should verify every production cookie, retention period, and any analytics or marketing technology before making broader privacy promises.

Data minimization and security

RSG Alpha should collect and retain only information needed for legitimate service purposes, restrict access, protect credentials and secrets, and maintain incident-response and deletion procedures appropriate to the information held.

Notification retention and account deletion (pre-launch engineering)

Customer alert delivery remains disabled. The current pre-launch database design deletes account-linked notification settings, ticker subscriptions, contact endpoints, deliveries, delivery attempts, and attached provider-event rows when an account is deleted. To prevent accidental re-contact after an opt-out, bounce, or complaint, a suppression record may retain a pseudonymous SHA-256 fingerprint of the normalized destination without retaining the raw email address or phone number. Provider-side retention is separate and must be addressed in the final notice and vendor terms before customer alerts are activated.

Requests and contact

RSG Alpha provides a first-party privacy request form for access, correction, deletion, or other privacy requests. Do not include passwords, account numbers, brokerage credentials, or other unnecessary sensitive information in a request.

Submit a privacy request →