datamogger

Privacy Policy

Last updated: October 19, 2026

DataMogger ("DataMogger", "we", "us", "our") operates the website datamogger.com and provides a web analytics service: a tracking script that website owners add to their sites, a dashboard and a REST API (together, the "Service"). This Privacy Policy explains what personal data we handle, why we handle it, who helps us, how long we keep it and what rights you have.

Please read it together with our Terms of Service. Words defined in the Terms have the same meaning here.

1. Summary

  • Our customers are website owners. They add the DataMogger script to their sites to understand how people find and use them.
  • For your DataMogger account, we decide how your personal data is used, so we are its "controller".
  • For data about people who visit our customers' websites, the website owner is the controller. We process that data for them, on their instructions, as their "processor".
  • We don't sell personal data, share it for advertising, fingerprint devices or track people across websites.
  • We don't store the IP addresses of our customers' website visitors.
  • Our servers and database are in the United States.
  • For questions or privacy requests, email support@datamogger.com.

2. Our two roles

Account data: we are the controller. When you sign up for and use DataMogger, we are responsible for the personal data in your account. Sections 3 and 4 explain what we collect and why.

Website visitor data: we are a processor. When a customer installs our script on their website, we collect data about that website's visitors on the customer's behalf. The customer decides whether to use DataMogger, which features to turn on and what extra data to send us. That makes the customer the controller, and we act only on their instructions. Section 5 explains what this data is.

If you visited a website that uses DataMogger and have a question about your data, please contact that website's owner. Section 12 explains how we can help.

3. Information we collect about account holders

Information you give us

  • Email address. Required to create an account and to sign in.
  • Your websites and settings. The websites you add (name, domain, time zone and currency) and what you set up for them, such as goals, funnels, segments, notes, alerts, exclusion rules, API keys, payment webhook secrets and, if you connect Cloudflare, a read-only Cloudflare API token. Exclusion rules can include IP addresses you choose to exclude, such as your own. We store API keys only as hashes. When you connect a payment provider with an API key or by signing in to it, we use that access once, to create the webhook it needs, and don't keep it.
  • Billing. When you buy a plan, you pay Paddle.com, our reseller and the Merchant of Record for all our orders. Paddle collects your name, billing address, payment details and any tax ID under its own privacy policy. From Paddle we receive your Paddle customer and subscription IDs and your plan, its status and billing dates, which we use to give you your plan's limits. We never see your full card details.
  • Team members. If you invite someone to one of your websites, we store their email address to send the invitation and, once they accept, to give them access. People who accept sign in with their own account.
  • Messages. If you email us, we receive your email address and your message, and we use them to reply.

Signing in

  • Email code. We email you a 6-digit sign-in code. We store only a keyed hash of the code, never the code itself, and the code expires after 10 minutes. With each code request we also store the IP address and browser user agent it came from, so that we can detect and limit abuse. These records are deleted automatically after 30 days.
  • Google sign-in. If you choose to sign in with Google, we ask Google only for your basic profile and email address. We store your email address and Google's identifier for your account, and nothing else from Google.
  • Staying signed in. After you sign in, your browser keeps a session token in its local storage (not in a cookie).

Abuse prevention

  • We may block sign-ups from disposable email domains. When someone tries to sign in with a disposable address, we record the email address, IP address and browser user agent of the attempt. These records are deleted automatically after 30 days.
  • Our sign-in form uses Cloudflare Turnstile to check that a person, not a bot, is using it. To run this check, Cloudflare processes your IP address and information about your browser.
  • These checks are automated. If you think you were blocked by mistake, email us.

Using datamogger.com

  • When you visit datamogger.com, our servers and Cloudflare receive standard technical information, such as your IP address, browser user agent and the page requested, in order to deliver the site and protect it from attacks.
  • The dashboard shows website icons (favicons) that it loads from Google's favicon service. Your browser requests each icon directly from Google, so Google receives your IP address, your browser information and the domain whose icon is shown, such as the websites you track and the websites that send them traffic.
  • We don't use advertising cookies or third-party analytics on datamogger.com. We measure visits to it with DataMogger itself (see Section 6).
  • Error reports: when something fails in the Service, such as a page of the dashboard crashing in your browser or a payment notification that couldn't be recorded, we record what failed and when, with your user ID and the website's ID where they apply. For errors in your browser we also record the page address and your browser user agent. We use these reports only to find and fix problems, and we send a short alert with the error, the user ID and the website ID (never an email address) to our team through Telegram.

Emails we send

We send only service emails: sign-in codes, the weekly reports and alerts you choose (traffic spikes, tracking stopped, new customers, goals), team invitations you send, reminders about your trial, your plan's usage and any upcoming condensing or deletion of your data, and notices about your account or the Service (for example, changes to our Terms, this policy or pricing). We don't send marketing email.

4. How we use account information

We use account information to:

  • create your account, sign you in and keep your account secure;
  • provide the Service, including your dashboard, the API and the goal alerts you set up;
  • run your trial and your plan, including its limits, together with Paddle;
  • send you service emails;
  • understand how datamogger.com and the Service are used, so we can improve them (for example, which pages and features people use);
  • prevent and investigate fraud, abuse and security incidents, and enforce our Terms;
  • reply to your messages and requests; and
  • meet our legal obligations.

We don't sell account information, share it for advertising or use it for marketing.

Legal bases (EEA and UK)

If you are in the European Economic Area or the United Kingdom, we rely on these legal bases:

  • Contract: to create and run your account, sign you in, provide the Service and send service emails.
  • Legitimate interests: to keep the Service secure and free of abuse (for example, sign-in records, disposable-address checks, bot checks and rate limiting), to show website icons in the dashboard and to enforce our Terms, where these interests are not overridden by your rights. You can object to this processing (see Section 13).
  • Legal obligation: to respond to lawful requests and meet other legal requirements.

5. Data we process for customers about their website visitors

This section describes the data the Service processes when someone visits a website that uses DataMogger. We process it for the website owner, who is responsible for it.

Collected automatically by the script

  • Pages: the address of each page viewed (hostname and path, plus the part after # if the website owner turns that on) and when each page was viewed.
  • Traffic source: the referring website, and these campaign parameters from the page address: utm_source, utm_medium, utm_campaign, utm_term, utm_content, ref and via. We discard the rest of the query string.
  • Device: browser, operating system and device type, which we work out from the browser's user agent string (we don't keep the full string), and the screen (browser window) width.
  • Approximate location: country, region, city and approximate coordinates. Cloudflare derives these from the visitor's IP address at the edge of its network, before the request reaches our servers.
  • Outbound links: the address of any link to another website that the visitor clicks.
  • Random identifiers: a visitor ID and a session ID, stored in first-party cookies (see Section 6). They let the website owner count unique visitors, group pageviews into visits and follow a visitor's journey through that website.

On the Free plan

When the website's owner is on our Free plan, we don't store each visit. The script sends the same information, and we use it only to add to hourly and daily totals for the website (counts of visits, visitors, pageviews, events and time on site, by page, traffic source, campaign, country, device, browser and operating system, and counts of goal completions), then discard it. To count unique visitors, new visits and time on site without storing visits, our servers keep each visit's random IDs, start time and traffic source in memory for up to 35 minutes. For websites that record payments, we also keep a short reference to each visit (its random visitor and session IDs, start time and traffic source) for 30 days, so that a payment made after the visit can be credited to its traffic source.

IP addresses

We don't store visitors' IP addresses. Our servers use them only briefly, in memory, to limit excessive traffic, to apply any IP exclusion rules the website owner has set, to drop traffic from datacenter networks when the owner turns on attack mode, and, on websites that track without cookies, to work out the daily visitor hash described in Section 6.

Sent by the website owner, if they choose

  • Goals: actions the owner wants to count, such as sign-ups or downloads, with any properties the owner attaches.
  • Identity: a user ID, name, profile image and custom fields that the owner attaches to a visitor, for example after the visitor logs in to the owner's site.
  • Payments: payment records from the owner's billing provider or online store, sent through webhooks from Stripe, Paddle, Lemon Squeezy, Polar, Creem, Dodo Payments, Shopify, WooCommerce or Gumroad, or through our payments API. They include the amount, currency, transaction ID and customer ID, whether the payment was a renewal or a refund, and optionally the customer's email address, name, user ID and product. We use them to show which visits and traffic sources led to revenue. So that a payment can be credited to the visit, the script passes the visitor and session IDs to the checkout: it adds them to Stripe Payment Links, Buy Buttons and Pricing Tables (as a client reference ID), to checkouts opened with Paddle.js (as custom data), to links to some hosted checkouts (Lemon Squeezy, Creem, Polar, Dodo Payments and Gumroad), and on Shopify stores it saves them on the shopping cart as hidden attributes, which the order keeps. With our WordPress plugin on a WooCommerce store, they are also saved on each order in the owner's store. When a visitor arrives on a checkout's confirmation page, the script also reports the checkout reference from the page address (for example, a Stripe Checkout session ID, or a WooCommerce order key, which we keep only as a one-way hash). On Shopify, the owner can add our pixel instead of, or as well as, the script: it counts visits on store and checkout pages in the same way and reports each order's ID and amount from the order confirmation page.

What the website owner sees

The owner's dashboard and API show reports on visits, traffic sources, pages, locations, devices, goals, funnels and revenue. They also show individual visitors: a visitor's journey through the website, and an estimate of how likely that visitor is to become a paying customer, calculated only from that website's own data. On the Free plan, the dashboard shows only totals.

A website owner can also share a read-only view of the website's statistics through a link (which the owner can protect with a password and which expires when the owner chooses) or through badges, images showing visitor or revenue totals. These show only totals and breakdowns, never an individual visitor, and revenue only if the owner chooses to share it.

Peer benchmarks

The Service shows each website owner how their website compares with similar websites, for example its monthly growth, bounce rate or revenue per visitor against websites of the same kind and size. To do this, we combine the totals the Service counts for each website (such as the number of visits, visitors and events by traffic channel, and the number and amount of new payments) into anonymous statistics across websites. These totals contain no personal data: no visitor IDs, IP addresses, identity or payment details. A statistic is shown only when it comes from at least 10 websites; it's rounded to two significant digits, and we never show a minimum or a maximum, or name or identify a website, a website owner or a visitor. A website owner can mark what kind of business their website is, to be compared with similar ones. When a website is deleted, or its data is, its daily totals are first added to network-wide totals that name no website, so the statistics keep their history; anything shown from those totals alone comes from at least 10 websites.

If the owner sets up goal alerts, we email the owner when a goal is completed, with details of that visit, such as approximate location, traffic source, page, goal properties and the visitor's name if the owner has attached one.

What we don't do

  • We don't fingerprint devices.
  • We don't track people across websites. Each website's data is kept separate, and a visitor ID on one website is not linked to any other website.
  • We don't sell visitor data or share it for advertising.
  • Only the website's owner, and anyone the owner gives an API key to, can see a website's data. Other customers see only anonymous statistics across at least 10 websites (see "Peer benchmarks"). We access a website's data only when needed to run, secure or support the Service, or when the law requires it.

Controls for website owners

Website owners can exclude traffic by page path, IP address, country or hostname; delete a website and all its data at any time; delete their account; and use the API to remove the identity details attached to a person. After identity details are removed, that person's visits remain only as records linked to a random visitor ID.

Choices for visitors

  • Opt out of a website: open any page of the website with ?dm_ignore=1 added to the address (for example, https://example.com/?dm_ignore=1). The script saves an opt-out flag in that browser's local storage and stops counting visits from that browser on that website. Using ?dm_ignore=0 turns counting back on.
  • Cookies: deleting the DataMogger cookies resets the visitor ID; blocking them stops visits from being linked together.
  • Browser signals: the script does not currently respond to Do Not Track or Global Privacy Control signals. Website owners can choose not to load it for visitors who send them.

6. Cookies and similar technologies

On websites that use DataMogger

  • dm_vid: a first-party cookie holding a random visitor ID, set on the website's own domain. It expires 400 days after the visitor's most recent visit, and some browsers delete it sooner.
  • dm_sid: a first-party cookie holding a random session ID, set on the website's own domain. It expires after 30 minutes without activity.
  • dm_st_…: a first-party cookie (one per website) holding the time of this browser's last event on that website, the start of its session ID and how many events that visit has had. It lets us count new visits, engaged visits and unique visitors without storing each visit. It expires 400 days after the visitor's most recent visit.
  • dm_ignore: a local storage entry, saved only when a visitor opts out (see Section 5).
  • dm_cart: on Shopify stores only, a session storage entry noting that the current shopping cart already carries the visit's IDs, so they are saved once. The browser deletes it when the tab is closed.
  • dm_js: on Shopify stores that use both the script and our pixel, a first-party cookie telling the pixel that the script already counts the store's pages, so nothing is counted twice. It expires after 30 minutes without activity.

These cookies belong to the website being visited. Other websites can't read them, and we don't use them to follow people from one website to another.

A website owner can instead choose cookieless tracking. Then the script stores nothing on the visitor's device: no cookies, local storage or session storage. Our servers tell visits apart with a one-way hash of the visitor's IP address and browser (user agent), the website, and a secret that changes every day and is then deleted. The same visitor gets a different hash every day, so visits on different days can't be linked, and the hash can't be turned back into an IP address.

In the EU, the UK and some other places, the law may require the website owner to get visitors' consent before these cookies are set. That is the website owner's responsibility. One way to meet it is to load the DataMogger script only after the visitor agrees.

On datamogger.com

  • Session token (local storage): keeps you signed in until you sign out or the session expires.
  • Theme (local storage): remembers your choice of light or dark theme.
  • Cloudflare Turnstile: on the sign-in form, Cloudflare may store short-lived tokens or cookies that its bot check needs.
  • Paddle checkout: when you open the checkout to buy or change a plan, Paddle's script runs on the page and may store the cookies or similar data its checkout needs (see Paddle's privacy policy).
  • DataMogger analytics: we measure visits to datamogger.com, including the dashboard, with DataMogger itself. It sets the same first-party cookies as on our customers' websites (dm_vid, dm_sid and dm_st_…, described above), on datamogger.com only, and the data stays with us. When you're signed in, it links those visits to your account ID (nothing else), so we can see which channels bring sign-ups and customers, and it notes in local storage that a new account's sign-up was counted, so it's counted once.
  • Your cookie choice: if you visit from the EU, the EEA or the UK, we ask first, and DataMogger analytics runs only after you click "Accept all". We tell where you are from your browser's time zone and the country Cloudflare sees for your connection, and we don't store either. Elsewhere, DataMogger analytics runs from your first visit. Wherever you are, "Cookie settings" at the bottom of our pages lets you change your answer: "Reject all" stops DataMogger analytics on datamogger.com and deletes its cookies. We keep your answer for 12 months in a first-party cookie, cc_cookie.

We don't use cookies for advertising, or any other company's analytics, on datamogger.com.

7. AI crawler data

Website owners can send us visits from AI crawlers and other bots through our API, for example from their own server or CDN. For each visit we receive the crawler's user agent string and the page path, and we record the crawler's name and company, the path and the time. Owners whose site runs through Cloudflare can instead connect it with a read-only token: every 15 minutes we read, from Cloudflare's analytics, how many requests known crawlers made, by user agent, page path, host and hour, and store the same records with their counts. These records describe automated software, not people, and contain no personal data.

8. Who we share data with

Service providers (subprocessors)

These providers help us run the Service. They process data on our behalf under contractual obligations and may not use it for their own purposes.

  • Akamai (Linode): servers and database hosting in Newark, New Jersey, USA. Stores account data and website visitor data.
  • Cloudflare: DNS, content delivery, the secure network tunnel to our servers, bot protection (Turnstile) and approximate location from IP addresses. All requests to datamogger.com, the script and the API pass through Cloudflare.
  • Cloudflare R2: storage for our encrypted database backups.
  • Resend: delivers our emails. It receives each recipient's email address and the content of the email, which for goal alerts can include visit details.
  • Telegram: delivers error alerts to our team's phones. Each alert contains the error text and the user and website IDs involved, never an email address.
  • Google (Gmail): hosts our support mailbox. Cloudflare Email Routing forwards messages sent to support@datamogger.com there, so Google receives the emails you send us.
  • Paddle: our reseller and Merchant of Record. It sells you your plan and handles payments, taxes, invoices and refunds. It receives your email address and what you enter at checkout, and acts as a controller of that data under its own privacy policy.

We will update this list before a new provider starts processing personal data for us, and we will notify customers as described in our Terms.

Google

If you choose to sign in with Google, Google handles that sign-in under its own privacy policy. Google also receives the website icon requests described in Section 3.

Google Search Console

If a website owner connects Google Search Console (Settings → Install), they sign in with Google and allow DataMogger to read their Search Console data and see their Google account's email address. We use that access only to show the owner, and the people they give access to the website, which Google searches led to the website: the search terms, clicks, impressions, click-through rates, average positions and pages, next to the website's own analytics, including an estimate of the revenue each search led to. We read it when someone looks at these reports, through the dashboard, the API, the MCP server, the command-line tool or the weekly report, and keep the answers for up to an hour to avoid asking Google again. We don't store Search Console data beyond that, use it for anything else, combine it with other customers' data, use it for advertising, or transfer it to anyone, and no person at DataMogger reads it except to fix a problem the owner reports or where the law requires. The access Google gives us (a refresh token) is kept encrypted; disconnecting in Settings, or removing DataMogger's access in your Google account, ends it, and on disconnecting we also ask Google to revoke it.

DataMogger's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

Apps and tools you connect

When you connect an app to your account, such as an AI assistant through "Connect DataMogger", or use an API token you created, we send it the analytics it asks for, from the websites you allowed. That can include visit details and your customers' payment records (names and email addresses where your billing system sends them). The app's provider handles that data under its own terms and privacy policy. When you sign in to the DataMogger command-line tool, the token it gets is named after your computer (its hostname, as the tool reports it), so you can tell your tokens apart; the tool keeps it on that computer. You can see and disconnect your connected apps, and revoke your tokens, under Account → API & MCP at any time.

Alert channels you add

When you or a teammate add a Slack, Discord or Telegram channel or a webhook under Settings → Alerts, we send it the alerts picked there for that website: traffic numbers, sources and pages, new payments (amount, product, where the customer came from) and goal completions. A goal alert can include a visitor's name, if you identify visitors, and the goal's details. That service handles the messages under its own terms. Remove a channel there at any time.

Legal requirements

We may disclose information if required by law, regulation, legal process or a government request, or to protect the rights, property or safety of DataMogger, our users or the public. If a request concerns a customer's website data, we will try to refer it to the customer and, unless the law prevents it, tell the customer about it.

Business transfers

If DataMogger is involved in a merger, acquisition or sale of assets, personal data may be transferred as part of that transaction, and this policy will continue to apply to it.

Apart from the website owner and the cases described in this section, we don't share personal data with anyone.

9. International data transfers

Our servers and database are in the United States. Encrypted backups are stored with Cloudflare R2, which may keep them in the United States or another region. If you, or the visitors to a website that uses DataMogger, are outside the United States, personal data will be transferred to and processed in the United States, where data protection laws may differ from those where you live. Cloudflare also handles each request in a data center near the visitor, which may be in another country.

Where the law requires it, for example for personal data from the EEA, the UK or Switzerland, we rely on appropriate safeguards for these transfers, including standard contractual clauses approved by the European Commission and their UK equivalent.

10. How long we keep data

  • Account data: until you delete your account.
  • Sign-in code records (code hash, IP address and user agent): deleted automatically after 30 days. Each code stops working after 10 minutes.
  • Records of sign-in attempts with disposable email addresses: deleted automatically after 30 days.
  • Error reports: deleted automatically after 180 days, or sooner once the problem is fixed.
  • Website visitor data (pageviews, visits, goals, visitor and identity records, and payments): kept for the website owner's plan's data retention: 36 months on Starter and the Free plan, 60 months on Growth and during the free trial. After that, each day's data is rolled into anonymous daily totals, which contain counts only, and the visit-level records are deleted.
  • When an owner moves to the Free plan (their free trial or subscription ended without a plan): 7 days after the trial ended, or 30 days after the subscription ended, their websites' visit-level data (visits, events, and visitor and identity records) is condensed into anonymous hourly and daily totals, and the visit-level records are deleted. Payments are kept for the Free plan's data retention, as above.
  • Visit references on the Free plan: deleted after 30 days.
  • Inactive Free accounts: if none of an account's websites has recorded a visit or a payment, and its owner hasn't signed in, for 12 months, we email the owner and delete those websites' analytics data 30 days later. The account and its websites stay.
  • Team invitations: until the invitation is accepted or removed, or the website is deleted. An accepted member's access lasts until the owner removes it.
  • Billing records (Paddle IDs, plan, status and dates): until you delete your account. Paddle keeps its own records of your purchases as the law requires.
  • Anonymous hourly and daily totals and AI crawler records: contain no personal data and are kept until the website, or its data, is deleted. After 90 days, hourly totals are combined into daily ones, and a month's daily breakdowns into monthly ones.
  • Deleting a website: deletes all of that website's data immediately. Its daily network totals (counts of visits by traffic channel) are first added to the anonymous network-wide totals described under "Peer benchmarks", which name no website.
  • Deleting your account: immediately deletes your account, all your websites and their data, and the sign-in and abuse-prevention records for your email address. As when a website is deleted, each website's daily network totals are first added to the anonymous network-wide totals.
  • Backups: encrypted database backups are kept for up to 14 days (daily backups) or 8 weeks (weekly backups), then deleted. Deleted data can remain in a backup until that backup expires.
  • Server logs: our servers keep limited technical logs, such as request times, paths and browser user agents (not IP addresses), for troubleshooting and security. Requests from the tracking script are not logged. Logs are overwritten automatically as new logs are written.
  • Google Search Console: the connection (an encrypted refresh token, the property and the Google account's email address) until the owner disconnects it or deletes the website; the data read from Google, in memory for up to an hour.
  • Support emails: kept for as long as we need them to handle your request and keep a record of it.

11. Security

We protect data with measures that include:

  • encryption in transit (HTTPS/TLS) for all traffic to datamogger.com, the script and the API;
  • storing sign-in codes and API keys only as hashes;
  • checking incoming payment webhooks with a secret specific to each website;
  • restricting each website's data to its owner; and
  • encrypting our database backups.

No system is completely secure, and we can't guarantee the security of data sent over the internet. If we learn of a breach that affects personal data we hold, we will notify affected customers and, where the law requires, the relevant authorities and individuals.

12. If you visited a website that uses DataMogger

The owner of that website controls the data collected about your visit and is responsible for answering questions and requests about it. Please read their privacy notice and contact them first.

  • To access, correct or delete your data, or to object to its use, ask the website owner. We will help them respond.
  • If you can't reach the owner, email us at support@datamogger.com and we will pass your request on to them. We can act on visitor data only on the owner's instructions.
  • To stop being counted on a website, use the opt-out described in Section 5.

13. Your rights

Depending on where you live, you may have the right to:

  • access the personal data we hold about you;
  • correct data that is inaccurate;
  • delete your data (you can also delete websites or your whole account yourself in the dashboard);
  • receive a copy of your data in a portable format (for now, by emailing us); and
  • object to our use of your data, or ask us to restrict it.

If you are in the EEA or the UK, you can also lodge a complaint with your local data protection authority. We would appreciate the chance to address your concern first.

California residents have additional rights, described in Section 14.

How to make a request. Email support@datamogger.com, from the email address on your account if you have one. We may need to verify your identity before we act. We will respond within the time the law requires (generally within 30 days for GDPR requests or 45 days for CCPA requests). We won't treat you differently for exercising your rights.

14. California privacy notice

If you are a California resident, the California Consumer Privacy Act, as amended by the California Privacy Rights Act (together, the "CCPA"), gives you rights over your personal information.

  • What we collect: identifiers (email address, IP address, Google account identifier and random cookie IDs), internet activity (pages viewed, referring websites, device and browser details), approximate location, commercial information (payment records that customers send us) and inferences (the conversion estimates described in Section 5). Sections 3, 5 and 7 explain each, and Section 10 explains how long we keep them.
  • Sources: you, your browser or device, and our customers.
  • Purposes and recipients: described in Sections 4, 5 and 8.
  • Customers' website data: we process it as a service provider to the customer, who is responsible for it.
  • No sale or sharing: we don't sell personal information or share it for cross-context behavioral advertising, and we don't use sensitive personal information for any purpose that would give you a right to limit it.
  • Your rights: to know what personal information we collect, use and disclose; to access, correct and delete it; and not to be discriminated against for using these rights. An authorized agent can make a request for you; we may ask for proof of their authority and verify your identity.

15. Children's privacy

DataMogger accounts are for adults: you must be at least 18 years old to create one, as stated in our Terms of Service. We do not knowingly collect personal information from anyone under 18 for an account. If we learn that we have, we will delete it promptly. If you believe a minor has given us personal information, contact us at support@datamogger.com.

Websites that use DataMogger may be visited by people of any age. Owners of websites directed at children are responsible for complying with the children's privacy laws that apply to them, including any consent requirements.

16. Changes to this policy

We may update this policy from time to time. We will post the new version on this page and change the "Last updated" date. If a change is material, we will also email account holders before it takes effect. If you keep using the Service after a change takes effect, the updated policy applies to you.

17. Contact us

For questions about this policy or requests about your data, contact:

DataMogger