Transparency begins
with understanding.
Technology should explain itself. Cookies are small pieces of information that help websites remember preferences, maintain secure sessions, and improve the browsing experience.
They are not inherently good or bad. What matters is how they are used. Rheole believes users deserve complete transparency and meaningful control over these technologies.
What Are Cookies?
A cookie is a small text file that a website saves on your computer or mobile device when you visit the site. It enables the website to remember your actions and preferences (such as login, language, font size, and other display preferences) over a period of time.
First-party cookies are cookies set by the website you’re visiting. Only that website can read them. In addition, a website might potentially use external services, which also set their own cookies, known as third-party cookies.
Persistent cookies are saved on your computer and are not deleted automatically when you quit your browser, unlike a session cookie, which is deleted when you quit your browser.
Privacy Fact
Cookies themselves are simply plain text files. They cannot execute code, deliver viruses, or independently search your device for personal information.
Why Rheole Uses Cookies
We use strictly necessary technologies to make our site work. We do not use cookies for cross-site tracking or advertising profiling.
Maintaining secure sign-in sessions and verifying your identity.
Remembering your language and regional preferences.
Remembering interface preferences, such as light or dark mode.
Saving your explicit cookie consent choices across visits.
Improving website reliability by distributing traffic loads.
Measuring website performance to identify and resolve bottlenecks.
Supporting developer experiences within our API Reference and Sandbox.
Preventing abuse, fraud, and suspicious automated activity.
Cookie Categories
Essential Cookies
Can Disable: NoPurpose
These cookies are strictly necessary for the website to function securely and cannot be switched off in our systems.
Examples
Session identifiers, load balancing tokens, and security authenticators.
Impact if Disabled
Disabling these at the browser level will cause severe authentication failures and break core navigation functionality.
Performance Cookies
Can Disable: YesPurpose
These allow us to count visits and traffic sources so we can measure and improve the performance of our platform.
Examples
Anonymous load time metrics, error rate tracking, and page transition speeds.
Impact if Disabled
We will not know when you have visited our site, and we will not be able to monitor its performance to fix issues.
Functional Cookies
Can Disable: YesPurpose
These enable the website to provide enhanced functionality and personalization based on your previous interactions.
Examples
Language preferences, previously selected API environments, and dark mode toggles.
Impact if Disabled
Some or all of these services may not function properly, requiring you to manually set preferences on every visit.
Preference Cookies
Can Disable: YesPurpose
These specifically store your consent choices regarding other categories of cookies.
Examples
The 'rheole_consent_status' token.
Impact if Disabled
If deleted, you will be prompted to re-select your cookie preferences upon your next visit.
Security Cookies
Can Disable: NoPurpose
These help identify and prevent security risks, protecting user data from unauthorized access.
Examples
CSRF (Cross-Site Request Forgery) tokens and suspicious IP rate-limiting flags.
Impact if Disabled
These are considered essential. Removing them compromises the safety of your data.
Similar Technologies
While "cookies" is the standard term, websites rely on several underlying storage mechanisms built into modern browsers.
Local Storage
A web storage object that allows javascript sites and apps to store and access data right in the browser with no expiration date. We use this for non-sensitive UI state.
Session Storage
Similar to Local Storage, but data is cleared when the page session ends (when the browser tab is closed). We use this for temporary form data or multi-step wizard state.
Security Tokens
Cryptographic strings (like JSON Web Tokens) stored in memory or secure HTTP-only cookies to verify that a request is coming from an authenticated user.
Caching
Storing copies of frequently accessed files (like images or styles) locally on your device to drastically improve page load times on subsequent visits.
Cookie Lifecycle
Visit Website
Cookie Created
Purpose Fulfilled
Expiration
Third-Party Services
We minimize external dependencies. Where third-party services are used, they are bound by strict contractual obligations aligned with our Privacy Architecture.
Authentication Providers
Why it is used
To allow secure, federated login (e.g., 'Sign in with GitHub' or 'Sign in with Google') without requiring you to create a new password.
Information Processed
An anonymous session identifier and the public profile information you explicitly consent to share.
Infrastructure Analytics
Why it is used
To monitor the health, uptime, and latency of our global edge network.
Information Processed
Aggregated, anonymized performance metrics such as 'Time to First Byte' and regional server response times.
Security Services
Why it is used
To protect the platform against DDoS attacks, automated scraping, and credential stuffing.
Information Processed
IP addresses, browser signatures, and request velocity.
Your Choices
You have absolute control over non-essential cookies. You can accept or decline optional cookies at any time by updating your preferences in the footer. Furthermore, you can clear all cookies and site data directly through your browser's security settings.
Read our full Privacy Architecture →Frequently Asked Questions
Updates to this Policy
As our technology stack and regulatory environments evolve, we may update this policy. Significant changes will be accompanied by an update to the effective date. We encourage you to review this page periodically.
Contact our Privacy Team
If you have questions about our use of cookies or other technologies, please consult our Trust Center or contact us directly.