What cookies are
Small files a site stores on your device.
Cookies are small data files placed on your computer or mobile device when you visit a site. They are used to make a site work, to make it work better, and to report on how it is used. Cookies set by the site you are visiting are first-party cookies; cookies set by anyone else are third-party cookies.
Similar technologies exist — local storage in your browser, and web beacons or tracking pixels in pages and email. Where we use them, they are covered by this policy too.
What Rbundle sets
The list itself, with what each one is for and how long it lasts.
- Sign-in and session
- Set by Rbundle through the service that signs you in, and named by that service rather than by us — the name changes with the project, so this policy describes it rather than naming a string it cannot keep true. Keeps you authenticated as you move around the application and protects form submissions. Stays on your device between visits so you do not have to sign in each time. It is cleared when you sign out, and expires after 400 days. This row covers both that cookie and a short-lived sign-in cookie while a link is in flight.
- rb_account
- Set by Rbundle. Remembers which of your accounts you are acting as, so the choice is not re-asked every time you sign in. Holds the account type only, never an identifier. Kept for 365 days.
- rb_attr
- Set by Rbundle. Records where a visit came from when the link that brought you carried a referral or campaign tag, so we can tell which sources bring people here. Written once, on that first arrival, and kept for 30 days.
- Browser storage (not a cookie)
- Held by your own browser, not sent to us. While you are signed out, a Request you are building is kept here for 24 hours so you do not lose it. It is cleared when you send the request, when it is restored into your account, after 24 hours, or when you clear your browser's data. Your Service Finder answers are kept here too, and are used in your browser to show how many services may suit you. They are cleared when you start building a request, when you sign in, after 24 hours, or when you clear your browser's data.
We do not serve advertising on the Marketplace, and we do not set advertising or cross-site tracking cookies on it.
CONFIRM before launch: publish the actual cookie table — each cookie's name, the party that sets it, its purpose and its lifetime. The prior policy promised a table and shipped without one.
Your control
No banner to dismiss. Your browser is the control.
Every cookie Rbundle sets is listed above, with what it is for and how long it lasts. There is no consent banner.
You can set your browser to refuse cookies. Every browser handles this differently; the help menu in Chrome, Edge, Firefox, Safari or Opera will explain how. If you refuse cookies you can still read the site, though parts of the application that depend on being signed in will not work.
CONFIRM before launch: Confirm the approach against the consent requirements of each jurisdiction the site is offered in, and confirm whether Global Privacy Control signals must be honoured.
Changes and contact
We will post changes here.
We may update this policy to reflect changes to the cookies we use or for operational, legal or regulatory reasons. The date at the top shows the current version. Questions: info@rbundle.com.