REACHSTEAD PRIVATE BETA
Privacy Notice
Last updated September 29, 2026
This notice describes the invitation-only beta. The operator should add its legal business name, mailing address, and monitored support email before public launch or external OAuth verification.
Information collected
The beta stores account details, assigned business information, services and goals, public website or profile information supplied or imported by the user, scan results, recommendations, action progress, connection status, synchronization results, security events, and problem reports. An optional problem-report screenshot is visible only to the platform owner.
Connected platforms
When a user authorizes a supported platform, authorization tokens are stored in encrypted form so the requested read-only information can synchronize. The beta does not ask for or store the user’s password for Google, Facebook, Instagram, LinkedIn, X, TikTok, Pinterest, Threads, or YouTube. Each provider also applies its own privacy terms.
How information is used
Information is used to operate the beta, produce business-visibility guidance, synchronize authorized sources, prevent misuse, diagnose failures, support testers, and improve the product. The private-beta operator does not sell beta-client information.
Access and retention
Access is limited to the invited client and the platform owner supporting the beta. Information is retained while the beta account is active and as reasonably needed for security, recovery, and issue investigation. OAuth access can be disconnected in the product. A tester may request account or business-data deletion using the contact method in the beta invitation.
Security and limitations
The beta uses account isolation, hashed passwords, protected sessions, encrypted connection tokens, activity logging, and restricted administrator controls. No system can guarantee absolute security. Testers should not enter payment-card data, government identifiers, medical records, or other unnecessary sensitive information.
Questions
Contact the beta administrator using the email or contact method supplied with the invitation.