Overview

RepliMap is designed with privacy at its core. Our CLI tool runs locally on your machine. Your AWS credentials, infrastructure data, and generated outputs never leave your environment. The only call the CLI makes to our servers is license activation, described below. See What RepliMap talks to for the complete list of network destinations.

What We Collect

We collect minimal data necessary to operate our service:

Account Information: Email address for license management and support communications.
License Activation: When you run replimap license activate, the CLI sends your license key, a machine identifier and the CLI version. The machine identifier is a truncated SHA-256 hash of your operating system, CPU architecture and the operating system's machine id. It does not include your MAC address, and it includes your hostname only in the rare case where the CLI cannot write its fallback id file. The hash is not salted, so it is a stable pseudonymous identifier for your machine, not anonymous data. The service also receives your IP address as part of the connection. No infrastructure data is transmitted.
Activation Records: For each activation request we store a log entry (license, machine identifier, CLI version, timestamp), and a machine record with first-seen and last-seen times that is used to enforce your plan's machine limit. The CLI does not send scan counts or feature usage.
Fields the Service Does Not Accept: The license service has no endpoints that accept AWS account IDs, region or VPC identifiers, snapshot, remediation or usage-event data, or device hostnames.
Payment Information: Processed securely by Stripe. We do not store credit card numbers.

What We Do NOT Collect

AWS credentials or access keys
Infrastructure configuration data
Generated Terraform code
IAM policies or security configurations
Any data from your AWS accounts

Data Security

RepliMap operates entirely on your local machine. Besides your own AWS API calls, the only network communication is with our license server, and only when you activate a license. This communication is encrypted using TLS and contains only your license key, a hashed machine identifier and the CLI version. Rate limiting counters keyed by IP address are kept for about two minutes. Operational logs may contain a truncated identifier (the prefix RM- plus at most four characters of a license key, or a shortened machine identifier) when abuse checks trigger.

Air-Gapped Environments

Online activation (all paid plans) needs one network call. The CLI then verifies the signed license locally and does not contact our servers again on its own. The signed license expires at the end of your current billing period plus an offline grace period (7 days on Pro, 14 days on Team, 30 days on Sovereign), after which you must activate again.

Sovereign customers can instead activate with no network call on the isolated host, from CLI 0.6.1. You run replimap license machine-id on that host and send us the id. We issue a signed license file for that machine on request, and you import it with replimap license activate --file <path>. The file is bound to one machine and expires on the date set when we issue it. We record each file we issue (see Retention).

Retention

A job runs automatically every day and deletes data on the schedule below. Nothing else is deleted automatically.

Records of devices you have removed are deleted 90 days after removal. Active devices are never removed automatically.
Activation and validation logs are kept for 90 days.
Device-change logs are kept for 90 days.
The log of offline licenses we issue is kept as an audit record.
Request-deduplication keys are kept for 7 days.
Payment-event identifiers are kept for 30 days.

Contact

For privacy-related questions, contact us at hello@replimap.com

Privacy Policy