Trust
What a security or procurement review usually asks: who processes data for moqtap, where it is stored, how long it is kept, how to report a vulnerability, and how to get a data processing agreement. What a personal account holds is on the privacy page.
Who is responsible for what
- Insight telemetry, and traces, scenarios and notes in a team workspace: moqtap processes these for the customer, who decides what is collected and how long it is kept. The data processing agreement covers them.
- Accounts, sign-in records and the security log: moqtap is responsible for these itself, as described on the privacy page. The security log exists to protect the service; owners of a team workspace can read and export their workspace's part of it.
- Traces in a personal workspace: moqtap is responsible for these itself, and deletes them after 14 days. A trace can carry data from other parties to the recorded session, such as their identifiers and payloads, and the upload dialog says so before anything is sent. To report a trace that holds your data, email hello@moqtap.com with the share link; we take down traces that should not be there.
Sub-processors
| Company | What it does for moqtap | Where |
|---|---|---|
| Cloudflare, Inc. | Hosting for moqtap.com, app.moqtap.com, api.moqtap.com and the telemetry collector; databases and object storage; email delivery (Cloudflare Email Service); the Turnstile check on the email sign-in form at app.moqtap.com. | EU for telemetry, libraries and the security log; Western Europe for account data, with read copies worldwide |
| Hetzner Online GmbH | A server that builds analytics from Insight telemetry and keeps encrypted backups. | Helsinki, Finland |
| Proton AG | The mailbox that receives email sent to moqtap.com addresses, including messages from the contact form. | Switzerland |
| GitHub, Inc. | Sign in with GitHub. | United States |
| Google LLC | Sign in with Google. | United States |
GitHub and Google take part only when you choose to sign in with them. Nothing on moqtap.com loads a script from any of these companies.
Where data is stored
- Insight telemetry, team libraries, uploaded traces and the security log are stored in Cloudflare's EU jurisdiction, which keeps them in EU data centres. Analytics built from telemetry, and encrypted backups, are kept on a server in Helsinki, Finland.
- Account data — who you are, how you sign in, which workspaces you belong to — has its primary copy in Western Europe, with read-only copies in Cloudflare locations worldwide so that sign-in is fast wherever you are. Those copies are a transfer outside the EU, made under Cloudflare's certification to the EU–US Data Privacy Framework and the standard contractual clauses in moqtap's agreement with Cloudflare.
How long data is kept
| Insight telemetry | 30 days on the Free plan; within 14 days of deleting its project, workspace or account |
| Analytics built from telemetry | 90 days; within 14 days of deleting its project, workspace or account |
| Request counts at the Insight ingest address | 3 months |
| Traces in a team workspace | Set by the team; 90 days by default |
| Traces in a personal workspace | 14 days |
| Share links | 1 to 90 days, chosen when the link is made; revocable at any time; the record is deleted 30 days after expiry or revocation |
| Security log | 13 months for a team workspace; IP prefix and country removed after 90 days |
| Sessions | 7 days without use, 30 days at most |
| Sign-in codes and unfinished sign-ins | 1 day |
| A deleted account | 30 days, then removed |
| Backups | Up to 35 days; data deleted elsewhere can remain in a backup until it ages out |
Deleting a team workspace deletes its traces, scenarios, share links and telemetry. Data that has been deleted can remain in backups until they age out.
Deleting an Insight project, or the workspace or account that owns it, switches off its ingest keys within minutes and removes its telemetry within 14 days. Sessions and summaries go within hours, and stored uploads and analytics as soon as the processing server has caught up. Uploads stored together with other projects' data go about a week after they are processed, within 9 days of the project's last upload.
How the service handles your data
- There are no passwords. You sign in with GitHub, Google, or a one-time code sent by email.
- Every download of a trace from a library, and every export of a security log, is recorded in that workspace's security log first. If the record cannot be written, the download or export is refused.
- Traces are displayed by a viewer on its own domain, moqtapusercontent.com, which holds no sign-in. Its scripts cannot send data to any server, because its security policy allows no network connections, and it cannot read your other data. A malicious trace therefore has no session to take.
-
Files opened in the moqtrace inspector or with
moqtap inspectstay on your machine unless you share them.
Reporting a security issue
Email security@moqtap.com. Say what you found and how to reproduce it. We reply to every report, and ask that you give us a reasonable time to fix an issue before you publish it.
Data processing agreement
The data processing agreement is part of the Terms of Service and applies automatically to every customer. It covers Insight telemetry and team workspaces, and includes the standard contractual clauses for transfers outside the EU. If your procurement needs a signed copy, email hello@moqtap.com and we will send a countersigned PDF.