01
Authenticate
Sign-in and session handling stay tied to Firebase Authentication.
Security
Security atRearvy.
How Rearvy protects accounts, connected integrations, automation actions, and security reports.
OAuth
Integration access
Approval
Sensitive actions
June 3, 2026
Last updated
Security posture
Access, approvals, and reports stay explicit
Account
Firebase Authentication handles sign-in and sessions.
Integrations
Connected services use authorized provider access.
Actions
Sensitive sends and automation steps are approval-oriented.
Operating model
Security work stays explicit from sign-in to report.
Rearvy keeps the visible boundaries close to the workflow: accounts, connected services, approvals, and issue reporting.
02
Authorize
Integrations only access provider data after the relevant permission flow.
03
Review
Sensitive sends and automation steps are designed around visible approvals.
04
Report
Security reports route to a direct issue intake with reproduction details.
Account protection
Rearvy uses Firebase Authentication for account sign-in and session handling. Keep your account email secure, use strong passwords where password sign-in is enabled, and revoke access from devices you no longer trust.
Integration access
Connected services such as Google, Shopify, Meta, GitHub, and payment providers use authorization flows where available. Rearvy stores integration access only for the features you connect and lets you disconnect integrations from settings.
Automation safeguards
Workflows that send messages, use connected channels, control desktop actions, or perform sensitive operations are designed around approval gates and explicit user context instead of silent execution.
Reporting a security issue
If you believe you found a vulnerability, email myrearvy@gmail.com with a clear description, affected URL or feature, reproduction steps, and any relevant screenshots or logs. Do not access data that does not belong to you.