Dashboardly keeps optional analytics and advertising choices separate from the storage required to sign in and use the product. You can decide whether Dashboardly may measure usage and whether advertising tools may recognize your browser. Declining either option does not prevent you from creating an account, starting a trial, connecting a shop, or using your dashboard.
How your choices work
The cookie preferences panel on the Dashboardly website gives you separate choices for analytics and advertising measurement. Choosing analytics does not automatically enable advertising, and choosing advertising does not change the analytics setting. Until you make a choice, optional Google Ads, Meta, and affiliate measurement tools remain off.
Microsoft Clarity on the public website starts only after you enable Analytics in Privacy choices. It stays off when you have not made a choice or have declined Analytics. Allowing advertising alone does not enable Clarity. If you withdraw Analytics, Dashboardly stops Clarity and removes the Clarity cookies it can clear in your browser. Allowing Analytics again enables Clarity for your new choice.
If you allow advertising measurement, Dashboardly may use Google Ads and Meta advertising tools to remember that your browser visited a public Dashboardly page. This helps us measure campaigns and show more relevant follow-up advertising, such as an agency-focused message after you view the For Agencies page. Public page visits and high-intent pages such as Pricing may be used to create advertising audiences. Password, signup, payment, shop-connection, and other sensitive pages are excluded from Meta browser tracking.
Before Meta browser tracking starts, Dashboardly removes arbitrary query-string and page-fragment data from the browser address. Only Meta's opaque advertising click identifier may remain long enough to connect the visit to the ad click; email addresses, tokens, and other free-form URL values are not passed to the Meta runtime. Automatic Meta event discovery is disabled, so Dashboardly sends only the explicitly documented public-page events.
Meta browser tracking is also kept out of the authenticated Dashboardly product. Your Dashboard, Profit & Loss, shop data, billing settings, and other signed-in pages do not load the Meta Pixel. Confirmed milestones such as a trial start or paid activation are measured separately only when your advertising choice permits it.
For example, suppose you visit Pricing, allow advertising cookies, and leave without starting a trial. You may later see a Dashboardly reminder on Facebook or Instagram. If you decline advertising cookies, that visit is not added to a Dashboardly Meta website audience.
Essential signup source
Creating an account does not depend on optional analytics or advertising consent. During the signup session, Dashboardly may keep a short-lived, first-party source snapshot so it can distinguish a direct visit from a public website, campaign, partner, referral, or TikTok Shop App Store registration. The marketing channel and the signup entry point are kept as separate facts: a person can, for example, discover Dashboardly through a partner and still complete registration through the App Store.
This snapshot is limited to validated source, medium, campaign and ad-delivery labels, partner classification, timestamp, and a privacy-safe landing path. Search terms, creative-content values, advertising click IDs, raw referrer paths, URL query strings, email addresses, tokens, and the original path of a sensitive signup or authentication page are excluded before optional consent. When a supported advertising click parameter is present, Dashboardly may keep only its provider family (for example, Google paid search or Meta paid social) without retaining the identifier itself. Sensitive paths are replaced with a non-reversible product-page placeholder, and identifier-like path segments are redacted.
If you continue from the Dashboardly public website into the app, the signup link can carry the same protected source snapshot. It includes a source family, validated campaign and ad-delivery labels, and the queryless, redacted public page path. This lets Dashboardly distinguish an organic article visit from a generic website visit without placing an advertising click ID, search term, referrer path, or personal value in the handoff. For long public addresses, the protected path is preserved up to 500 characters so separate articles are not merged merely because their addresses share a long prefix.
Dashboardly may use these protected signup facts in combined acquisition reports so the team can compare channels, signup entry points, and landing pages. In a publicly served acquisition report, a detailed landing-page group is listed only when at least five signups share that group; smaller groups stay suppressed. This essential snapshot expires if signup is not completed and does not start Google, Meta, or affiliate browser tracking.
Free worksheets and the optional Operator Brief
The promotion worksheet on the public fee-calculator page works without an email address or newsletter subscription. Its inputs and downloadable CSV stay in your browser. They are not sent with the newsletter request.
If you allow analytics, Dashboardly can record that you compared offers, downloaded the worksheet CSV or selected the trial link. Example comparisons are distinguished from manually entered or edited inputs. These events contain no email address, worksheet amounts or financial results. Declining analytics does not prevent calculation, download or registration.
If you want the weekly TikTok Shop Operator Brief, complete the separate form and tick its unchecked permission box. The form records your email, your self-reported role, Shop market and approximate order range. Newsletter permission is separate from analytics and advertising choices. A saved request does not mean your email address has been verified or that a message has been sent.
After a saved request, Dashboardly uses an opaque, secure API cookie for up to seven days to connect that request with a later signup using the same email in the same browser. The cookie contains no email and cannot be read by page scripts. It is not placed in signup links. Dashboardly can then connect the signup with confirmed product and payment records; it does not treat the newsletter request as a trial or a payment. A different browser or email may leave these records unlinked.
An optional browser lead event is sent only after the request is saved and only to the measurement service you have allowed. It contains no email, worksheet inputs or financial results. The event describes a newsletter request, not a verified seller or paying customer. Declining the newsletter leaves the trial link available and does not change your cookie preferences.
Trials, subscriptions, and advertising measurement
When you have allowed advertising measurement and Dashboardly's server-side advertising connection is active, Dashboardly may report important account milestones to the advertising provider. These milestones include starting a trial or activating a paid subscription. They help Dashboardly understand whether an advertisement led to a meaningful product outcome rather than only a page visit.
Dashboardly sends these milestones from the confirmed product action. A trial is counted only after the trial actually starts, and a subscription is counted only after it becomes active. Page visits, registrations, connected shops, and booked calls may be measured separately, but they are not treated as paid subscriptions. This distinction prevents a single customer journey from being misread as several unique trials.
Advertising identifiers are used only after an advertising grant. Contact details used for matching are protected before they are sent to the advertising provider. Dashboardly does not place advertising credentials in your browser and does not include password, payment, or shop data in these advertising events.
Changing or withdrawing consent
Analytics choices between the website and app
Your analytics choice is shared between the Dashboardly website and app in the same browser. The app reads your latest website choice when it opens and when you return to it. An older choice saved only in the app does not override your current website preference.
Changing analytics permission in the app updates the shared browser choice. The website uses that choice when you open or refresh it. Your separate advertising and support choices are preserved. These preferences do not automatically transfer to another browser or device.
You can decline optional measurement before signing in. That choice applies immediately in your browser. After you sign in, Dashboardly reconciles the saved browser choice with your account and completes any pending withdrawal of optional shop-connection measurements. Declining does not require an account.
If your browser blocks saving the shared choice, the app still respects your explicit choice on the current page. Returning later may use the previously saved choice.
You can update your preferences from the cookie controls on the Dashboardly website. When you withdraw advertising consent, Dashboardly stops sending new browser advertising events and removes the Dashboardly Meta browser identifiers that it can clear. Pending advertising measurements for your account are also stopped where they have not already been delivered.
If you later allow advertising again, the new choice applies only to actions after that new permission. Dashboardly does not revive an older pending advertising event that belonged to a previous consent period.
Withdrawing consent does not remove information that an advertising provider was permitted to receive before your change. It prevents new optional marketing measurement from that point forward. Essential sign-in and security storage continues because it is required for the service to work.
If you clear all browser cookies, Dashboardly may ask for your preferences again the next time you visit. Your selection can also differ between browsers or devices until you make the same choice on each one.
Requesting account deletion
Open Delete your Dashboardly account to see how to request deletion, including when you cannot sign in. Email hello@dashboardly.io from your registered account address with the subject Account deletion request. Our team verifies ownership and the scope before processing a request. Never send your password.
An owner's request covers the account and connected shop data. A collaborator or agency team member requests deletion of their own account and access, without deleting another owner's shop or agency. Verified requests are processed within 30 days. Billing records may be kept for up to seven years for tax compliance, as described in the Privacy Policy.
Sending an email does not automatically sign you out or cancel a subscription. Cancel in Settings > Subscriptions, or ask support to help, to prevent a renewal while your request is being processed. You can contact support to withdraw your request before it is processed. Uninstalling the mobile app does not delete your account.
Common questions
Will declining advertising measurement prevent me from using Dashboardly? No. Signup, trial, subscription, shop connection, and product features continue to work.
Does allowing analytics also allow advertising? No. Analytics and advertising measurement are separate choices. Meta browser tracking requires the advertising choice.
Does Dashboardly track password or payment pages for advertising? No. Sensitive account, credential, payment, and connection pages are excluded from browser advertising tracking.
Why might I still see a Dashboardly advertisement after opting out? You may see a general advertisement that is not based on your Dashboardly website visit, or an audience may take time to refresh. Dashboardly stops sending new optional marketing signals after the withdrawal is applied.