Trust Center

1. Each workspace is kept apart

Every organization has its own workspace. Separation is enforced by the database itself, using row-level security on every table that holds workspace data: a request made for one organization cannot read another's records, whatever the application asks for. The application connects with a restricted database role that cannot bypass these rules.

An automated isolation test runs on every change to the code and fails if one organization's data could ever be read from another's session.

2. Access inside your workspace

• Roles: Owners, Admins and Members, each with its own permissions; Owners and Admins can adjust roles and add their own.
• Private teams: new teams are private, so their projects and tasks are seen only by their members and by your Owners and Admins.
• Finance: off by default. Books are visible only to people given finance access, one organization at a time.
• Library: each section has its own audience, and sections can be kept out of Rose's AI entirely.
• Connected accounts: calendar and mail connections belong to the person who connected them.

3. Sign-in and multi-factor authentication

Sign-in is handled by Supabase Auth. Rose is invite-only: nobody can create an account in your workspace unless one of your Owners or Admins adds them. Every sign-in is two steps: your password, then a code from an authenticator app. There is no way to sign in without the second step, and an Owner can reset a lost authenticator from People › Members.

Session cookies are secure and HTTP-only. Removing or deactivating a person ends their access to the workspace.

4. Support access, only with your permission

• Rose staff are not members of your workspace and cannot sign in to it.
• To get help, one of your Owners creates a one-time support code in Settings and chooses how long it lasts. We can only enter your workspace with that code, and only until it expires.
• The support view is read only, enforced by the database. It does not show anyone's connected mail or calendar.
• If we need to change something, we ask, and one of your Owners must approve before we can.
• Every support session and every change made during it is recorded in your Audit Log, and your Owners can end a session at any time.

5. Viewing as a member, and protection from it

Inside a workspace, an Owner can use View as to see Rose as one of their own members see it, read only for up to an hour, with a second step before any change. Every session is recorded under both names. Owners, and anyone whose role includes Cannot be viewed as, are protected: the database refuses to start such a session. Each person can check that protection live in Settings › Privacy, which reads it straight from the database and lists every time anyone has viewed Rose as them.

6. Audit logs

Changes to people and access, support and view-as sessions, and changes to important records are written to an audit log; sign-ins are recorded by Supabase Auth. The database rejects any attempt to edit or delete an audit entry. Your Owners and Admins can read your organization's log in People › Audit Log.

7. Encryption

• All traffic to Rose uses HTTPS (TLS).
• Data is stored with providers that encrypt it at rest.
• The tokens that let Rose reach your connected Google, Microsoft, Calendly, QuickBooks and Zoho accounts are additionally encrypted with AES-256-GCM, decrypted only in memory when needed, and never sent to the browser.
• Service secrets are kept in our hosting provider's encrypted environment settings, never in the code.

8. Connected accounts and your books

Accounting connections are read only: Rose never writes to QuickBooks or Zoho Books. Only people with finance-administration rights can connect books. Any connection can be disconnected at any time, which revokes our access with the provider and deletes the stored credentials.

9. AI and your data

When you use an AI feature, the content it needs is sent to our AI providers to produce the result. We configure these services so that customer information is not used to train their general models. Library sections can be marked so Rose never reads them. Our providers are listed on the Data Protection page.

10. Data location and retention

• Information is stored and processed in the United States.
• Meeting audio is deleted after 30 days; transcripts and action items after one year.
• Disconnecting a calendar or mail account deletes what Rose stored for it.
• When an organization closes its account, we delete or de-identify its information on request, except what the law requires us to keep.

11. Reporting a security issue

If you believe you have found a security vulnerability in Rose, email admin@paragonroofingsolutions.com with the details. Please don't access other people's data or disrupt the service while testing. We will confirm receipt and keep you updated.

12. Contact

Rose Tech HQ LLC · 4 Haddonfield Rd, Cherry Hill, NJ 08002 · admin@paragonroofingsolutions.com