1. Who is responsible
The party responsible for processing personal data in connection with DeployWatchers and the website https://deploywatchers.com (the "Service") ("controller") is:
DeployWatchers S.R.L.
MD-2068, mun. Chișinău, str. Matei Basarab, 5/1, ap. 58
Republica Moldova
E-mail: support@deploywatchers.com
For all privacy-related requests please contact support@deploywatchers.com .
2. Overview
We process personal data only to the extent necessary to provide and secure the Service, to communicate with you and to meet legal obligations. We do not sell personal data and do not use advertising tracking. On our public website we use Google Analytics 4 only if you consent (see section 9). With that consent, we also measure registration, the first website added and checkout/purchase outcomes. We do not track page views, forms or account activity inside the authenticated application, and no analytics is used in the admin panel.
The operator is located in the Republic of Moldova, where Law No. 195/2024 on personal data protection applies. Where the EU General Data Protection Regulation (GDPR) applies to our processing, for example because we offer the Service to people in the European Union, we indicate the GDPR legal basis for each purpose below. Depending on where you are located, other data protection laws may apply instead or in addition.
3. Account data
- Data: name, e-mail address, optional separate alert e-mail address, password (stored only as a one-way hash), plan, notification preferences, API token names (tokens themselves are stored only as hashes), and whether your account is active or disabled.
- Purpose: creating and managing your account, authentication, providing the Service, customer support.
- Legal basis (where the GDPR applies): performance of a contract (Art. 6(1)(b) GDPR).
Optional Google sign-in
If you choose Continue with Google, we redirect you to Google to authenticate. Google receives the sign-in request and processes your interaction under its own privacy policy. We receive your Google account identifier, name, email address and email verification information. We store the identifier to connect your account; we do not store Google access or refresh tokens, or import your profile photo. We request no access to your mail, contacts or files. This sign-in choice is separate from optional Google Analytics consent.
You may continue to use email/password registration instead. To connect an existing account, sign in with your password and connect Google in Settings. Google authorization does not replace acceptance of our Terms or acknowledgement of this Privacy Policy. See Google’s Privacy Policy (opens in a new tab) .
Paid subscriptions and billing
Prices on our pricing and checkout pages are provided by Paddle: these pages load Paddle.js, so your browser sends your IP address and browser information to Paddle, which uses them to determine your location, currency and applicable tax. Paddle.js also loads Paddle Retain (formerly ProfitWell), Paddle's subscription-retention script. For Retain initialization, where a signed-in customer has a linked Paddle customer record, we pass that Paddle customer identifier rather than separate name or email fields. Paddle can associate this identifier with its existing customer records. Where GDPR applies, the legal bases are steps taken at your request before entering into a contract (Art. 6(1)(b)) and our legitimate interest in showing correct local prices (Art. 6(1)(f)). Other pages do not load Paddle.
When you open Checkout, we also pass your account email to prefill the payment form and an encrypted account reference to associate the purchase with your DeployWatchers account and grant the correct access. This reference contains our internal account identifier and billing environment in encrypted form; the internal identifier is not sent as a plain-text field. If you consent to conversion measurement, we may also pass a separate random analytics reference to match the confirmed payment to that measurement (section 9). These Checkout data flows are separate from Retain initialization.
Paddle is our merchant of record: it sells the subscription to you and handles checkout, payments, applicable sales taxes, invoices and payment-related fraud checks. Payment and billing details entered in Paddle Checkout are processed by Paddle under Paddle’s Privacy Policy (opens in a new tab) . We do not receive or store full card numbers or card security codes.
We keep the Paddle customer identifier and email, subscription and transaction identifiers, selected plan and prices, status, billing periods, scheduled changes, currency, tax and totals to grant access, reconcile payments, provide billing support and prevent abuse. This necessary processing does not depend on analytics consent. Where GDPR applies, the legal bases are performance of the subscription contract (Art. 6(1)(b)), compliance with applicable legal obligations (Art. 6(1)(c)) and our legitimate interest in preventing fraud and resolving billing disputes (Art. 6(1)(f)).
You can manage payment methods, invoices and cancellation through Billing in your account. Billing records are retained separately from monitoring data; deleting an account does not erase transaction history required for accounting, legal obligations or billing disputes. Contact us for a review of any retained personal data.
4. Website URLs and domains
- Data: the URLs, domains and names of websites you register, monitoring settings and heartbeat names. Heartbeat tokens are stored only as hashes.
- Purpose: performing the monitoring checks you requested.
- Legal basis: performance of a contract (Art. 6(1)(b) GDPR).
Monitored websites must be publicly accessible. You are responsible for having the right to have the websites you register monitored (see our Terms of Service). URLs can contain personal data (for example a personal name in a domain); please avoid submitting URLs that contain personal data of others unless you are entitled to do so.
5. Monitoring results and technical metadata
- Data: results of checks against your websites — HTTP status codes, response times, redirect chains, selected HTTP response headers, DNS records, SSL certificate details, robots.txt rules, sitemap statistics, PageSpeed scores, heartbeat timestamps, and detected changes and incidents.
- Cookies on monitored websites: our cookie check loads your page in an isolated browser and records only cookie metadata (name, domain, path, expiry, security flags, whether it is a third-party or tracking cookie). Cookie values are never stored.
- Browser JavaScript monitoring (when enabled on an eligible plan): we process console errors, uncaught exceptions, observable unhandled promise rejections and failed JavaScript resource requests, with a normalized message, source URL with query and fragment removed, line/column where available, first/last seen times and an occurrence count. We do not collect form values, cookies, browser storage, request bodies or arbitrary page text. Error messages can nevertheless contain personal or sensitive data.
- Visual monitoring (when enabled): we capture either the first screen (a 1366 × 900 viewport) or the full page, according to your settings. Full-page captures have a technical height limit and may be truncated. When a baseline exists, we also create a pixel-difference image and changed-pixel score. Screenshots can contain personal data rendered by your website. They are stored privately and deleted under the plan retention period or when the website/account is deleted. Pixel differences can be caused by normal dynamic content.
- Purpose: showing you the state of your websites, detecting changes, creating incidents and alerts.
- Legal basis: performance of a contract (Art. 6(1)(b) GDPR).
Monitoring results describe the technical state of websites. They are usually not personal data, but they can contain it in individual cases, for example a person's name in a domain or URL, or an e-mail address in DNS records or SSL certificates of the monitored website (see section 13).
For PageSpeed analysis the public URL of your website is sent to the Google PageSpeed Insights API, which loads the page from Google's infrastructure. No account data is sent to Google for this purpose.
6. Notification data
- Data: recipient address, subject, type and delivery status of alert e-mails and account e-mails (e.g. verification, password reset). The content of the e-mails is passed to our e-mail delivery provider (see section 12) but not stored in our notification log.
- Purpose: sending alerts you configured and account-related messages; troubleshooting delivery.
- Legal basis: performance of a contract (Art. 6(1)(b) GDPR).
If you configure Telegram or Slack, we store the bot token or incoming webhook URL encrypted and the Telegram destination identifier. We send the website domain/name, incident type, severity, a short incident title, UTC time and a link to the relevant DeployWatchers page to the provider you selected. We do not send screenshots, browser error stacks, credentials or full monitored URLs. Delivery status, attempt count and a sanitized error are stored for 365 days. Telegram and Slack process the information they receive under their own terms and privacy policies.
7. Logs, security and consent records
-
Data:
- web server access logs: IP address, time, request method, requested path (without query string), status code, referring page and browser user agent;
- short-lived rate-limiting counters for login attempts and API requests (based on e-mail address and IP address, or account);
- administrative audit logs of actions taken by our administrators (including the administrator's IP address and, for account-related actions, the affected account's e-mail address);
- a record of which version of the Terms of Service and Privacy Policy you accepted, when, and from which IP address;
- technical error reports and, when enabled, aggregate operational metrics, sampled request traces and scheduler check-ins (see section 12, Sentry). SQL spans exclude query text and parameter values. The application removes user identifiers, IP addresses, e-mail addresses, cookies, request bodies and query strings before sending. Operational metrics do not include customer website URLs or identifiers.
- Purpose: operating and securing the Service, preventing abuse, investigating incidents, and being able to demonstrate accepted contract terms.
- Legal basis: our legitimate interests in secure and reliable operation and in documenting contractual agreements (Art. 6(1)(f) GDPR); where applicable, legal obligations (Art. 6(1)(c) GDPR).
8. Cookies and similar technologies
We use necessary first-party cookies (session, CSRF protection, "remember me" if you choose it, and a cookie that stores your cookie choice). Analytics cookies are used only with your consent (see section 9). Details are in our Cookie Policy.
Consent records for website visitors: your cookie choice is stored only in the
dw_consent cookie in your browser. It contains the version
of the Cookie Policy you responded to, whether you allowed analytics (yes/no) and the date of your choice. We do not
store visitors' cookie choices together with personal data on our servers.
9. Website analytics (Google Analytics 4)
The analytics scope described here was updated on 4 November 2026. Previous public-page-only consent is not reused for conversion measurement; we ask for your analytics choice again.
-
Scope: Google Analytics 4 ("GA4") is used only on our public website (for example the home page
and these legal pages). With your consent, additional outcomes are measured: successful registration
(
sign_up), adding your first website (first_website_added), opening checkout (begin_checkout) and a webhook-confirmed checkout payment (purchase). These are sent through an isolated conversion document without loading Google Analytics into the private page itself. We do not send private page URLs or titles, monitored website addresses, form contents, passwords, names, email addresses or account IDs to Google. The admin panel is not tracked. Purchase measurement includes the plan, monthly/yearly interval, currency, amount excluding tax, tax and a random checkout identifier for deduplication. It does not include your Paddle customer or transaction ID. Renewals are not counted as new acquisition purchases. Necessary billing records and fulfillment checks operate independently of analytics consent. - Purpose: to understand how visitors use our public website, to measure the reach of our content and to understand which campaigns lead to registration, first use and paid subscriptions.
- Information that may be collected: pseudonymous identifiers stored in cookies, pages viewed, the referring page, approximate location (country, region, city), device type, browser and operating system, interactions with the public website, the conversion events described above, approved campaign labels and timestamps. Your IP address is processed by Google to derive the approximate location; according to Google, GA4 does not log or store IP addresses.
- Provider: Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland (for users in the EEA, the UK and Switzerland) and Google LLC, 1600 Amphitheatre Parkway, Mountain View, CA 94043, USA. Google processes the data as our processor / service provider in accordance with its terms for Google Analytics.
- Transfers to the USA: Google LLC may process GA4 data in the United States. For transfers subject to GDPR Chapter V (Articles 44–49), the EU-U.S. Data Privacy Framework (DPF) provides an Article 45 adequacy route under Commission Implementing Decision (EU) 2023/1795 only while the recipient has an active certification covering the transferred data and that decision applies. Google describes its participation in its transfer framework information (opens in a new tab) . Where an applicable adequacy route does not cover a transfer, Google's Data Processing Terms (opens in a new tab) provide for Standard Contractual Clauses (SCCs) as applicable safeguards under Article 46(2)(c) GDPR. Section 14 explains the separate requirements of Moldova Law No. 195/2024. Your analytics consent does not replace a required transfer safeguard.
- Legal basis (where the GDPR / ePrivacy rules apply): your consent (Art. 6(1)(a) GDPR); storing and accessing information on your device is likewise based on your consent under applicable ePrivacy law.
- Activation only after consent: Google Analytics is not loaded and sends no requests until you choose "Accept all" or enable Analytics under "Manage preferences" in our cookie banner. If you reject non-essential cookies or make no choice, GA4 is not loaded at all.
- Withdrawing or changing consent: you can change your choice at any time with effect for the future via the Cookie settings link in the footer or the button below. On withdrawal, tracking stops immediately and the Google Analytics cookies set on our domain are deleted where technically possible.
- Retention: Google Analytics data is retained for 2 months. Cookie durations are listed in our Cookie Policy.
More information from Google: Google Privacy Policy (opens in a new tab) , Google's privacy information for business products (opens in a new tab) , Safeguarding your data (Google Analytics) (opens in a new tab) . You can also use Google's browser add-on to opt out of Google Analytics (opens in a new tab) .
10. Retention periods
| Data | Retention |
|---|---|
| Account data | Until your account is deleted |
| Subscription and transaction records | Retained separately from the account. Retention is determined by the subscription lifecycle, unresolved payments, refunds or disputes, and applicable accounting and legal recordkeeping obligations. Billing mirror records currently have no automatic deletion schedule; account deletion does not erase them. Requests to erase retained billing personal data are reviewed individually against these purposes and obligations. Paddle applies its own retention policy. |
| Website URLs and settings | Until you delete the website or your account |
| Detailed check results | 30 days |
| Browser JavaScript error records | Deleted 30 days after last seen |
| Browser screenshots and visual-difference images | Pro: 30 days; Agency: 90 days; approved baselines follow the same limit. Deleting a website or account also deletes its files. |
| Encrypted Telegram/Slack credentials | Until you remove the integration or your account is deleted |
| Chat notification delivery records | 365 days |
| Detected changes (events) | 365 days |
| Resolved incidents | 365 days |
| Notification logs | 365 days; when your account is deleted, recipient address and subject are removed immediately |
| Administrative audit logs | 730 days; when your account is deleted, your e-mail address is removed from them |
| Session data (server-side) | 120 minutes after your last activity, or until you log out |
| Rate-limiting counters | A few minutes |
| Web server and application logs | Rotated automatically by size (at most 50 MB per component); older entries are overwritten. There is no fixed time period. |
| Technical error reports, operational metrics, sampled request traces and scheduler check-ins (Sentry) | Sentry applies the retention configured for the relevant data type and subscription plan; events, traces and metrics can have different periods. Contact us for the period applicable to your request. |
| E-mail delivery records at our e-mail provider (Resend) | Resend applies the retention for sent-email content and delivery logs under our account and its service terms. Copies delivered to recipients remain under their control. Contact us for the period applicable to your request or to request removal of provider-held records. |
| Encrypted database backups | Daily backups for 14 days, weekly backups for 8 weeks; then deleted automatically after the next successful backup. The most recent backup is always kept. |
| Aggregated daily statistics (per website and check: number of passed/failed checks, average response time) | As long as the website exists; deleted together with the website or your account. They remain linked to your website and are therefore not anonymous. |
| Google Analytics data (only with consent) | 2 months; cookie durations see Cookie Policy |
Cookie choice of website visitors (dw_consent, in your browser) | 180 days |
| Consent records (accepted terms version, time, IP) | Until your account is deleted |
11. Deleting your data
- You can delete individual websites at any time in the application; their monitoring data, heartbeats and statistics are deleted with them.
- To delete your account, contact support@deploywatchers.com from the e-mail address of your account. After verifying the request we delete, without undue delay, your account, all your websites and their monitoring data, heartbeats and API tokens. Notification logs keep only anonymous delivery statistics, and your e-mail address is removed from administrative audit logs. If the account has Paddle billing history, we first resolve cancellation and any unsettled payments with you; deleting an account does not itself cancel a subscription. Once those matters are resolved, we detach the retained billing records and delete the account and monitoring data. The retained Paddle customer record is marked so that it cannot be linked automatically to a later account. Billing data is retained separately as described in section 10; you may request a review of any retained personal data.
- Data that has already been sent to service providers (for example e-mail delivery records or error reports) is deleted according to their retention periods (section 10).
- Deleted data can remain in our encrypted database backups until those backups are deleted automatically. While backups run normally (daily), this happens after approximately 8 weeks at the latest. Old backups are only deleted after a new backup has succeeded, and the most recent backup is always kept, so the period can be longer if backups are interrupted. Backups are only used to restore the Service after a failure.
- Any exception to these periods must have an applicable legal basis, such as a mandatory recordkeeping obligation or the establishment, exercise or defence of a legal claim. We assess erasure requests against the data and purposes involved.
12. Service providers and recipients
We do not sell personal data. We share data with the service providers listed below only to the extent necessary for the purposes stated in the table: operating and securing the Service, delivering e-mails, fixing errors, storing backups and, only with your consent, analysing public-site visits and the consent-based conversion outcomes described in section 9. Beyond that, we disclose data to other recipients only where required by law (for example at the request of a competent authority). Providers listed as processors process personal data on our behalf; details are in the privacy information of each provider.
| Provider and role | Purpose and data | Location |
|---|---|---|
| Scaleway SAS, 8 rue de la Ville-l'Évêque, 75008 Paris, France Processor (hosting provider) Privacy information (opens in a new tab) |
Hosting of the application servers and the database; operation, availability and security of the infrastructure. Primary infrastructure: the application and the live database run here, so account data, website settings, monitoring results and logs are stored and processed on it. Encrypted backup copies of the database are additionally stored at Cloudflare R2 (see below). | Netherlands (Scaleway AMS1; application and database) |
| Cloudflare, Inc. (DNS, TLS and reverse proxy) Processor (network and security provider) Privacy information (opens in a new tab) |
Domain name resolution, encrypted delivery of the website and the application, protection against attacks and abuse. Every request to the website passes through Cloudflare: IP address, requested URL, browser user agent, request headers and the transmitted content. | Cloudflare's global network (requests are handled by a data centre close to the visitor) |
| Cloudflare, Inc. (R2 object storage) Processor (storage provider) Privacy information (opens in a new tab) |
Storage of database backups for disaster recovery. Backup copies of the database, created daily on our server (and as a safety copy before a restore) and encrypted before upload; Cloudflare does not hold the decryption key. R2 does not hold a live copy of the database and is not used to run the Service. | Eastern Europe (R2 location hint EEUR; no EU-only jurisdiction guarantee) |
| Resend (Plus Five Five, Inc.) Processor (e-mail delivery) Privacy information (opens in a new tab) |
Delivery of account e-mails (verification, password reset) and monitoring alerts. Recipient e-mail address, subject and content of the e-mail, delivery status. | United States (stored email content and delivery logs; sending region may differ) |
| Paddle (merchant of record) Independent controller for payment processing, tax and fraud prevention Privacy information (opens in a new tab) |
Selling paid subscriptions, collecting payments, issuing invoices and providing the customer billing portal. Checkout email, billing details and payment information submitted directly to Paddle. We receive customer, subscription and transaction identifiers, email, plan, billing dates, currency, totals and payment status. We do not receive or store full card numbers or card security codes. | See Paddle’s privacy information, including international transfers |
| Sentry (Functional Software, Inc.) Processor (error monitoring and operational diagnostics) Privacy information (opens in a new tab) |
Detecting and fixing technical errors and monitoring the reliability of the Service. Technical error reports (error message, stack trace, release, request path); when enabled, aggregate HTTP/check counts and durations, queue health, scheduler check-ins and sampled request traces. SQL spans contain only timing, operation and a keyed fingerprint, never query text or parameter values. Operational metrics contain only registered route templates, HTTP methods/status classes, predefined check types, results, queue names, environment and release, without customer website URLs or identifiers. User identifiers, IP addresses, cookies, request bodies, query strings and e-mail addresses are removed by the application before sending. | European Union (Germany; Sentry EU ingest region) |
| Google (optional sign-in) External identity provider Privacy information (opens in a new tab) |
Authentication when you choose to sign in or connect your account with Google. Sign-in request; Google account identifier, name, email and verification information returned to us. Access and refresh tokens are not retained. | See Google’s privacy information |
| Google Analytics 4 (Google Ireland Limited / Google LLC) — only with your consent Processor (web analytics) Privacy information (opens in a new tab) |
Public website usage and consent-based registration, first-website and checkout/purchase conversion measurement (see "Website analytics"). Pseudonymous cookie identifiers, pages viewed, referrer, device and browser information, approximate location derived from the IP address. | EU and USA (see "International transfers") |
| Google PageSpeed Insights API (Google LLC) Independent provider of the API Privacy information (opens in a new tab) |
Performance analysis of the monitored websites. Only the public URL of the monitored website. No account data is sent. | See the provider's privacy information |
For data about our own customer relationship with them (for example our contact and billing details), the providers act as independent controllers.
13. Our role for monitoring data
We are the controller for the data we process to manage accounts, operate and secure the Service and run our public website.
When you use the Service to monitor websites, the monitoring results may in individual cases contain personal data of third parties (section 5). For such data we may act as a processor on your behalf, depending on the circumstances and the applicable law. If your use requires a controller–processor agreement, contact support@deploywatchers.com before registering websites whose monitoring results may contain personal data. The required written agreement must be concluded before that processing begins; acceptance of this Privacy Policy alone is not a data processing agreement. Until then, do not submit websites for processing that requires such an agreement.
14. International transfers
The locations and recipients for each enabled service are listed in section 12. US-based and global providers may process data outside Moldova and the EEA, including through remote access and onward transfers. A provider's European storage region does not by itself exclude access from another country; the R2 location hint is not an EU-only jurisdiction guarantee.
Transfers subject to the EU GDPR
GDPR Chapter V, Articles 44–49 (opens in a new tab) , applies alongside the lawful basis for the underlying processing. Article 44 covers onward transfers as well as the initial transfer.
- Adequacy — Article 45: an applicable European Commission adequacy decision permits covered transfers. For the USA, Decision (EU) 2023/1795 (EU-U.S. DPF) (opens in a new tab) covers participating US organisations with an active certification for the relevant data; it is not a blanket approval of every US provider or service.
- Appropriate safeguards — Article 46: where no applicable adequacy decision covers the transfer, the relevant provider data processing terms provide contractual safeguards, including the European Commission SCCs, Decision (EU) 2021/914 (opens in a new tab) , as applicable. Their use requires enforceable rights and effective remedies, assessment of the destination's laws and practices, and supplementary technical or organisational measures where necessary. Signing a DPA alone does not establish that every transfer is covered.
- Other Chapter V rules: Article 47 addresses binding corporate rules; we do not claim to have adopted our own. Article 48 limits recognition of third-country disclosure orders. Article 49 derogations apply only where their specific conditions are met and are not our routine basis for analytics, hosting or email processing.
Transfers from Moldova
Chapter V of Moldova Law No. 195/2024 of 25 July 2024 (opens in a new tab) governs transfers to other states and international organisations. Article 44(2) excludes transfers to EEA member states from that chapter and requires no special authorisation for those transfers; other data protection obligations still apply.
For other destinations, Article 45 concerns adequacy decisions by Moldova's National Center for Personal Data Protection. The EU-U.S. DPF decision is an EU mechanism, not by itself a Moldovan adequacy decision. In the absence of an applicable Moldovan adequacy decision, Article 46(1) requires appropriate safeguards, enforceable rights and effective remedies. Article 46(2)(c) expressly permits standard data protection clauses approved by the Center or adopted by the European Commission, without specific authorisation. Clauses and their application must meet these requirements; an ordinary confidentiality agreement is not a substitute. Articles 47–49 regulate binding corporate rules, foreign disclosure orders and specific derogations.
Provider terms and access to safeguards
The following links describe the relevant provider's transfer terms or, for Paddle's own payment processing, its privacy information. Only enabled providers from section 12 are listed.
- Scaleway SAS, 8 rue de la Ville-l'Évêque, 75008 Paris, France (opens in a new tab)
- Cloudflare, Inc. (DNS, TLS and reverse proxy) (opens in a new tab)
- Cloudflare, Inc. (R2 object storage) (opens in a new tab)
- Resend (Plus Five Five, Inc.) (opens in a new tab)
- Paddle (merchant of record) (opens in a new tab)
- Sentry (Functional Software, Inc.) (opens in a new tab)
- Google Analytics 4 (Google Ireland Limited / Google LLC) — only with your consent (opens in a new tab)
You can request information about the safeguards applicable to your data, including a copy of relevant contractual safeguards, from support@deploywatchers.com . We may redact confidential information while preserving the information necessary to explain the safeguards.
15. Your rights
Depending on the applicable law, you may have the right to:
- access the personal data we hold about you;
- rectification of inaccurate data;
- erasure of your data;
- restriction of processing;
- data portability;
- object to processing based on legitimate interests;
- withdraw consent at any time with effect for the future, where processing is based on consent;
- lodge a complaint with a data protection supervisory authority.
To exercise your rights, contact support@deploywatchers.com . We may need to verify your identity before acting on a request.
The supervisory authority in the Republic of Moldova is the National Center for Personal Data Protection (datepersonale.md (opens in a new tab) ). Where the GDPR applies, you can also lodge a complaint with the supervisory authority of the EU member state where you live or work.
16. Security
We use technical and organisational measures appropriate to the risk, including encryption in transit (HTTPS), hashing of passwords and access tokens, encrypted sessions, role-based access for administrators with audit logging, network isolation of the components that access monitored websites, encryption of database backups before they leave our server, and regular deletion of data that is no longer needed. No system is completely secure, and we cannot guarantee absolute security.
17. Children
The Service is intended for businesses and professionals and is not directed at children. We do not knowingly collect personal data of children.
18. Changes to this policy
We may update this Privacy Policy when our processing or the law changes. The current version is 1.4. We will inform you of material changes and ask you to acknowledge the new version when you next use the Service.