ProjectScope 360
Security, with clear boundaries.
Implemented controls are described below. They are not a certification or a guarantee that every security risk has been eliminated.
Implemented access controls
Lovable Cloud authentication supports email verification and password recovery. Database row-level security (RLS) scopes project records to workspace membership. Owner, admin, member and viewer roles are stored separately from profiles; database checks restrict role changes.
Seller administration uses a separate service-managed permission. Being a workspace owner does not grant access to other customers or seller settings.
Payment and data controls
Stripe checkout handles card entry. The app verifies payment webhook signatures before updating workspace subscriptions. Test and live subscription environments are kept separate; client-side screens are not the authorisation boundary.
CSV exports neutralise spreadsheet formula-leading text. The public demo uses isolated fictional data. AI requests require a paid eligible workspace and its configuration flag, and read records within the caller’s access.
What has not been established
No ISO certification, SOC 2 report, GDPR certification, independent penetration test or contractual SLA is claimed. Automated tests and source review are not a substitute for an independent assessment.
Full sandbox buyer purchase, email acceptance, tenant-isolation and expired-plan behaviour still require authenticated end-to-end evidence. Operators should assess data suitability and procurement requirements before a pilot.