URD ATLAS
Account
This page describes how Urd Atlas handles account, billing, usage, and authenticated access data across the public website, subscriber dashboard, and API.
This Privacy Policy applies to Urd Atlas public pages, subscriber account pages, authenticated JSON delivery, and related support, billing, and operational workflows.
It covers the handling of account information, entitlement state, usage data, API access data, billing-related metadata, and technical service-operation metadata.
Urd Atlas has two distinct product surfaces: the public read-only website, which exposes descriptive pages and public API routes, and the subscriber system, which includes dashboard access, account state, API keys, and entitlement-gated file delivery.
Privacy handling may differ depending on whether a user is only visiting public pages or using subscriber functionality that requires authentication and account-linked access.
Depending on how you use the service, Urd Atlas may process:
Urd Atlas uses Clerk for authentication and account session handling. Authentication data is therefore also subject to Clerk's own product and privacy terms.
The site may process account-linked identifiers needed to determine whether a user has access to subscriber-only features such as dashboard routes, API keys, or authenticated file delivery.
Urd Atlas uses Stripe for billing, checkout, and subscription processing.
Payment card details are not stored directly by Urd Atlas. Billing-related metadata such as customer identifiers, subscription identifiers, plan information, and webhook status may be processed to operate the subscriber service.
Authenticated file delivery requires API keys. Urd Atlas may process API key metadata and request metadata needed for authentication and entitlement enforcement, security monitoring, rate limiting, abuse prevention, and subscriber support.
Secret API keys should only be displayed once at creation and should not be recoverable in plaintext afterward.
Urd Atlas may process limited operational and technical information necessary to operate the public website and API, such as route usage, availability signals, error states, freshness information, response timing, and delivery diagnostics.
The product is not designed to collect unnecessary personal content. Public blockchain analytics content is descriptive and does not require user profiling to function.
Public routes may expose dataset version, methodology version, source mode, freshness context, chain-specific lag, and canonical contract fields.
These fields are part of the product's transparency model and are intended to describe the published analytics state rather than identify end users.
Data may be processed to:
Urd Atlas may rely on third-party processors and infrastructure providers, including services used for authentication, billing, deployment, hosting, storage, and rate limiting.
Data is shared only to the extent reasonably necessary to provide or secure the service, or where required by law.
Subscriber account metadata, billing references, API key metadata, and operational logs may be retained for as long as reasonably necessary to provide the service, investigate misuse, maintain business records, or comply with legal obligations.
Urd Atlas uses route protection, entitlement checks, key status enforcement, and rate limiting as part of its security model.
No online system can guarantee absolute security, but the product is designed to reduce exposure of sensitive access credentials and restrict delivery to authorized scope.
Depending on applicable law, users may have rights related to access, correction, deletion, restriction, or objection in relation to their personal data.
Requests are handled according to the operator's applicable legal obligations and the service records required to operate, secure, and support the platform.
Terms governing use of the service are available at Terms of Service.
System health and freshness are documented at System Status.
Methodology and descriptive product boundaries are documented at Methodology, About, Glossary, and API Docs.