Cookie Policy
What you place on a visitor's device, and what it is for.
A disclosure explaining what cookies and similar tracking technologies a website uses, for what purpose (analytics, advertising, functionality), and what choices a visitor has. It usually works alongside a privacy policy rather than replacing it, and matters most for businesses running ad tracking or analytics on their site.
- Business days
- 1–5Business days
- Lawyer reviewed
- 100%Lawyer reviewed
- Surprise bills
- $0Surprise bills
What a Cookie Policy should include
What a cookie does here — in plain language, for a reader who is not technical.
Categories — strictly necessary, preference, analytics and advertising, kept separate because consent differs.
Third parties — every script that sets one, named, including analytics and ad platforms.
Duration — how long each category persists.
How to refuse or withdraw — the actual mechanism, not a pointer to browser settings alone.
How the notice is kept current — who checks it when the tag stack changes.
When you need one
When your site sets anything beyond what is strictly necessary to deliver it — analytics and advertising tags being the common triggers. It is also the document most likely to be out of date, because tags get added without anyone updating the notice.
How Ruby drafts it
Tell us what you need
Describe the agreement, your business context, and how fast you need it. A few smart questions, not a legal questionnaire. Your price and turnaround are confirmed before anything starts.
Ruby drafts it
Once pricing is confirmed a qualified Ruby lawyer is assigned to your file, and the first draft is built from your answers and real Canadian statute.
A licensed lawyer reviews every line
A lawyer licensed in Canada reviews and finalizes the document before it reaches you, and writes the plain-language summary that comes with it.
Signed, stored, and yours to revisit
You get the final agreement and its summary, stored so you can come back to it rather than hunting through email for the current version.
The fee is set before any of that starts. Hourly billing moves as scope does; a flat fee is one number, confirmed in writing, that doesn’t change after the work is done. See how Ruby prices agreements.
Or did you mean one of these?
These get confused with a Cookie Policy often enough to be worth ruling out before you buy the wrong document.
Questions people ask
Whether a banner is required, and what it must do, depends on what you set and on which privacy framework applies to you. The practical answer for most Canadian businesses running analytics and ad tags is that you need a clear disclosure and a real way to refuse.
It can. Keeping it separate mainly helps maintenance: the cookie list changes whenever marketing adds a tag, and the privacy policy usually does not.
Broadly, one the service cannot function without — session and security cookies, for instance. Analytics is generally not in that category even when it feels essential to the business.
Looking for the plain definition rather than the document? See Cookie Policy in the Ruby legal glossary.
This page is general information about Canadian business law and is not legal advice. Laws differ by province and change over time, and how they apply depends on your circumstances. For advice on your situation, speak with a lawyer licensed in your province.
Need a Cookie Policy?
Ruby drafts it for a flat $299 CAD, confirmed before any work begins, with a licensed Canadian lawyer on every document.