Relmock

Privacy Policy

Last updated 20 October 2026

Relmock keeps what it needs to run your account and your mock APIs, nothing more. There are no ads, no analytics and no tracking cookies. You can export everything or delete your account at any time from the Account page.

Who we are

Relmock (relmock.com and app.relmock.com) is run by [operator name], [country]. For anything about your data, write to [contact email].

What we store

Your account

Your projects

Requests to your mock APIs

The Requests page shows each call made to your mock: method, path, query, request headers and body, response body, status and timing. Request headers can include the caller's IP address and browser details. Values whose name looks like a credential (for example Authorization, password or token) are replaced with [REDACTED] before they are stored.

Please don't send real personal data or real secrets to a mock. Relmock is built for test data.

In your browser

The app keeps your sign-in token and your theme choice in your browser's local storage. We set no advertising or analytics cookies. The landing page uses no cookies or trackers at all.

Technical logs

Our servers keep short-lived technical logs and error reports (time, address requested, status, error details) to keep the service running and secure.

Why we use it

Who processes it for us

We don't sell or share your data. These providers process it only to run Relmock:

Some of these providers may process data outside your country. Where the law requires it, we rely on their standard contractual safeguards.

How long we keep it

Your choices and rights

Security

Connections use HTTPS. Passwords and API keys are stored as hashes. Each account's data is separated in the database by row-level security, so one account cannot read another's. No system is perfectly secure, so please use a unique password.

Children

Relmock is a developer tool and is not meant for anyone under 16.

Changes

If this policy changes in a way that matters, we will update the date above and tell signed-in users in the app or by email before the change takes effect.