Privacy policy

[ENTITY NAME] (trading as Keygredient), registered in [JURISDICTION OF INCORPORATION] under company number [COMPANY NUMBER], with its registered office at [REGISTERED OFFICE ADDRESS], is the controller of the personal data described here.

Privacy questions and rights requests go to [PRIVACY EMAIL]. No data protection officer has been appointed; requests are handled by the address above.

Most of this directory can be read without an account and without identifying yourself. What is collected depends on what you do.

If you only read pages. A page-view counter records that a page was viewed, once per viewer per page per day. It does not store your IP address: the address and your browser’s user-agent string are combined with a secret and hashed, and only the hash is kept. The hash cannot be reversed to recover the address, and it is what lets a supplier be told “412 people looked at this listing” rather than a meaningless hit count.

If you have an account. Your email address, name, the company you say you work for, your role, and a hash of your password (never the password itself). Plus whatever you create: saved items, projects, sample and quote requests, messages to suppliers, and your notification preferences.

If you claim or manage a company page. The claim itself, the evidence you submit with it, the edits you propose, and the documents you upload.

If you pay for a plan. Your subscription state, plan and invoice history. Card details are never seen by, sent to, or stored on this site — they go directly to Stripe.

If you consent to analytics. Google Analytics 4 sets cookies and records the pages you visit. It loads only after you accept, and nothing is sent to Google before then — see Cookies.

• To run your account and the things you ask it to do — signing in, saving a listing, sending a request to a supplier, showing your messages. Necessary to perform the contract you entered into by creating an account.
• To keep the directory accurate — reviewing supplier edits, handling reported inaccuracies, verifying a claim on a company page. Legitimate interest in publishing a catalogue that is correct.
• To tell suppliers how their listings perform, using the pseudonymous counter described above. Legitimate interest, balanced by the fact that no individual is identifiable in it.
• To take payment and issue invoices, where you buy a plan. Necessary to perform that contract, and to meet tax record-keeping obligations.
• To send service email — verification, password resets, decisions on something you submitted. Necessary to perform the contract.
• To measure how the site is used, through GA4. Consent, which you give or refuse in the banner and can change at any time.
• To keep the site secure and available — rate limiting, error reporting, and an audit log of internal actions. Legitimate interest in operating the service safely.

Your data is not sold, and it is not shared for anybody else’s advertising. It reaches the following processors because the service cannot run without them:

• Neon — the database everything is stored in.
• Cloudflare R2 — file storage for uploaded documents and images.
• Cloudflare — DNS, TLS and the CDN in front of the site.
• Resend — sending transactional email.
• Stripe — subscriptions and payments. Stripe is a controller in its own right for the card data it handles.
• Sentry — error reports, which can incidentally include the URL you were on and your account id when something breaks.
• Vercel — hosting, plus the page-view count and page-speed measurement described under Cookies. Neither sets a cookie or stores an identifier that can be traced back to you.
• Google Analytics — only if you have consented.

When you send a sample or quote request to a supplier, the supplier sees your name, your company and what you asked for. That is the point of sending it, and the form says so before you send.

• Account data — until you erase your account, and then only what is described under Erasure below.
• Page-view hashes — 24 months, then deleted. The hash is not reversible at any point.
• Messages and requests — kept while your account exists, because they are a record shared with a supplier who also relies on them.
• Invoices and payment records — as long as tax law requires, regardless of erasure.
• The internal audit log — retained, because it is the record of who changed what in the catalogue. Entries name the actor as they were at the time rather than linking to a live account.

You can ask for a copy of your data, ask for it to be corrected, ask for it to be erased, object to processing based on legitimate interest, and withdraw consent to analytics at any time. Withdrawing consent does not affect anything done before you withdrew it.

Two of these do not need a request at all. Your data in your account settings will export everything held about you as a file, and will erase your account, immediately and without anybody having to approve it.

Anything else, write to [PRIVACY EMAIL]. Requests are answered within 30 days. If you are not satisfied with the response you can complain to the supervisory authority in your country.

Erasing your account removes your name, email, password, profile, saved items, projects, watches and notification preferences. That is a real deletion, not a flag.

Some records survive, in a form that no longer identifies you, and it is worth being precise about which and why rather than claiming a clean sweep:

• Messages and requests you sent to a supplier stay, with your name replaced by “a former account”. They are the supplier’s record of a conversation as much as yours, and deleting one side of a thread would leave them with an unreadable one.
• Invoices stay, because tax law requires them to.
• Audit-log entries for actions you took as internal staff or as a supplier keep the label recorded at the time. That log is what makes the catalogue accountable.

The erasure screen states this before you confirm, so nothing here is a surprise after the fact.

Two cookies are set regardless of consent, because the site cannot work without them: a session cookie once you sign in, and a cookie recording your answer to the consent banner so you are not asked on every page.

Analytics cookies are set by Google Analytics 4, and only after you press accept. Until then the script is not on the page at all — not loaded and blocked, but genuinely absent, so no request is made to Google and nothing about your visit leaves this server. Refusing leaves it that way permanently.

Two measurements run for everyone and set no cookie at all: a count of page views, and how fast pages loaded. Both are collected by Vercel, and neither stores an identifier on your device or one that can be traced back to you across days — which is why they are not behind the banner. They record the page, not the person.

You can change your answer whenever you like from the link in the footer of every page.

Some processors above operate outside the country you are in, including in the United States. Where that happens the transfer relies on the European Commission’s standard contractual clauses or on an adequacy decision, as set out in each processor’s own terms.

The effective date at the top of this page changes when the text does, and only then. Where a change materially affects how your data is used, account holders are told by email rather than left to notice a new date.