Privacy

Raypx is an open-source application skeleton. The upstream project does not collect, transmit, or store personal data on its own.

When you clone and run Raypx yourself, account records, sessions, workspace data, audit events, and integration settings stay in the database and infrastructure you configure.

Authentication is powered by Better Auth. The app stores account identifiers, session records, and credentials required for sign-in flows in the configured Postgres database.

Session cookies are used to keep users signed in and to protect authenticated dashboard routes.

Optional integrations such as analytics, email delivery, storage providers, or observability tools only become active when an operator configures the relevant environment variables.

A hosted deployment may have its own privacy practices. If you use someone else's deployment, review the operator's privacy notice for details.

Questions about the codebase, data flow, or privacy-sensitive implementation details are best raised in the Raypx GitHub repository.