Legal

Privacy Policy

SamTech Solutions · Effective date: 2026-10-17

This Privacy Policy explains what information SamTech Solutions (“we”, “us”, “our”) collects, how we use it, and what choices and rights you may have when you use the Domain Monitor mobile app, related websites, and supporting services (together, the “Services”).

1. Information we collect

DataSourceWhy
Email addressFirebase AuthenticationCreating and securing your account, sending magic-link sign-in emails, and contacting you about account or support matters
Display name / profile pictureGoogle Sign-In, if you choose itShowing your profile in the App
Firebase UID and account identifiersFirebase AuthenticationLinking your account across our backend, notifications, and subscription systems
Target configurationYou enter it in the AppMonitoring the hostnames, URLs, ports, paths, and related settings you ask us to check
Monitoring resultsGenerated by our monitoring serviceDisplaying status, latency, SSL/TLS details, recent history, troubleshooting details, and alerts
Support messages and related metadataYou submit it in the App or by emailResponding to support requests, bug reports, and product issues
FCM device tokenFirebase Cloud MessagingDelivering push notifications to signed-in devices
App version and platform (iOS or Android)The App, when you open it signed inKnowing which version of the App you use, so we can help with support requests and plan updates
Subscription and entitlement statusRevenueCat, Google Play, Apple App StoreDetermining your plan, managing trials and subscriptions, and enforcing feature limits
IP address, request metadata, and basic diagnosticsStandard server/network logs and anti-abuse systemsSecurity, fraud and abuse prevention, reliability, rate limiting, and debugging
Crash and error diagnosticsFirebase Crashlytics (Google), in released builds of the AppFinding and fixing crashes and errors in the App
Anonymous app-usage analyticsGoogle Analytics for Firebase, in released builds of the App. In the EU, the EEA, the UK and Switzerland only if you have agreed; elsewhere unless you have opted outUnderstanding which features are used so we can improve the App

Target configuration can include keyword rules you set to check a page’s content. When a check fails a keyword rule, a copy of that rule is stored with the check result it belongs to, kept for as long as that result is (see Section 4). Push and email alerts we send to the account owner may quote the specific rule that failed.

We do not collect passwords, full payment card details, or precise location data. Payment processing is handled by the relevant app store and supporting subscription providers. We receive subscription and entitlement information needed to manage access to paid features.

If you are on a Pro plan, you can turn on “Check from this device” in the App’s settings. It is off by default. When it is on, your phone checks your own monitors in the background, directly from its current network, on a schedule the operating system decides — we do not control or promise a fixed interval. The results of those checks are stored only on your device; we do not receive or store them. When a background check fails, and at most about once a day otherwise, the App contacts our backend through your existing signed-in session to read the cloud’s latest result for that monitor and confirm your subscription is still active; no new data is sent to us. The one notification this feature can produce is created on your device itself, not sent through a push service. Turning the toggle off, signing out, or your Pro plan ending stops all of this.

2. How we use information

  • To provide the Services, including running checks, storing recent monitoring history, syncing account-backed data, and showing results in the App.
  • To send push notifications and subscription-related service messages.
  • To authenticate users, secure accounts, and prevent unauthorized access or abuse.
  • To determine plan limits, trial eligibility, and paid feature access.
  • To respond to support requests, bug reports, and operational issues.
  • To maintain, troubleshoot, improve, and protect the reliability of the Services.

Where applicable, we process personal data to perform our contract with you in providing the Services, to comply with legal obligations, and for our legitimate interests in operating, securing, and improving the Services.

3. Third-party services

  • Firebase (Google) — authentication and push notification delivery. Firebase Privacy →
  • Firebase Crashlytics (Google) — crash and error diagnostics. Released builds of the App report crashes and errors so we can find and fix them. A report contains the error and its stack trace, your device model, its operating system version, and an installation identifier that Crashlytics generates. The App does not attach your account identifier or your monitoring data to these reports, and the one error it reports deliberately — a background check that could not show its notification — is sent as a fixed description with no address, monitor name or keyword in it. An unexpected crash carries whatever description the failure itself produced, which in rare cases could include an address you monitor. We do not use any of this for advertising. This is separate from the usage-analytics switch in the App: turning “Share anonymous usage data” off stops analytics, not crash reporting. Firebase Privacy →
  • Google Analytics for Firebase — anonymous product-usage analytics, in released builds of the App. If your device reports that it is in the European Union, the European Economic Area, the United Kingdom or Switzerland, the App asks you first and analytics stays off until you agree — nothing is collected and nothing is sent before then, including if you decline. Everywhere else it is on by default and you can turn it off in the App under About › Share anonymous usage data. We work out which of the two applies from the region setting and time zone your device already reports; we do not ask for your location, and we do not look your region up from your IP address to decide this. It records anonymous app interactions (for example: a monitor was added, a check was run, the upgrade screen was viewed), screen names, and a per-installation identifier that Firebase assigns (the Firebase app-instance ID), together with two coarse install-level properties: your plan tier (none, registered or Pro) and how many monitors you have, rounded into a band (0, 1–5, 6–15, 16–30). Firebase also automatically attaches coarse device and app information to these events, as Google documents for every app that uses it: app version, operating system version, device model, language, and a country-level region derived from your IP address, not your precise location. It never includes the addresses, names, keywords, domains, or results of anything you monitor, and never your account email or user ID — the App never links an analytics event to your account. It is not used for advertising: no advertising identifier is collected, and the App does not track you across other companies’ apps or websites. Wherever you are, you can change your answer at any time in the App under About › Share anonymous usage data. Turning it off takes effect at once: your choice is stored immediately, the App sends one final, empty “opted out” signal so we know to expect nothing more from this installation (not where analytics had never been switched on, because there was nothing to stop), and collection stops within a couple of seconds. It is off entirely in development builds. Firebase Privacy →
  • RevenueCat — subscription management and receipt validation. RevenueCat may process subscription status, transaction metadata, and device or app identifiers needed to manage entitlements. RevenueCat Privacy →
  • Cloudflare Turnstile — anti-bot protection on our sign-in flow. Turnstile may process IP address and browser/device signals to distinguish humans from bots. Cloudflare Privacy →
  • Google Play / Apple App Store — payment processing and subscription platform services.
  • Fly.io — backend hosting and infrastructure. Our backend is currently hosted in the EU region. Fly.io Privacy →
  • Postmark (ActiveCampaign) — transactional email delivery for sign-in emails, alert emails and in-app support messages. Postmark Privacy →
  • Domain registries (RDAP) — to show the registration expiry date and registrar for domains you monitor, the App looks up that public registration record directly from your device through the public RDAP bootstrap service rdap.org, which redirects the request to that domain's registry. The request contains only the domain name, and rdap.org sees that name and your device's IP address. For Pro accounts, our server performs the same public lookup once a day per domain to send expiry warnings.
  • Google (connectivity check) — when the “Check from this device” feature (see Section 1) has a check fail at the network level, the App may send a single request to a connectivity-check address Google operates, to tell “this site is unreachable” apart from “this phone is offline.” That request carries no account information and none of your monitor addresses; Google sees your device's IP address, as it would for any request to a Google server. Google Privacy →

We do not sell your personal information. We share data with service providers only as needed to operate, secure, and support the Services.

4. Data retention

  • Account data is retained while your account remains active, unless we need to keep certain records for legal, security, fraud-prevention, or operational reasons.
  • Monitoring history is retained as a rolling recent history and is currently capped at up to 300 check results per target.
  • Push notification tokens are removed when you sign out. Tokens for inactive or unreachable devices may also be removed automatically over time.
  • Support communications may be retained for as long as reasonably necessary to handle your request, maintain support history, and protect the Services.
  • Server and security logs are generally retained for up to 90 days, unless a longer period is needed for investigation, legal compliance, or abuse prevention.

5. Your rights and choices

Depending on your location, you may have rights to access, correct, delete, or export your personal data, or to object to or restrict certain processing. For users in the EU/EEA or other regions with similar laws, this may include rights available under applicable data protection law, including the GDPR.

You can request account deletion and deletion of associated data directly through the App. We may need to verify your identity before acting on certain requests. We will respond within the timeframe required by applicable law.

6. International data processing

Your information may be processed by our service providers in countries other than your own, depending on where those providers operate their infrastructure. When we use third-party providers, data may be transferred internationally as needed to provide the Services.

7. Children’s privacy

The Services are not directed to children under 13, or the minimum age required by local law to consent to digital services. We do not knowingly collect personal information from children in violation of applicable law. If you believe a child has provided us with personal information, please contact us and we will take appropriate steps to delete it.

8. Security

We use reasonable technical and organizational measures designed to protect your information, including HTTPS for data in transit, authentication controls, and access restrictions on backend systems. No method of transmission over the internet or electronic storage is completely secure, so we cannot guarantee absolute security.

9. Changes to this policy

We may update this Privacy Policy from time to time. When we do, we will post the updated version here and update the effective date above. If we make material changes, we may also notify you through the Services or by email.

10. Contact

If you have questions about this Privacy Policy or want to make a privacy-related request, contact us at support@samtech.solutions.

← Back to site