Privacy

Cookies

• Pages on moqtap.com set no cookies and load no third-party scripts.
• Signing in at app.moqtap.com sets one strictly necessary session cookie and one short-lived sign-in cookie; there are no analytics cookies anywhere.

The session cookie, __Host-mqt_s, keeps you signed in. It lasts until you sign out, until 7 days pass without you using it, or for at most 30 days. The sign-in cookie, __Host-mqt_x, exists only while you are signing in and is good for 10 minutes. Both are sent only to app.moqtap.com.

This site uses your browser's localStorage for two things: remembering whether you picked the light or dark theme, and the offline submission buffer described below. Both stay in your browser.

No tracking

No analytics, no tag manager, no advertising or social pixels, on this site or in the account pages. Every script this site runs is served from moqtap.com.

The moqtrace inspector

The tool at /tools/moqtrace-inspector shows .moqtrace capture files. A file you open from your machine, by choosing it or dropping it on the page, is read in your browser and not uploaded. The same holds for a capture that moqtap inspect opens for you: it goes from the command on your machine to the page in your browser.

The part of the page that reads the file runs in a frame from moqtapusercontent.com, a separate domain moqtap uses only for this. The file is handed to that frame inside your browser. The frame sets no cookies and holds no sign-in. Its scripts cannot send data to any server, because its security policy allows no network connections, and it cannot read any of your other data.

A capture leaves your machine only if you share it, which needs you to be signed in and to confirm the share.

What an account stores

• Your handle, display name, avatar URL and email address. These come from the way you first signed in.
• Each way you sign in: for GitHub or Google, the account ID that provider gives us; for sign-in by email, a keyed hash of the address. Provider access tokens are used once to read your profile and then discarded. There are no passwords.
• Each signed-in browser, command-line login and extension: when it signed in, the first part of its IP address (the /24 of an IPv4 address, the /48 of an IPv6 one), its country, and a browser or client name. You see the same list under Devices and can sign any of them out.
• The workspaces you belong to, your role in each, and invitations you send or receive.
• The traces you upload, and the share links you create for them.
• For a workspace on a paid plan: the plan, its billing period and payment status, and the Stripe customer ID that links the workspace to its billing record.
• A security log of sign-ins, sign-outs and account changes, with the same IP prefix and country.

We hold this to run your account, under our contract with you. For data a team puts in a team workspace, moqtap processes it on the team's behalf; the trust page covers that arrangement.

Who processes it

These companies process personal data for moqtap. The list is also on the trust page.

Cloudflare

Hosts moqtap.com, app.moqtap.com and api.moqtap.com, and stores account data, uploaded traces and the security log. Sends sign-in codes and invitations by email (Cloudflare Email Service). Runs the Turnstile check on the email sign-in form at app.moqtap.com.

Hetzner

Runs a server in Helsinki, Finland, that keeps encrypted backups of account data and builds analytics from Insight telemetry.

Proton

Hosts the mailbox that receives email sent to moqtap.com addresses, including messages from the contact form. Cloudflare forwards that mail to it.

Stripe

Takes payment for Pro, Team and Business through Link, Stripe's payment service. It collects your card and billing details and charges any tax. We never see the card number.

GitHub

Confirms who you are when you sign in with GitHub, and tells us your GitHub user ID, username, verified primary email address and whether two-factor authentication is on.

Google

Confirms who you are when you sign in with Google, and tells us your Google account ID, your verified email address and, if the account belongs to a Google Workspace organisation, its domain.

Data is never sold, and never shared for advertising.

How long it is kept

• Sign-in codes and unfinished sign-ins: deleted after a day.
• Sessions: deleted once they expire or you sign out.
• Traces in your personal workspace: 14 days. In a team workspace: as long as the team sets, 90 days unless it changes that.
• Share links: a link stops working when it expires, between 1 and 90 days after it is made, or when it is revoked. Its record is deleted 30 days after that.
• The security log: IP prefix and country are removed after 90 days. Entries about a team workspace are kept for 13 months, so its owners can review them.
• Insight telemetry: as long as the workspace's plan keeps it, 30 days on Free and Pro and 90 days on Team and Business. Hourly summaries and analytics built from it: 90 days on Free, Pro and Team, and 13 months on Business. After a move to a plan that keeps them for less time, older telemetry, hourly summaries and analytics are kept 30 more days, so they can be downloaded. Those of a deleted Insight project, workspace or account are removed within 14 days.
• A deleted account: removed 30 days after deletion. Backups are kept for up to 35 days, so a deleted account can remain in a backup for that long before it is gone everywhere.
• Interest form submissions, and the emails the contact form sends us: kept until you ask for them to be deleted.

Your copy, a correction, a deletion

Email hello@moqtap.com from the address on your account, or about a form you submitted, and ask. You can have a copy of everything held about you, have it corrected, or have it deleted, including the whole account.

In the account itself you can download a copy of your account data, change your email address, sign out any device, revoke share links, and delete your account, which is removed for good 30 days later. As a workspace owner you can delete the workspace and everything in it, and as an admin you can delete an Insight project and its telemetry. Workspace owners can also export the workspace's security log.

If you are unhappy with how your data is handled, tell us first. You can also complain to the UK Information Commissioner's Office at ico.org.uk, or to the data protection authority where you live.

The interest form on /ibc

When you submit that form, it collects:

• Your name and email. Both are required.
• Company, role, a relay or endpoint URL, and a free-text message. All optional.
• Which product interests you ticked.
• A source tag recording which surface you reached the form from — a printed QR code, say, rather than typing the URL.
• The consent checkbox, which has to be ticked before the form will submit.

Three more things are added on the server rather than typed by you: the time of submission, the country your request came from, and your browser's user-agent string.

The submission is stored in a Cloudflare D1 database and also sent to the moqtap team by email. If the consent box is not ticked the submission is refused outright and nothing is kept, so every record that exists is one where permission was given.

If the network drops as you submit

Conference wifi being what it is, the /ibc form holds your submission in your own browser (localStorage) if the network fails at the moment you send it, then sends it when a connection returns. While it is buffered it is on your device only. It is cleared once it has been sent.

The contact form on /contact

It collects your name, email, an optional company, an optional topic, and a message. That message is emailed to us and nothing else — the contact form is not stored in any database.