Account access
Supabase Auth handles account authentication. Protected routes use a verified user session and role-aware access checks. SSO is planned and is not currently configured with an identity provider.
A current overview of application access, subprocessors, retention, and the controls Cadivor is still building.
Supabase Auth handles account authentication. Protected routes use a verified user session and role-aware access checks. SSO is planned and is not currently configured with an identity provider.
Product APIs scope reports and decisions to the active workspace and authorized members. Shared links are limited to the specific content described by that feature.
Supplier, AI, email, and payment credentials are configured server-side and are not sent to the browser by product routes.
Where billing is enabled, Stripe processes checkout and subscription payments. Cadivor does not store full card numbers.
Certification status: Cadivor does not currently claim SOC 2, ISO 27001, or another independent security certification. A SOC 2 readiness plan is in progress; it is not an audit or certification.
These providers support the current product or marketing deployment. Specific feature use depends on configuration and customer activity.
| Provider | Purpose | When used |
|---|---|---|
| Cloudflare | DNS, edge delivery, and public marketing-site hosting | Website requests |
| Railway | Application API, web application, and scheduled service hosting | Product use |
| Supabase | Authentication and application database services | Account and workspace use |
| Stripe | Payment checkout and subscription billing | When billing is enabled and a user purchases |
| Resend | Transactional email delivery | When a verified sender and delivery credentials are configured |
| OpenAI or configured compatible endpoint | AI-assisted question answering and analysis features | When a user invokes a feature that uses the configured model endpoint |
Supplier catalogs such as DigiKey, Mouser, Newark, and Nexar are data sources used by supported workflows, not hosting or authentication subprocessors. Coverage depends on the configured integration.
Shared summary links stop working after 30 days. Public audit rows are targeted for deletion after 30 days and email lead metadata after 180 days; the database cleanup schedule must be enabled in the production database for those deletion windows to run automatically. You can request earlier deletion by contacting [email protected].
Optional analytics are off unless a visitor opts in. Events exclude email, IP address, BOM contents, and component identifiers; event records are retained for up to 180 days.
Workspace records are retained while the account is active. Workspace admins can delete supported saved BOM and report records in the product. Configurable workspace retention periods are not available yet. Account-level deletion is handled through a verified request to [email protected]; backup and provider retention windows may apply.
Email [email protected] from the account address and identify the account or data you want removed. Cadivor verifies the request before acting and may retain limited records where required for legal, security, or payment obligations.
Download the current questionnaire or send a security question. The questionnaire labels items that still need confirmation.