Data security

Your documents often contain financial and personal information. Here is how Parsedit protects them.

Account isolation

Every document, parser, and extracted value belongs to exactly one account, and isolation is enforced at the database level with row-level security. The database itself refuses queries that cross account boundaries, so isolation does not depend on application code behaving correctly. Team members see shared data only through their role permissions.

Your data is not used to train AI models

Extraction is AI-powered, and your documents are processed only to produce your results. Neither your documents nor your extracted data are used to train AI models.

Limited Google access

When you connect Google for Sheets or Drive import, Parsedit requests only the drive.file OAuth scope. That scope grants access exclusively to files you explicitly pick or create through Parsedit. Parsedit cannot browse, list, or read anything else in your Google Drive.

Secure storage and transport

• Documents are stored in access-controlled cloud storage scoped to your account.
• File downloads use short-lived signed URLs rather than public links.
• Integration credentials (OAuth tokens, webhook secrets) are stored encrypted.
• All traffic between your browser and Parsedit, and between Parsedit and your destinations, uses HTTPS.

Access controls

• Multi-factor authentication is available for every account.
• Inbound webhooks support a shared secret header, and API access is scoped per token and revocable at any time.
• Connected applications can be reviewed and revoked under Integrations → Connected applications.