1. What GetRemma protects
GetRemma combines an account, mailbox services and a mobile VPN. Security is layered across login, registered installations, short-lived credentials, encrypted network transport, VPN configuration controls and provider access. No single control removes every risk.
2. VPN protocols and encryption boundary
The mobile VPN supports WireGuard and VLESS with REALITY. WireGuard uses modern authenticated encryption. In the selected VLESS configuration, REALITY protects transport to the VPN endpoint. Exact availability depends on mode and location.
The VPN protects traffic between your device and the selected GetRemma VPN endpoint. From that endpoint to a destination, protection depends on the destination protocol, such as HTTPS. A VPN does not hide information you give to a website, prevent account fingerprinting by that website, or guarantee anonymity.
3. VPN traffic and logs
VPN nodes must temporarily receive and forward packets while a connection is active. GetRemma does not use tunnel traffic for advertising and does not design the product to create a browsing-history profile or store tunnel content. Inspected VLESS nodes did not have destination access logging enabled, and WireGuard ordinarily does not create destination/content logs.
Infrastructure and security components can still record connection state, warnings or errors. Not every node has completed the same independent audit. We therefore do not make an absolute “zero logs” promise.
4. Service records and traffic counters
Account-linked control records can include the selected location, device public key, VPN assignment, configuration revision, connection attempt and revocation state. The backend keeps Xray byte counters and service aggregates used to operate access and capacity. WireGuard backend accounting is currently disabled. The mobile Home display shows local totals for the current connection and is not a speed test or browsing-history record.
5. Account and device security
Passwords are stored as one-way hashes rather than plaintext. Mobile sessions use short-lived access credentials and rotating or revocable session material. An installation identity and device proof bind protected mobile exchanges to a registered installation. Sensitive device material uses platform secure storage where supported. These controls reduce replay and credential theft risk but do not protect a compromised or unlocked device from every threat.
6. Website, API and mail transport
Websites and APIs use TLS in transit. Mail transport encryption depends on both mail servers and can fall back according to internet mail interoperability; end-to-end message encryption is not provided by default. Mailbox content is stored to provide the service and is accessible to the systems required for delivery, spam filtering, support and security under controlled access.
7. Support diagnostics
Support requests can be submitted without optional diagnostics. If a user chooses to attach diagnostics, the accepted mobile schema is limited to app, build, platform and engine versions, capability flags, bounded connection stages, failure codes, a validated location code and elapsed-time buckets. It excludes IP addresses, DNS queries and browsing destinations. Local diagnostic bundles and server payloads have bounded sizes and expiry described in the Privacy Policy.
8. Website measurement and preferences
Necessary storage keeps security, session, language and privacy choices. Detailed self-hosted Umami analytics is designed to run only after analytics consent. A separate aggregate candidate is designed to count only allowlisted pages, coarse sources, internal transitions, UTC hour and country without IP, visitor or session identifiers. It remains disabled pending approval of its legitimate-interest assessment, objection preference, GPC/DNT handling and retention controls.
9. Retention, deletion and backups
Different data has different operational or legal periods. The Privacy Policy contains the canonical retention table and identifies rows or logs without a fixed enforced expiry. Account deletion revokes access and removes account, mailbox, device and connected-service data through a multi-step process. It does not cancel an external subscription. Limited payment, security, legal and encrypted deletion-reconciliation records can remain, and deleted data may persist temporarily in protected backups until their rotation expires.
10. Infrastructure and service providers
GetRemma uses controlled infrastructure and external providers for hosting, VPN capacity, transactional mail, stores, payments and optional integrations. Self-hosted components such as Mailcow, Roundcube and Umami are software inside GetRemma-controlled hosting, not separate recipients. Ask us for details about providers relevant to a particular service or transfer.
11. Limits of security claims
We do not claim that GetRemma provides total anonymity, blocks every leak, operates only in RAM, has completed an independent no-logs audit, or encrypts all stored data with one universal method. We publish narrower claims that can be supported by current engineering evidence and update them when controls or evidence change.
12. Reporting a security issue
Report suspected vulnerabilities privately to support@getremma.com. Include a concise impact, affected URL or version and safe reproduction steps. Do not access customer data, disrupt service, publish credentials or assume a bug bounty or response deadline that has not been announced.