Porter logo
Porter

Porter

App description

Connect Ramp to Porter to import card transactions and bills into your accounting workflow. Review source-linked spending, track bill status, and see which items need attention before the books close. Porter helps your team keep Ramp activity alongside the rest of your financial records.

Security and compliance

Production access is restricted to a small number of internal operators with documented business need. Specifically:

• Engineering and operations staff with production credentials can access the application database for debugging and customer support, scoped per-incident. Access is logged in Render and Supabase audit trails. Access reviews are part of Porter's operating security program.
• Customer-facing operators (Porter's managed bookkeeping team) access customer workspaces only via the same role-based product UI that customers use, gated by the same Kinde JWT + per-company role check. They do not have direct database access.
• No general-purpose BI tool, analytics warehouse, or employee dashboard is plugged into customer-identifiable transactional data. Aggregate product metrics (e.g., sync counts) are captured separately and do not surface specific customer transactions.
• AI subprocessors (OpenAI, Anthropic) receive scoped, request-shaped data only as required to power specific Porter features (e.g., transaction categorization). They are contractually prohibited from training on Porter customer data per their commercial API terms.

Porter maintains a written incident, token-compromise, and restore runbook covering containment, credential rotation, evidence preservation, rollback, and customer communication for any situation where access boundaries are suspected to have been crossed.

Active customers. Customer data — including Ramp-sourced card transactions — is retained for the duration of the active Porter subscription so the customer has a continuous bookkeeping history. There is no automatic purge while the account is active.

OAuth token lifecycle. Tokens are retained only while the Ramp connection is active. When a customer disconnects Ramp from Porter's Settings, the stored access and refresh tokens are deleted from the secrets database and Porter stops pulling new Ramp data. Previously ingested transactions remain in the customer's Porter workspace as part of their accounting history.

Account closure. On customer account closure, the customer can request deletion of their workspace data. Deletion is executed within 30 days of the request. Supabase backups age out per the platform's standard point-in-time recovery window (currently 7 days), after which deleted data is unrecoverable.

Operational logs. Application logs on Render are retained 30 days. Error telemetry in Sentry is retained per Sentry's default (30 days), with personally identifiable information scrubbing enabled.

Porter does not currently retain Ramp-sourced data for any purpose beyond serving the customer's active bookkeeping workspace.

https://www.buildwithporter.com/security

App information
Developer
Porter Agents Inc.
Category
Accounting

Discover more integrations

Ramp integrates with all your existing software so you can manage your business with ease—from one place.

Time is money. Save both.