How we handle your data

What we collect in the hosted app

When you take a scorecard on app.dimensionkit.com or on a site that embeds one of our scorecards, we store the answers you submit, the contact details you provide (such as email address and any custom form fields the scorecard owner configured), the IP address of the submission, and a timestamp. This data is stored in a PostgreSQL database operated by us.

If you create an admin account to build scorecards, we also store your name, email address, and a hashed password.

How we use your data

We use submission data only to run the service: to score answers, to display the result, to deliver the result email, to operate anti-abuse protections such as IP rate limiting, and to make the data available to the scorecard owner. We do not sell your data. We do not share it with third parties except service providers acting on our behalf (see below), where the scorecard owner connects an AI assistant to their account (see below), or when required by law.

Connected AI assistants

An account owner can connect an AI assistant — any client that supports remote MCP servers, such as Claude or Cursor — to their DimensionKit account. Connecting is optional and nothing is connected by default. The owner approves the connection and its access level: read-only, or read and write.

Once connected, that client can call our tools on the owner’s behalf, and those tools return the data it asks for. That includes scorecard content and, for a connection with read access, submission data: the answers given, the per-dimension scores, and the respondent details collected by the form, such as email address and any custom fields. The data leaves DimensionKit for the client the owner connected and the AI provider behind it, where that provider’s own terms and privacy policy apply. We do not control how it is used or retained there.

Access lasts until it is revoked. Connected apps in the admin lists every assistant attached to the account, and disconnecting ends its access immediately. Removing the server inside the assistant only deletes that client’s copy of the token; to cut off access, disconnect it in DimensionKit.

Service providers

We run the service on infrastructure provided by Hetzner Online GmbH in Germany. Outbound email is delivered through an SMTP provider. Cloudflare is used in front of the application for DNS and edge protection. When a scorecard has Cloudflare Turnstile enabled, Turnstile receives request metadata for bot detection. Each of these providers processes only the data needed to perform their function and is bound by their own data processing terms.

Embedded scorecards

When a DimensionKit scorecard is embedded on a third-party website, that site is the data controller for the scorecard owner’s use of the form. We act as the processor running the form on their behalf. The scorecard owner is responsible for their own privacy notice covering how they use the submissions.

Cookies and analytics

The marketing site uses the self-hosted Umami analytics described above. Public scorecards do not load an analytics script or set analytics cookies. The app stores a small amount of local browser state (such as your selected theme) in localStorage. The admin uses a session cookie so you can stay signed in.

Service activity and embed counts

We record limited backend events to understand account activation and service reliability: account creation, scorecard creation, editing and publication, completed-response counts, and MCP tool names, outcome categories and execution times. Events contain internal account and scorecard identifiers and timestamps. They exclude respondent identifiers, contact details, answers, prompts, tool arguments, tool results and error-message text. Account-linked activity is not anonymous. We use it for our legitimate interests in understanding adoption and improving the service; you may object by contacting us.

When embed-load measurement is enabled, we count successful embedded scorecard page requests at Cloudflare, using a scorecard identifier and a count. These events do not contain visitor identifiers, IP addresses, user agents or referring URLs. Cloudflare still processes normal network request information to deliver and protect the service. We import daily aggregate estimates for the scorecard owner; these are not counts of unique people. Reloads and automated requests can be included.

Backend product events are retained for up to 180 days and MCP call details for up to 30 days, with daily cleanup. Imported daily embed totals are retained for up to 365 days, with daily cleanup. Deleting an account removes its product events; deleting a scorecard removes its imported embed totals. Cloudflare applies its own Analytics Engine retention period to edge events.

Data retention and deletion

Submission data is retained until it is deleted. Unpublishing a scorecard does not delete anything: it only takes the scorecard out of circulation, and the submissions already collected are kept and stay available to the scorecard owner. Deleting a scorecard deletes its submissions with it.

If you submitted a scorecard and want your data removed, contact the scorecard owner directly, or email us and we will route the request to them. We can also remove submission data from our systems on request.

Security

We use standard security measures including TLS in transit, hashed passwords, isolated containers, restricted server access, and standard operating system hardening. No system is perfectly secure and we cannot guarantee absolute security.

Your rights

If you are in the EU/EEA, the UK, or another jurisdiction with comparable laws, you have rights to access, correct, delete, or restrict the processing of your personal data, and to withdraw consent where processing is based on consent. Email rob@worbee.com to exercise any of these rights.