01About this policy
Copyright Record uses cookies and similar browser storage to operate its website and registration application. This policy explains what those technologies do, when they are used and how to control them. Contact privacy@copyrightrecord.com with questions, and read our Privacy Policy for information about personal data and your rights.
This policy concerns copyrightrecord.com and app.copyrightrecord.com. Payment pages hosted by Stripe are described separately below. Internal mail and administration tools may have additional service-specific authentication settings.
02Cookies and similar technologies
Cookies are small items stored by your browser and sent to the relevant website. Local storage remains until it is removed by the browser or application. Session storage belongs to a browser tab and is normally cleared when that tab's browsing session ends; browser session-restoration features can retain it longer.
These rules apply to similar storage technologies, not only files named cookies. Some data can identify an account or link activity to an individual. We do not treat such information as automatically anonymous.
03Necessary application storage
The registration application uses the following first-party technologies when the relevant service is requested:
| Name | Purpose | Provider / scope | Duration |
|---|---|---|---|
__Host-cr_refresh | Keeps an authenticated session available and supports secure session renewal. It is Secure, HttpOnly and SameSite=Strict. | Copyright Record; app.copyrightrecord.com | Up to 7 days per issue. Rotation can issue a replacement; logout clears it and server revocation may end access earlier. |
__Host-cr_csrf | Helps protect authenticated requests against cross-site request forgery. It is Secure and SameSite=Strict; application JavaScript can read it to submit the security check. | Copyright Record; app.copyrightrecord.com | Up to 7 days per issue, renewed or cleared with the browser session credentials. |
copyright-registration-draft in session storage | Carries the registration details entered by the customer between the registration form and payment review. It can include the work title, description and selected declarations; it is not a public record. | Copyright Record; application tab | Temporary tab-session storage; removed after successful processing by the application or when the browser clears the tab session. |
| In-memory authentication state | Holds short-lived access and interface state while the application is running. Current access credentials are not intentionally persisted in local storage. | Copyright Record; application page | Until the page is reloaded, closed or the state is cleared. |
These technologies support requested account, registration and security functions. Blocking or clearing them can sign you out or interrupt a draft. They do not authorise publication of an original document. The public certificate disclosure acknowledgement is separate from cookie settings and is not blanket consent for tracking.
04WordPress website and administration
Ordinary anonymous visits to the inspected public pages did not set WordPress login cookies. The separate WordPress login page uses wordpress_test_cookie to check whether the browser accepts cookies; the observed lifetime was the browser session.
When an authorised person signs in to WordPress, its core authentication and administration-preference cookies can be used. These can include wordpress_sec_*, wordpress_logged_in_*, wp-settings-* and wp-settings-time-*. They are for signed-in website administration rather than advertising. The inspected WordPress core sets saved administration preferences for one year. Without Remember Me, authentication cookies are normally browser-session cookies; with Remember Me, the core authentication window is normally 14 days, with an additional 12-hour browser-cookie grace period. Server settings and revocation can shorten access. These durations were checked in source code, not by logging in as an administrator or reading personal cookie values.
The unnecessary WordPress emoji-support session cache (wpEmojiSettingsSupports) has been disabled on the public website. Normal browser rendering of text and emoji remains available.
05Analytics, advertising and optional features
No analytics or advertising cookies were observed in fresh anonymous checks of the homepage, application sign-in, application registration and Privacy Policy pages. The inspected active website plugins did not include a dedicated analytics or advertising plugin. This is a scoped technical observation, not a guarantee about every third-party service or every future feature.
We do not ask you to accept optional tracking categories that are not currently enabled. If we introduce non-essential analytics, advertising or other storage requiring consent, it must remain off until you actively opt in through suitable controls. Refusing must be as straightforward as accepting, and consent must be withdrawable. Continuing to browse or accepting the Terms does not provide that consent.
06Externally hosted fonts and images
The inspected website/application pages request some fonts from Google Fonts (fonts.googleapis.com and fonts.gstatic.com), and the homepage requests some images from images.unsplash.com. Such requests transmit network information, such as an IP address, to the relevant provider even where no cookie is set. This is distinct from permission to store optional cookies. Applicable personal-data and international-transfer requirements still need to be met; see our Privacy Policy.
07Stripe payment pages
When you choose to pay, you are redirected to Stripe-hosted Checkout. Stripe may use its own cookies and similar technologies for payment functionality, security and fraud prevention, with names and lifetimes that depend on the service and environment. Read Stripe's Cookie Policy and the information on the payment page. Those provider controls do not give Copyright Record permission to introduce unrelated optional tracking on its website.
The inspected ordinary public pages did not load Stripe Checkout or Stripe tracking scripts before a customer chose the payment flow. This review did not submit a payment or inspect an authenticated Stripe checkout session.
08Your controls
You can inspect, block or delete cookies and site storage in your browser's privacy settings. Settings are usually available under site data or cookies. You can clear copyrightrecord.com and app.copyrightrecord.com separately. Private browsing may limit persistence but does not make network requests anonymous.
To end an application session, use Sign Out as well as any browser clearing you require. Clearing necessary cookies or a registration draft can interrupt your session or remove unsent details. Deleting cookies does not delete a registration, original document, NFT or blockchain record; contact privacy@copyrightrecord.com for data-rights requests.
There are currently no optional cookie categories to change through an Accept All / Reject All banner. Any future optional categories must have a genuine settings and withdrawal mechanism before activation.
09Legal framework and changes
Norwegian electronic communications rules require valid consent for storing or accessing information on a device unless a narrow exception applies, such as storage strictly necessary for a service the user explicitly requests. Personal-data processing also requires its own applicable GDPR basis. A necessary-cookie exception is not a general exemption from data-protection duties.
We will review this policy when the technologies or purposes change. For questions or requests, contact privacy@copyrightrecord.com. Our Privacy Policy and Terms and Conditions provide related information.