Safeguards
Depending on the system and data, safeguards may include:
- access controls and role-based permissions
- tenant isolation and database controls
- logging and monitoring
The statements under 'How your documents are handled.' and 'Your controls' are quoted from the published Privacy Policy and Terms; the processor table follows the published Processor List, with the payment processor shown by its role.
Depending on the system and data, safeguards may include:
Supabase takes automated daily backups of our database, which they retain for seven days; those backups are held by Supabase and are not separately downloaded or stored by us.
Copies may persist in the backups described above until those backups expire on the schedules stated — no more than seven days for database backups and ninety days for encrypted document copies.
We do not use Customer Content—including policy, payroll, employee, claim, loss-run, or customer document data—to train or improve generalized or shared machine-learning models.
We do not sell personal information for money.
We do not share personal information for cross-context behavioral advertising.
Complete payment-card numbers are intended to be collected and processed by our payment processor, not stored by Premwise.
For the self-serve employer-direct service, Premwise does not review your findings: no Premwise person approves, edits, or signs off on them.
No system is completely secure, and we cannot guarantee that an incident will never occur.
Customer may revoke future access as stated in the authorization or by contacting Premwise.
Revocation does not undo access or processing completed before revocation became effective, does not require deletion where retention is legally required, and may prevent completion of the Services.
Customer may self-serve export its Customer Content and final documents in machine-readable form at any time during the Term and for thirty (30) days after termination.
In no case will Customer Content persist more than one hundred fifty (150) days after termination: up to thirty (30) days for you to make a deletion request, up to thirty (30) days for us to delete it from our live systems, and up to ninety (90) further days for the backup copies described above to expire.
They may process information only for the contracted purpose and under confidentiality, security, use-restriction, deletion, and subprocessor terms appropriate to the information.
Additions require notice to Customers before the new subprocessor begins processing, per MSA §8.2(e).
Read the Processor List| Provider | What it does for Premwise |
|---|---|
| Supabase, Inc. | Application database, authentication, and object storage for customer-uploaded documents |
| Vercel Inc. | Application hosting and serverless compute — the product itself runs here |
| Anthropic PBC | AI-assisted extraction of fields from customer-supplied documents |
| Cloudflare, Inc. | Object storage (R2) for encrypted copies of customer-uploaded documents |
| Payment processor | Payment processing, subscription billing, and invoicing |
| Resend, Inc. | Transactional and operational email delivery |
| Functional Software, Inc. (Sentry) | Application error monitoring |
| HubSpot, Inc. | Customer-relationship records for prospects and customers |
| Plausible Insights OÜ | Product and site analytics |
Report privately.
Acknowledgement within 2 business days; initial assessment within 5.
/.well-known/security.txtPremwise is software. Premwise is not your broker, carrier, or attorney, and it never submits anything to a carrier, rating bureau, or third party.
Other questions: support@premwise.ai
Ready to start?
Create account