Phaedra Solutions · Rubrily
Cookie Policy
Effective: 11 July 2026Last updated: 11 July 2026Version: 1.0
This page lists every cookie rubrily.com uses, what each one does, and how consent works. The short version: the site works with no optional cookies at all, analytics only run if you agree, and your browser’s Do Not Track setting is honored.
1. What cookies are
In short: Small files a site stores in your browser so it can remember things between pages and visits.
Cookies are small text files a website stores in your browser. Similar technologies — localStorage keys, pixels, device identifiers — do the same job, and this policy covers those too. Cookies split into two honest categories: essential ones the site cannot work without, and everything else, which needs your consent.
2. The cookies we set
In short: Today the marketing site works without any consent-required cookies. Analytics and attribution cookies only appear after you say yes.
Essential: the marketing site at rubrily.com currently needs no cookies to render — there is no login, cart or session here. One essential cookie appears if we need to remember your consent choice itself once the consent banner ships (you cannot consent-gate the memory of consent). The application atapp.rubrily.com sets the session cookies any authenticated product needs; they are covered by the product documentation and the Privacy Policy.
Consent-gated analytics and attribution — set only after you accept them in the consent banner:
| Cookie | Provider | Purpose | Lifetime |
|---|---|---|---|
| phaedra_attr | Rubrily (first-party) | First-touch campaign attribution: remembers the first page, referrer and UTM values that brought you here so a later signup can be attributed to the right campaign | 180 days |
| ph_* (e.g. ph_<project>_posthog) | PostHog (first-party cookie, US cloud) | Product analytics: page views and product events, device identifier, session continuity | Up to 12 months |
That is the whole list. No advertising cookies, no cross-site trackers, no data brokers.
3. Consent, and changing your mind
In short: Nothing optional runs before you say yes, and withdrawing is as easy as accepting.
When our consent banner ships, it works like this: on your first visit you get a plain choice — accept or decline analytics — and no analytics or attribution cookie is set before you accept. Declining is one click and never degrades the site. You can change your mind any time via the “Cookie settings” link in the footer; withdrawing consent stops future collection and removes our analytics cookies.
Until the banner ships, analytics stay off in production — this policy describes the implementation the site launches with, not an aspiration.
4. Browser controls, Do Not Track and GPC
In short: Your browser can block or clear cookies, and we treat DNT and GPC as a no.
Every modern browser lets you view, block and delete cookies — per-site or wholesale — in its privacy settings. Blocking our analytics cookies breaks nothing.
Our analytics configuration respects “Do Not Track”: if your browser sends DNT, analytics do not run for you regardless of banner state. We treat a Global Privacy Control (GPC) signal the same way — as a refusal of analytics (default — confirm at consent-banner implementation).
5. Changes and contact
In short: New cookie → new table row → new date at the top.
If we add, change or remove a cookie, this page and its table are updated first and the “last updated” date above changes. Questions: privacy@rubrily.com. For the bigger privacy picture, see the Privacy Policy.
Contact
Phaedra Solutions ([CONFIRM: exact registered legal form, e.g. “Phaedra Solutions (Private) Limited”]), Lahore, Pakistan · [CONFIRM: full registered company address]
Privacy: privacy@rubrily.com · Legal: legal@rubrily.com · General: contact@rubrily.com