Security messaging without inflated claims
Firepype is designed around practical safeguards, transparent language, and user control over provider permissions.
Core controls
A concise view of the controls that shape Firepype's security posture.
OAuth flows
Provider access is authorized through OAuth where available. Firepype does not require you to store provider passwords in form fields.
Encryption in transit
Data transfer channels are expected to use transport encryption between systems. We avoid claiming guarantees beyond what deployment and provider constraints can support.
Scoped permissions
Access is limited by the permissions granted during connection setup. Users remain responsible for selecting least-privilege scopes that fit their workflow.
Data handling stance
Firepype's role is orchestration. Providers continue to host your files and mailbox content.
Firepype coordinates operations based on your job settings. We do not claim ownership of your content, and we do not market data resale as part of the product model.
Logging and notifications exist to support operational visibility, troubleshooting, and accountability. Retention behavior should be published clearly as implementation matures.
This site is a prototype presentation. Signup and supporter flows are demos and do not process real authentication or payment transactions.