Cookie Policy
1. Introduction
This Cookie Policy explains how PRYZM uses cookies and similar technologies when you access or use the PRYZM website, web application, mobile application, and related services collectively referred to as the “Service.”
This Cookie Policy should be read together with the PRYZM Privacy Policy, Terms of Service, and other applicable notices.
Depending on how they are used, cookies and similar identifiers may contain or generate information relating to an identified or identifiable user. Where such information constitutes personal data, it is processed in accordance with the PRYZM Privacy Policy and applicable data protection law.
This Cookie Policy does not itself constitute consent to the use of optional cookies. Where consent is required, PRYZM will request it through a cookie banner, cookie settings interface, application setting, or another appropriate mechanism.
2. Who Is Responsible for the Use of Cookies
The personal data controller and operator of the Service is:
PRYZM Club LLC
[Full postal address]
USA
Email: support@pryzm.club
References in this Cookie Policy to “PRYZM,” “we,” “us,” or “our” mean the Controller identified above.
3. What Cookies Are
Cookies are small text files that a website places on a user’s device when the user visits the website or uses a web application.
Cookies may allow the Service to:
- recognize a browser or device;
- maintain an authenticated session;
- protect forms and accounts against unauthorized requests;
- remember language, accessibility, and interface preferences;
- maintain security and prevent fraud;
- understand whether features operate correctly;
- store a user’s cookie choices;
- perform analytics or personalization where such functionality has been enabled.
Cookies do not necessarily identify you by name. However, a cookie identifier may be associated with your account, IP address, device, browser, session, activity, or other information.
4. Similar Technologies
In addition to traditional browser cookies, PRYZM may use technologies that perform similar functions, including:
- local storage and session storage;
- device and application identifiers;
- authentication tokens;
- software development kits used in mobile applications;
- service workers and application caches;
- pixels or tags, where enabled;
- security and fraud-prevention identifiers;
- push-notification tokens;
- server-side logs containing IP addresses, request information, and technical identifiers.
References to “cookies” in this Policy include these similar technologies where appropriate.
5. Types of Cookies
5.1. First-Party and Third-Party Cookies
First-party cookies are placed directly by PRYZM on domains controlled by PRYZM.
Third-party cookies are placed by another organization when its services are used through or in connection with PRYZM. For example, an external authentication provider may use its own cookies when you choose to sign in through that provider.
5.2. Session and Persistent Cookies
Session cookies normally expire when you close your browser or when the relevant session ends.
Persistent cookies remain on your device for a specified period or until you delete them.
6. Cookie Categories Used by PRYZM
6.1. Strictly Necessary Cookies
Strictly necessary cookies are required for the Service to function securely and correctly. They cannot ordinarily be disabled through the PRYZM cookie settings interface because the Service may not operate without them.
They may be used to:
- maintain login and account sessions;
- authenticate users;
- protect forms against cross-site request forgery;
- protect accounts against unauthorized access;
- route requests between Service infrastructure components;
- apply security controls and rate limits;
- detect malicious, automated, or fraudulent activity;
- store cookie consent choices;
- provide features specifically requested by the user.
The legal basis for processing associated with these cookies may include performance of the user agreement, provision of a user-requested function, compliance with legal obligations, and protection of the legitimate interests and security of PRYZM and its users.
6.2. Preference and Functionality Cookies
Preference cookies allow PRYZM to remember choices that affect how the Service appears or operates.
They may remember:
- language selection;
- light or dark appearance;
- accessibility settings;
- content display preferences;
- notification preferences;
- layout and navigation choices;
- whether informational notices have been dismissed.
Depending on applicable law and the nature of the preference, these cookies may be used at your request or with your consent.
6.3. Analytics and Performance Cookies
Where enabled, analytics cookies help PRYZM understand how the Service is used and whether its features operate correctly.
They may be used to measure:
- page and feature usage;
- navigation paths;
- errors, crashes, and performance problems;
- approximate session duration;
- browser and device categories;
- aggregate Service reliability and engagement statistics.
Optional analytics cookies will not be activated before obtaining consent where consent is required by applicable law.
PRYZM should identify every analytics provider actually used by the Service in the cookie register below.
6.4. Personalization and Recommendation Technologies
PRYZM may personalize content or recommendations using information about your account, settings, interactions, follows, reactions, searches, and activity within the Service.
Not every recommendation technology relies on browser cookies. Recommendation systems may also use account-level and server-side information.
Where PRYZM uses technologies that collect, organize, and analyze information about user preferences for the purpose of providing recommendations, additional information about those technologies may be provided in a separate Recommendation Technologies Notice.
Optional personalization cookies will be controlled through the consent mechanism where required by applicable law.
6.5. Advertising and Marketing Cookies
PRYZM does not activate advertising or cross-service behavioral targeting cookies unless they are expressly identified in the current cookie register and, where required, the user has provided prior consent.
If advertising technologies are introduced, this Policy and the cookie settings interface will be updated to identify:
- the relevant provider;
- the purpose of the technology;
- the information collected;
- the applicable retention period;
- whether information is shared across services;
- how the user may refuse or withdraw consent.
7. PRYZM Cookie Register
The following table must reflect the cookies and similar technologies actually present in the production version of the Service. Cookie names or retention periods may differ where PRYZM has changed the relevant application settings.
| Name or technology | Provider | Category | Purpose | Typical duration |
|---|---|---|---|---|
sessionid | PRYZM | Strictly necessary | Maintains the user’s server-side session and, where applicable, authenticated state. | Browser session or the period configured by PRYZM. |
csrftoken | PRYZM | Strictly necessary | Helps protect forms and authenticated actions against cross-site request forgery. | Up to the period configured by PRYZM, commonly up to one year. |
cookie_consent or equivalent | PRYZM | Strictly necessary / preference | Records the cookie categories accepted or rejected by the user. | Up to 12 months, unless consent is changed or withdrawn earlier. |
django_language or equivalent | PRYZM | Preference | Stores the language selected by the user, where this feature is enabled. | Up to the period configured by PRYZM. |
| Appearance or interface preference identifier | PRYZM | Preference | Remembers appearance, layout, accessibility, or display choices. | Browser session or up to 12 months. |
| Security and rate-limiting identifiers | PRYZM or an identified infrastructure provider | Strictly necessary | Detects suspicious activity, prevents abuse, and protects Service availability. | Browser session or the period necessary for security purposes. |
| OAuth authentication cookies | Selected external authentication provider | Strictly necessary when the user selects external login | Allows the external provider to authenticate the user and return an authorization result to PRYZM. | Determined by the external provider. |
8. External Authentication Providers
PRYZM may allow users to register or sign in through an external authentication provider, such as Google.
When you choose an external authentication method, you may be redirected to a website or interface controlled by that provider. The provider may use its own cookies and process information in accordance with its own terms and privacy documentation.
PRYZM does not control cookies placed directly on a provider’s domain. Before using an external authentication method, you should review the provider’s cookie and privacy information:
Selecting external authentication is optional unless PRYZM expressly states otherwise. Where available, users may instead choose another registration or authentication method.
9. Legal Bases
Depending on the type of cookie and applicable law, PRYZM may process information associated with cookies on one or more of the following grounds:
- the user’s consent;
- the necessity of providing a function expressly requested by the user;
- performance of the agreement between PRYZM and the user;
- compliance with a legal obligation;
- protection of users, accounts, infrastructure, rights, and legitimate interests, provided that the user’s rights and freedoms are not overridden.
Strictly necessary cookies may be used without optional-cookie consent where they are required to provide, secure, or maintain the Service.
Analytics, advertising, and other optional cookies will be activated only on an appropriate legal basis and, where required, after consent has been obtained.
10. Cookie Consent
Where consent is required, PRYZM will provide sufficient information about the relevant cookie categories before optional cookies are enabled.
Consent must be:
- freely given;
- specific;
- informed;
- unambiguous;
- expressed through an affirmative action.
Optional-cookie consent will not be inferred solely from silence, inactivity, continued browsing, or a preselected checkbox where such a method does not constitute valid consent under applicable law.
Refusing optional cookies will not prevent access to the core Service. However, certain optional preferences or integrations may not function as intended.
11. How to Manage Cookies
11.1. PRYZM Cookie Settings
Where available, you may review or change your cookie choices through:
Withdrawing consent does not affect the lawfulness of processing that occurred before the withdrawal.
11.2. Browser Settings
Most browsers allow you to view, block, or delete cookies through their privacy or security settings.
Blocking all cookies may prevent authentication, account security, preference storage, and other important Service functions from working correctly.
11.3. Mobile Application Settings
Mobile operating systems may provide controls for application storage, advertising identifiers, permissions, notifications, and other device technologies.
Deleting application data or reinstalling the application may reset locally stored preferences and authentication information.
12. Do Not Track and Similar Browser Signals
Some browsers transmit “Do Not Track,” Global Privacy Control, or similar signals.
Because technical and legal standards for these signals may vary, PRYZM will respond to them where required by applicable law or where PRYZM has implemented support for the relevant signal.
Users should use the PRYZM cookie settings interface as the primary method for communicating cookie preferences.
13. Information Associated with Cookies
Depending on the relevant technology, PRYZM or an identified service provider may process:
- cookie and session identifiers;
- account identifiers;
- IP address;
- browser type and version;
- operating system and device information;
- language and time-zone settings;
- authentication and security status;
- date and time of requests;
- requested pages and application functions;
- referring and destination pages;
- error and performance information;
- consent and preference records;
- approximate location derived from an IP address;
- other technical information necessary to provide and protect the Service.
Precise geolocation obtained through device permissions is not treated as an ordinary browser cookie and is addressed separately in the PRYZM Privacy Policy and application permission interface.
14. Recipients and Service Providers
Information associated with cookies may be made available to persons who need it for the purposes described in this Policy, including:
- authorized PRYZM personnel;
- hosting and infrastructure providers;
- security and anti-abuse providers;
- authentication providers;
- analytics providers, where enabled;
- error-monitoring and technical-support providers;
- public authorities where disclosure is required or permitted by law.
Service providers may process information only for documented purposes and subject to applicable contractual, confidentiality, and security requirements.
PRYZM does not sell cookie-derived personal data.
15. International and Cross-Border Processing
Certain third-party integrations, including external authentication services, may involve the transfer or remote processing of information outside the Russian Federation or the user’s country of residence.
Where cross-border processing constitutes a transfer of personal data, PRYZM will take the measures required by applicable law before the transfer begins. Such measures may include:
- identifying the recipient and destination country;
- obtaining information about the recipient’s data-protection measures;
- determining an appropriate legal basis;
- providing required notices;
- submitting required regulatory notifications;
- implementing contractual, organizational, and technical safeguards.
Information about material cross-border processing should also be included in the PRYZM Privacy Policy.
16. Retention
Cookies are retained only for the period necessary for their stated purpose, subject to the applicable cookie configuration and legal requirements.
A cookie may expire:
- when the browser or application session ends;
- on a specified expiration date;
- when the user deletes it;
- when consent is withdrawn and the relevant identifier is removed;
- when PRYZM no longer requires it for its stated purpose.
Information previously received from a cookie may be retained separately where necessary for account security, fraud prevention, dispute resolution, legal compliance, or another lawful purpose.
17. Security
PRYZM applies legal, organizational, and technical measures designed to protect information associated with cookies against unauthorized access, alteration, disclosure, loss, or destruction.
Depending on the cookie and technical context, measures may include:
- HTTPS transmission;
Securecookie attributes;HttpOnlycookie attributes;SameSiterestrictions;- limited cookie scope and lifetime;
- access controls;
- session invalidation;
- security monitoring;
- fraud and abuse detection.
No internet service can guarantee absolute security. Users should protect their devices, browsers, passwords, and account access.
18. Adults Only
PRYZM is intended exclusively for persons aged 18 or older, or any higher minimum age required by applicable law.
PRYZM does not knowingly use cookies to create accounts for, profile, or target minors.
If PRYZM has reasonable grounds to believe that an account belongs to a person below the required age, PRYZM may restrict the account and take appropriate verification, deletion, preservation, or reporting measures.
19. Changes to This Cookie Policy
PRYZM may update this Cookie Policy to reflect:
- changes to the Service;
- new or removed cookies;
- changes to third-party providers;
- changes in law or regulatory guidance;
- security or operational developments.
The current version will be published through the Service with a revised “Last updated” date.
Where a change materially affects optional-cookie consent, PRYZM may ask users to review or renew their choices.
20. Contact Information
Questions or requests relating to this Cookie Policy may be sent to:
[Full legal name of the Controller]
[Full postal address]
Russian Federation
Email: support@pryzm.club
Requests concerning personal data rights should be submitted in accordance with the procedure described in the PRYZM Privacy Policy.