RegCatalog

Privacy notice

RegCatalog V0 is designed as a stateless browser tool.

Last updated: 23 August 2026. This notice explains the current public V0 of RegCatalog: a no-signup EU Data Act Product Data Notice generator, guide pages and a browser-only contact inquiry builder.

Summary

RegCatalog does not require an account and does not upload your draft Product Data Notice to a RegCatalog database. Draft persistence is local to your browser. If you clear your browser storage or reset the draft inside the generator, that local draft can be removed.

Do not enter secrets, passwords, private keys, security credentials, unpublished vulnerabilities or confidential technical details that should not appear in a draft product notice. The generator is meant for reviewable product-disclosure information, not sensitive operational secrets.

AreaStatusWhat it means

Generator drafts

Stored in your browser only

The V0 generator uses browser storage so your in-progress product notice can survive refreshes. RegCatalog does not provide an account or server-side draft database in V0.

Exported files

Created locally for you to download

JSON, CSV, HTML or notice outputs are generated from the fields you enter. You decide where to save, share or publish them.

Contact form submissions

Not collected

The contact page contains a browser-only inquiry builder. It prepares text for copying and does not transmit the message to RegCatalog.

Google Analytics

Optional after consent

RegCatalog uses Google Analytics 4 only after Analytics consent to understand page views, generator usage, notice exports and marketplace-output interest. It is not used to upload your generator draft fields, exported files or browser-only contact inquiry text to RegCatalog.

Portfolio early-access requests

Submitted through Tally by request

If you choose to join RegCatalog Portfolio early access, the Tally form collects the responses you submit and synchronizes them to a Google Sheet named RegCatalog Early Access. Product Data Notice generator contents are not submitted through the early-access form.

Accounts, billing and workspaces

Not present in V0

RegCatalog currently has no authentication, payment processing, organization workspace or hosted product catalogue database.

Local browser storage

The generator may use localStorage or similar browser storage for your draft. This storage is controlled by your browser and device. Other people with access to the same browser profile may be able to see the draft.

Portfolio early access

RegCatalog uses Tally to collect Portfolio early-access requests. Submitted responses are synchronized to Google Sheets and used to contact people who explicitly request early access, product follow-up or launch communication.

The Product Data Notice generator's contents are not submitted through the early-access form. The form receives only controlled attribution fields such as source, origin page, journey stage and recognized UTM parameters.

You can ask to stop receiving future early-access or launch communication by contacting RegCatalog through the contact page.

Analytics

RegCatalog uses Google Analytics 4 only after you accept Analytics cookies. Analytics helps measure aggregate website usage, generator starts, review-ready completion, notice exports and marketplace-output usage. The generator remains browser-local: draft Product Data Notice fields are not submitted to a RegCatalog backend for analytics processing and are not intentionally sent to Google Analytics.

You can reject or withdraw Analytics consent at any time through Cookie settings in the footer. Withdrawing Analytics stops future GA tracking and attempts to remove RegCatalog-domain _ga cookies without deleting Product Data Notice drafts.

Cookies and consent

Necessary browser storage is always available for site operation, remembering your cookie choice and preserving local generator functionality. Google Analytics is classified as optional Analytics, not necessary storage.

RegCatalog does not use advertising cookies, Google Ads tags, Google Signals, remarketing or ad personalization in the current public V0.

Read the Cookie Policy