Sign in

Privacy

RSLVR is private infrastructure for persistent links, resources, scenarios, and controlled experiences. This page describes what the application stores, what it does not store, and how request infrastructure fits in.

Resolutions

A successful GET to a RSLVR identifier records only aggregate usage data:

By default, RSLVR does not persist IP addresses, user agents, referrers, device identifiers, or location as part of resolution analytics. There is no per-request visit log. HEAD requests, unknown keys, and inactive keys are not counted. Notes are noindex and are not listed in sitemap.xml.

Optional country analytics

An owner may enable country analytics for a project, covering Blocks within that project, or for an eligible Link target.

When enabled, a successful GET also increments an aggregate daily count keyed by Cloudflare’s two-letter country code.

RSLVR does not store raw IP addresses, user agents, exact timestamps associated with country observations, or per-request geolocation events.

Country buckets containing fewer than 5 resolutions in the selected range are grouped as Other.

Request processing

RSLVR runs on Cloudflare infrastructure. Handling an HTTP request necessarily involves Cloudflare processing network information such as IP addresses.

This is infrastructure-level request processing and is distinct from the application-level resolution data RSLVR persists. See Cloudflare’s privacy policy.

Accounts

Account creation is private and is not open public registration. Accounts store a username, an email address, a role (user or superuser), a password hash, session records, and hashed API-token representations with token metadata.

Email addresses are stored for account identity. They are currently not verified, and RSLVR does not send email. An account email can be changed in Settings with the current password.

A superuser may inspect account identity and operational metadata required for administration and support. They cannot impersonate another account, obtain another user’s active session secret, retrieve plaintext passwords, or retrieve API token secrets.

The admin session cookie is rslvr_session, is HTTP-only, and currently has a 30-day lifetime. Public resolutions do not require an authenticated account and do not set the admin session cookie.

Why account data is processed

Account and authentication data is processed to identify users, protect access to private RSLVR resources, maintain sessions, and operate the service securely.

The legal basis is the legitimate interest in securely operating this private service.

Data controller

RSLVR is operated by Didac Cristobal, who acts as the data controller for personal data stored directly by RSLVR.

Contact: contact@didac-crst.com

Retention

Account information is retained while the account exists.

Sessions expire according to their configured lifetime.

When an account is deleted, associated account, project, session, and API-token records are removed as described below.

Reserved identifiers and aggregate resolution history may remain after account deletion where required by RSLVR’s permanent-key model.

Account deletion

Deleting an account tombstones every link identifier owned by that account, then removes the user, their projects, sessions, and API tokens.

RSLVR identifiers remain permanently reserved and are detached from the deleted user. They never become available to a later account, including an account using the same username or email address.

Aggregate resolution counts already associated with those identifiers may remain as anonymous tombstone history.

Rights

You may request access to, correction of, or deletion of personal data associated with your account by contacting contact@didac-crst.com.

Where applicable, you may also request restriction of processing or exercise other rights available under data-protection law.

You may lodge a complaint with the CNIL.

Contact

Questions: contact@didac-crst.com.