Encryption
All traffic between you and RemMe is encrypted in transit using TLS 1.3. Older protocol versions are refused. All data stored on Panderose servers is encrypted at rest. Passwords are never stored in plain text.
Network
All communication with RemMe happens over HTTPS. Data services run on a private internal network and are not reachable from the internet. Access to production systems requires key-based authentication.
Data storage
Your data is stored exclusively on Panderose's own servers in Prescott, AZ. We do not replicate your data to AWS, GCP, or any third-party cloud provider. Backups are encrypted.
Authorization tokens for connected integrations are stored in encrypted form on Panderose servers. They are used only to sync your data and are never shared with third parties.
AI processing
Chat responses are generated using a third-party AI provider. When you send a message, we transmit only your query and the most relevant excerpts from your data, not your entire account. See our Privacy Policy for details on which provider we use and how your data is handled.
We implement commercially reasonable technical, administrative, and organizational measures designed to protect your data from loss, misuse, and unauthorized access. No internet transmission is ever fully secure, but we take the responsibility seriously.
Incident response
In the event of a confirmed security incident affecting user data, we will notify affected users by email within 72 hours of discovery, describe the nature of the incident, and outline steps taken to contain and remediate it.
Vulnerability disclosure
We welcome good-faith security research. If you discover a vulnerability, email [email protected] with a description. We will acknowledge receipt within one business day, work to remediate confirmed issues, and credit researchers who report responsibly.
Please do not disclose publicly until we have had a reasonable opportunity to fix the issue.