Platform
Ask AI about Rimplo
Effective Date: August 19, 2026 · Rimplo, Inc.
This Cookie Policy explains how Rimplo, Inc. ("Rimplo," "we," "us," or "our") uses cookies and similar technologies on our website (rimplo.com) and our application (app.rimplo.com), and the choices available to you.
Where this policy says "cookies," it also covers browser storage — localStorage and sessionStorage — because these serve comparable purposes and merit the same disclosure. This policy supplements our Privacy Policy.
When you first visit, we ask whether you accept optional cookies. Until you choose, we set only what is strictly necessary to operate the Services.
Your decision is recorded in a cookie on .rimplo.com, which covers both our website and our application. You are therefore asked once rather than twice, and your choice carries with you when you move from our website into the product.
Select "Cookie Settings" in the consent banner to allow or refuse each optional category individually. To revisit a decision already made, clear the rimplo_consent cookie in your browser settings; you will be asked again on your next visit.
Declining optional cookies does not restrict your access to any part of Rimplo. No feature is withheld on the basis of this choice.
These are required for the Services to function. They are set regardless of your consent choice, because without them you could not sign in or maintain a session.
refresh_token, an HTTP-only, Secure cookie restricted to the /api/auth/refresh path and unreadable by JavaScript.
Keeps you signed in between visits without requiring you to re-enter your password.
7 days.
rimplo_consent.
Records your cookie choice so that we honour it and do not ask you repeatedly.
180 days.
account_access_token, user_access_token, available_accounts, user_profile, current_account_id, account_plan_tier, active_chat_id, stored in your browser’s session storage; and pre_checkout_account_id, stored in local storage.
Authenticate your requests, record which workspace you are working in and what it is entitled to, keep an assistant conversation open as you move between pages, and return you to the correct workspace after a payment.
Session storage is cleared when you close the tab. pre_checkout_account_id is removed once checkout completes.
__stripe_mid and __stripe_sid, set by Stripe when billing pages load.
Payment processing and fraud prevention. We do not store full payment card numbers.
As set by Stripe; per Stripe’s documentation, one year and thirty minutes respectively.
g_state, set by Google.
Supports authentication when you choose to sign in with your Google account.
As set by Google.
Set only if you accept the Analytics category. We use these to understand which features are used and where people encounter difficulty. We do not use them for advertising.
_ga and _ga_<identifier>.
Distinguishes visitors and sessions in order to produce aggregate usage statistics.
2 years.
Consent.
ph_<key>_posthog, served from our own domain.
Product analytics: which features are used, how people move between our website and our application, and where flows break down.
1 year.
Consent.
rimplo_checkout_value and rimplo_purchase_tracked:<identifier>, both in session storage.
Carries the plan price across the payment redirect so that a completed purchase can be measured, and prevents a single purchase being counted twice if you reload the confirmation page.
The first is deleted as soon as it is read; both are cleared when you close the tab.
Consent.
An internal user identifier, an internal workspace identifier, your plan tier, your role, and your email domain (for example, example.com).
Your name, your email address, your password, the contents of your conversations with the AI assistant, files you upload, or any of the business data you connect to Rimplo. Data belonging to your customers is never sent to analytics providers.
We do not record your screen. Session replay is disabled on both our website and our application.
We currently set no advertising cookies. Rimplo does not run advertising campaigns at this time, and no advertising tag is deployed on our website or our application.
Our consent banner offers this category because we may later measure whether a marketing campaign led to a sign-up. If that changes, Google advertising identifiers would be set only for people who accepted this category, and this policy will be updated before any such cookie is used.
Advertising identifiers are removed from any measurement request we send, and campaign information is passed in the page address rather than stored on your device.
Cookies beginning intercom-.
Operates the in-app support chat and preserves your conversation history with our support team.
Only while you are signed in to the application.
When you connect a data source such as HubSpot or Salesforce, authorisation takes place in a window on that provider’s own site. Any cookies set during that step belong to the provider and are governed by their policy, not ours. Rimplo sets no cookies during a connection flow.
theme, sidebar_open, and chat_sidebar_open, stored in local storage.
Remembers whether you prefer light or dark appearance and whether the sidebars are expanded.
These values never leave your browser and are shared with no one.
Google Analytics processes data on Google infrastructure, and PostHog processes data on its United States cloud, both of which involve transfers to the United States. Stripe and Intercom process data as described in their own privacy policies. Further detail on transfer mechanisms is set out in our Privacy Policy.
Browser "Do Not Track" signals have no consistent, agreed meaning across the industry, and we therefore do not act on them. Please use the consent banner instead, which records an unambiguous choice.
We will update this page whenever what we store on your device changes, and we will revise the Effective Date above. Where a change materially expands what we collect, we will ask for your consent again.
Questions about this Cookie Policy may be sent to privacy@rimplo.com.