Privacy policy

The short version

We collect what you type into our contact and resource forms, plus analytics about how the site is used — cookies and advertising signals only if you agree to them, and an anonymous count of the visit either way. We never sell or share your details with anyone for their own purposes, and nothing you type into a form is used for advertising. Requesting a PDF sends that one resource; it does not subscribe you to marketing email. If you install our browser extension, the search term you type goes to a search-data provider and never to us. If you want your data gone, email us and it's gone.

Who we are

Daena Digital is a digital marketing studio operating from Canada, founded and run by Sima and Sadeq. For the purposes of Canadian privacy law, we are the organisation responsible for the personal information described here.

Questions, requests or complaints: info@daenadigital.com.

What we collect

When you fill in the contact form

Only what you choose to enter:

• Your name and email address
• Your company or act, and what kind of organisation it is
• Which services you're interested in
• Any key date, budget range or urgency you tell us
• Your message
• Whether you ticked the consent box

Alongside that, our server records the page you submitted from, your browser's user-agent string, and the country your request came from. That's used to understand context and to filter automated spam.

When you request a resource

We collect your name, email address and the resource you chose. Cloudflare also processes your IP address and counts requests so the form cannot be used to send unlimited email. We pass your name and email to Brevo to create a contact record if that address is new and send the requested download link. Existing contact details are left unchanged. That is fulfilment of your request, not permission to add you to a marketing list.

The PDF itself is stored by Sanity and the email contains its public Sanity download link. When you click it, Sanity receives the ordinary connection information needed to deliver a file, including your IP address. The link can be shared; the email form records interest but does not make the PDF private.

When you use the website redesign preview

When you use it, we send the public website address you submit to Cloudflare Browser Rendering, which loads the page with its own scripts running inside Cloudflare's isolated browser, and we read its visible text, navigation, images, reviews and contact details. Screenshots of the page and its visible markup go to an AI model run by Cloudflare Workers AI. Depending on the version running, that model either outlines the page's sections, with every word it returns checked against the page, or writes the design brief itself; when it writes the brief, we also read the text of up to four other public pages the homepage links to on the same site and give it that text too. We then send the page's text and the design brief — never the images — to Google's Stitch service, which returns a proposed page layout. Google processes that text under its own terms. Sample content the layout tool adds is listed beside the preview as content to replace.

The captured content, images, screenshots, findings and proposal are stored with Cloudflare. The working copy expires one hour after the job starts, and deletion is scheduled for that time. Failed runs discard captured material and retain only a failure summary until expiry. Platform delays can delay deletion, but do not extend access. Hashed network-address counters limit hourly use; a separate counter limits daily usage.

A finished redesign is also kept, with no expiry, at its own public link under /resources/redesigns/: the website address, the proposal, the two first-screen screenshots of the submitted page, and the report beside them, including the page text it was built from. Anyone holding the link can open it. The page asks search engines not to list it and is left out of our sitemap. It holds nothing about the person who ran it: no name, email or network address. To have one removed, contact us with its link and we will delete it.

The proposal is shown in an isolated frame. To render it, your browser loads one stylesheet script from cdn.tailwindcss.com and fonts from Google Fonts; those hosts see your IP address and the request, nothing more. The frame makes no request to the website you submitted and loads none of its scripts.

Clicking “Request a quote” saves the source address, preview reference and findings in your browser’s session storage so the contact form can read them. The form removes that saved handoff when it reads it, refuses handoffs older than an hour, and shows the text for you to review. Nothing is submitted until you send the contact form. That enquiry then follows the contact-record retention below; the private preview still expires, and its public link stays until removed.

When you simply visit

Our host, Cloudflare, processes your IP address in order to route the request and protect the site from attacks and bots.

Since 19 August 2026 the site also runs Google Tag Manager, which loads the measurement tags we've configured. Those record how the site is used — pages viewed, how you arrived, roughly where in the world you are, what kind of device you're on — and set cookies so that one visit can be told from the next. Loading them means your browser contacts Google, which reveals your IP address to them.

Since 31 August 2026 no analytics or advertising data is stored on your device unless you agree to it. A banner asks on your first visit. Until you answer, Google Tag Manager does not load. If you decline, the only thing this site stores or reads back is your answer, saved in your own browser; no analytics cookie or identifier is sent, so nothing can follow you between visits or between sites. You can erase that answer and any cookies already set through your browser's site-data settings.

Being precise about the part that is easy to overstate: declining does not stop your browser contacting Google at all. One file — Google's tag manager itself — is still downloaded, which reveals your IP address to them as any request to any server does. No analytics or advertising tag runs after it, and beyond reading your saved answer no analytics identifier is stored or read. Our setup is configured so that any measurement in that state would be anonymous and cookieless — but as of 31 August 2026 it isn't sending anything at all, which we checked in a real browser rather than assuming. If that changes, this page will say so. The rule that makes a consent banner necessary concerns storing information on your device and reading it back; the Google request does neither, while the IP address is ordinary processing described here rather than hidden. The cookie policy covers exactly what each button does.

What that measurement is not: it is not tied to your name or email, nothing you type into the contact form is sent to it, and we don't attempt to work out which individual person a visit belongs to.

One part of it is advertising rather than measurement, and we found that out late. Google Analytics has a feature called Google Signals, switched on by default, which sends two extra requests alongside the ordinary pageview — one to Google's ads-audience endpoint and one to stats.g.doubleclick.net, Google's advertising domain. Where a visitor is signed in to a Google account with ads personalisation enabled, it allows Google to associate the visit with that account, which is what makes remarketing audiences and cross-device reporting possible. We didn't add an advertising tag; the analytics we did add came with this switched on. We checked in a real browser on 28 August 2026 and corrected both this page and the cookie policy on 31 August. The feature stays switched on, and it is now behind the consent banner along with everything else — so it runs only for visitors who have said yes. The cookie policy covers it in full, including how to opt out through your Google account.

When you use one of the free tools

None of them asks for an email address, and none of them creates an account. Beyond that they divide in two, and the difference matters:

• The three ad cost calculators — Google, Facebook, TikTok. The arithmetic runs in your browser and the numbers never leave your device. Your margins and budgets are not sent to us, not stored, and not visible to us at any point. Close the tab and they're gone.
• The AI Search Readiness Audit — this one does reach our server, because it has to: you give it a website address and we fetch that site's public pages the way any search crawler would. It reads robots.txt, finds the sitemap and fetches up to ten pages, then computes the report from what came back.

What the audit keeps: the finished report — the scores, the summaries and the page addresses a finding refers to — for 24 hours, so that re-running the same site returns the result instead of crawling it again. A run that failed to score is discarded after five minutes. The fetched pages themselves are never written down anywhere. They exist in memory for the length of one run and go when it ends, so there is no copy of anybody's website sitting on our infrastructure afterwards.

We also count requests per visitor, so one person can't run the tools thousands of times and hand us somebody else's hosting bill. That count is keyed on your IP address, but the address is turned into an identifier on the way in and never stored as an address — so the counter can tell that some visitor is on their eleventh run this hour, and cannot tell us who, or which sites they looked at.

When you install the SERP Traffic browser extension

This one is not part of this website. It's a Chrome extension you choose to install, it runs in your browser on Google search pages, and it adds an estimated-traffic badge under each result. Everything in this section applies only if you install it; nothing here describes visitors to this site.

One thing leaves your browser: the search term you typed. It's sent to seodata.dev, a search-data provider, to look up that term's monthly search volume — which is half of the arithmetic behind the badge. That request goes from your browser straight to them.

It does not come to us. Our servers are not in the path, we never receive your searches, and we could not tell you what anybody has searched for even if we were asked. What seodata.dev receives is the search term and, as any server does, the IP address the request came from.

What is not sent, to them or to anyone: the results on the page, the pages you go on to visit, your browsing history, your bookmarks, the contents of any other tab, and anything identifying you. There is no account, no login, no analytics inside the extension and no tracking of how you use it.

What is kept on your own device, and nowhere else: the search volumes it has already looked up, held for a week so that repeating a search costs no request at all; your chosen country; and, if you add one, your own seodata.dev key. Removing the extension removes all of it. You can also clear the stored volumes from the extension's settings page at any time.

seodata.dev is a third party with its own terms and its own privacy practices, and we don't control what they do with a request once it reaches them. If that matters to you, the extension is optional and the website works without it.

When you email us

Mail sent to info@daenadigital.com is forwarded to our inbox. We keep correspondence for as long as it's useful, then delete it.

Why we collect it

To reply to you, to send a resource you requested, to prepare the free audit if you ask for one, and to keep a record of enquiries so nothing gets lost. Where we later send you anything commercial by email, we do so only with your consent, as Canada's anti-spam legislation requires — and every such message will have a working unsubscribe link.

We do not use anything you send us to train models or to enrich third-party datasets, and we do not use it to build advertising audiences. That last one now needs a companion sentence rather than standing alone: the Google Signals feature described above builds an advertising signal out of anonymous site visits, on Google's side, by default. It has nothing to do with your enquiry — the two never meet — but "we build no advertising audiences" would be doing quiet work for us if we left it unqualified.

Where it goes

We're a small team using ordinary tools. Your enquiry is stored with these providers:

This means your information may be stored or processed outside Canada, and may therefore be accessible to the courts and authorities of those countries. We've told you rather than burying it.

Beyond those providers, we share nothing. No data brokers, no advertising networks, no "partners".

What a page loads from elsewhere

One company: Google, for the tag manager, the analytics tags it loads and the two Google Signals requests described above. Everything else — fonts, images, stylesheets, scripts — comes from our own domain. The typefaces used to load from Google Fonts, which revealed your IP address to Google on every page; we moved them onto our own domain and that request is gone.

That count covers pages on this website. The SERP Traffic extension is separate software running in your own browser, it contacts a different company, and it is described in its own section above.

We keep that list short on purpose, and the site enforces it rather than trusting us to remember: it sends a policy naming the few addresses a script is allowed to be fetched from, so anything else is refused by your browser. That policy is also what was quietly refusing the Google Signals requests until 28 August, which is a fair illustration of both its value and its limits — it stopped something we hadn't agreed to, and it couldn't tell us it was doing so.

How long we keep it

• Enquiries that go nowhere — deleted within 24 months.
• Resource requests — kept in Brevo for up to 24 months, unless you ask us to delete them sooner.
• Client records — kept for the relationship, then as long as tax and accounting rules require.
• Anything you ask us to delete — deleted, unless we're legally required to keep it.

Your rights

Under Canadian privacy law you can ask us to:

• Tell you what personal information we hold about you
• Correct anything that's wrong
• Delete it
• Withdraw consent for us to contact you, at any time

Email info@daenadigital.com and we'll act within 30 days. There's no form to fill in and no charge.

If you're unhappy with how we've handled a request, you can complain to the Office of the Privacy Commissioner of Canada.

Security, honestly stated

The site is served only over HTTPS. Our form endpoint validates and rate-limits what it accepts, and service-provider keys are held server-side. The redesign preview limits requests per network address and per day. Accounts holding your data use strong, unique credentials.

What we won't claim: no setup is perfectly secure, and we rely on the providers above for the security of what they store. If we ever become aware of a breach affecting your information, we'll tell you and the regulator as the law requires.

Children

This is a business-to-business site and isn't directed at children. We don't knowingly collect information from anyone under 18.

Changes

If we change this policy we'll update the date at the top. If a change materially affects how we handle information you've already given us, we'll email you about it rather than quietly editing the page.