EFFECTIVE 1 OCTOBER 2026 · EARLY BETA

Privacy notice

Scopeflow is an independent beta operated by VijeyaHasen. Privacy and support contact: hasenhamesh15@gmail.com.

Information used

Signing in supplies a site-specific account identifier and may supply your email and display name through Neon Auth. The application stores the account identifier with projects. It stores scope text, client names, fees, dates, version history, review-link tokens, reviewer-entered names and comments, decision timestamps, and hashed API tokens with their expiry dates. Do not include passwords, payment card details, or unnecessary sensitive information in a scope.

Purpose and access

This information is used to save scopes, create review links, record decisions, authenticate API requests, and provide support. The app and its policies are publicly accessible. Saved projects require account authentication. Anyone possessing an active, unrevoked review link can read that version and submit its one decision while it is current. Reviewer names are self-reported. Review links also show the previous version’s changed fields. Only include information intended for your reviewer.

Service providers and agents

The site uses Render hosting and Neon PostgreSQL storage and authentication infrastructure. Neon Auth manages signup, login, passwords, email verification, and recovery. These providers process requests and may maintain operational and security logs under their own policies. The application does not add advertising trackers or sell data. It does not currently call an AI model with scope content. When you configure an agent or connector with a Scopeflow API token, the scope content and recorded decisions you request are returned to that agent under its provider’s policies. API tokens are account-scoped and stored as hashes; the app does not expose its Neon database credentials. If you manually send a brief to Muse, or later authorize a Muse connector to read your scopes, Meta processes the information under its own policies and your connector settings.

Retention and control

Project versions and decisions remain stored to provide the project history until you delete them. There is no automatic project expiry in this beta. Rate-limit records store an account or review-version identifier, minute window, and request count to control write traffic; they do not store IP addresses. API tokens expire after 30 days and can be revoked from the Muse & API page. Export each selected project and its version history from the workspace. Revoke or replace review links there to block their prior URL. Delete all your Scopeflow data directly from Data controls after signing in and typing DELETE to confirm. This removes your projects, versions, reviewer decisions and comments, review links, ledger entries, API tokens, and associated rate-limit records from the live application database. Your Neon Auth login account remains active; this control deletes Scopeflow application data. Exported files and copies shared elsewhere are not removed. Contact the operator for correction of personal details or access assistance; ownership verification may be needed. Deleted application data may remain temporarily in provider backups or logs according to provider retention practices.

Cookies, payments, and updates

Hosting authentication may use session cookies. This beta does not collect payments or store card information. If data practices change, this notice will be updated before the changed feature is enabled. This beta is intended for adult professionals.