Data export

Download the personal data Norcube holds for your account — what's in the archive, what isn't, and how the 72-hour link works.

Under GDPR Articles 15 and 20 (access and portability), you can export the personal data attached to your account, self-service.

Request an export

Account → Data & privacy → Request export. The page sets expectations precisely: "We will build a ZIP archive containing your account profile and the list of organizations you're a member of, and email you a download link valid for 72 hours."

The request is queued and usually completes within minutes. The Past requests table tracks every request through its lifecycle — Queued → Building… → Ready (or Failed), and eventually Expired — with a Download button while ready.

What's in the archive

account.json — your profile fields and account metadata (never your password hash).
organizations.json — the organizations you're a member of.
README.txt — orientation notes.

What's deliberately not in it

Content you created inside organizations — translations, backup records, prompts, monitored domains — belongs to the organization, not to your personal account (the controller/processor split). The page says it plainly: "an org admin can request that data separately by emailing [email protected]."

For self-service org-data access, each product's API is fully paginated — LangSync, Backup, DomainRadar — so an org admin can also script an export.

The download link

Delivered by email when the export is ready, and available from the Download button (each click mints a fresh short-lived URL to the same archive).
Valid for 72 hours; the archive itself is deleted from storage about 7 days after creation, after which the request shows Expired — just request a new one.
The archive is encrypted at rest. But note the warning on the page: "The link doesn't require a Norcube login to use — anyone with the URL can download — so do not forward the email."

Behaviour and edge cases

An export is a snapshot as of when it was built; later changes need a new request.
A failed export (rare, infrastructure-side) shows Failed in the table — just request again; if it persists, contact [email protected].
Requests are permanent history — the table keeps expired and failed rows for your records.

Account deletion — export first if you want a copy; deletion is irreversible after the cooling-off.