Privacy Policy

1. Information We Collect

Account information. When you sign up, our authentication provider (Clerk) collects your name, email address, sign-in credentials, and organization details. We receive your account identifiers and profile information from Clerk; we never see or store your password.

Billing information. Paid plans are processed by Stripe. Stripe collects and stores your payment-card details directly — we never receive or store full card numbers. We retain your Stripe customer and subscription identifiers, your plan, and your billing status.

Service data. To provide monitoring, we store the configuration you create — the URLs, hostnames, IP addresses, ports, and settings of the monitors you set up; the servers you register; and the metrics your agent reports (CPU, memory, disk, network, load, and systemd service names). We store the results and history of these checks.

Communications data. The notification destinations you configure, such as email addresses, chat webhook URLs, and bot tokens. Credentials of this kind are encrypted at rest.

Mobile phone numbers. If you opt in to SMS or text-message alerts, we collect the mobile phone number you provide and a record of your opt-in (timestamp and the action that opted you in). We use this information solely to deliver the alerts you have configured and to honor opt-out and HELP requests.

Mobile app data. The Ensju companion app for Android and iOS uses the same account as the web. It stores only the session token issued by Clerk, kept in the platform's encrypted secure store (iOS Keychain / Android EncryptedSharedPreferences). The app does not collect device advertising identifiers, does not include analytics or crash-reporting SDKs, does not request location, contacts, photos, microphone, or camera permissions, and does not track you across apps or websites.

Push notification registration. If you turn on push notifications in the mobile app, the app sends us four things about that device: the push token issued for it by the operating system's notification service through Expo (an opaque string that addresses the device and nothing else — it is not a device serial number, advertising identifier, or phone number), the platform (iOS or Android), a device name you supply or accept (for example “Robby’s iPhone”), and the app version. We store those alongside the date the device was registered and the date we last delivered to it. We use them for one purpose: sending that device the alerts you have already configured in Ensju. We do not use them to profile you or to track you across apps or websites.

Usage and technical data. Logs of requests to the Service — including IP address, browser type, timestamps, and actions taken — used for security, debugging, and abuse prevention.

Website and product analytics. For usage analytics we run a privacy-friendly tool (Umami) that we self-host on our own infrastructure — no third-party analytics company is involved in it. It records only aggregate, non-identifying usage such as page views, referring site, approximate region, and browser type; it sets no advertising or cross-site tracking cookies, builds no individual advertising profile, and is not present in our mobile app.

Marketing-site visitor identification. On our public marketing pages only — not the signed-in app, and not the mobile app — we also use a third-party service, Leadsy (vtag.ai), that helps us recognize the businesses that visit ensju.com so we can follow up with prospective customers. It may receive your IP address and on-page activity and may set its own cookies.

2. How We Use Your Information

We use the information we collect to:

• operate, maintain, and secure the Service;
• run your monitors and deliver the alerts you have configured;
• process payments and manage your subscription;
• provide customer support;
• detect, prevent, and respond to abuse, fraud, and security incidents;
• send service, security, and account notices;
• comply with legal obligations; and
• understand usage so we can improve the Service.

3. We Do Not Sell Your Data

We have never sold, rented, or traded your personal information or your service data, and we never will. We do not share it with advertisers or data brokers, and we do not use it for advertising or profiling. 17 Solutions is funded by subscriptions — not by your data.

Mobile phone numbers and opt-in data are never shared with third parties or affiliates for marketing or promotional purposes. We share this information only with the carrier and messaging-platform sub-processors needed to deliver the messages you asked for.

4. SMS / Text Message Notifications

We send SMS or text-message alerts only to users who have explicitly opted in by adding a mobile phone number to a notification channel in their account and confirming consent. You may opt out at any time by replying STOP to any message you receive from us; replying HELP returns help instructions and our support contact.

Message frequency varies based on the monitors and alerts you configure — some accounts will receive no SMS messages for weeks, others will receive several during an incident. Message and data rates may apply depending on your mobile carrier and plan.

We use SMTP2GO to deliver SMS messages. SMTP2GO handles your phone number and message content only as our sub-processor under contract, and is bound by the same restriction: your mobile information is not used for marketing or shared with affiliates or third parties for promotional purposes.

We do not sell or rent mobile phone numbers, opt-in records, or message content to anyone, for any purpose.

5. Newsletter and Marketing Email

If you subscribe to our newsletter or request a resource such as a guide, we add the email address you provide to our marketing list, which is managed for us by MailerLite as a sub-processor. These messages are separate from the service, security, and alert emails tied to your account.

Every marketing email includes an unsubscribe link and you can opt out at any time. We never add you to marketing email without an action on your part, and if you never subscribe we never send you marketing email. This mailing list is unrelated to the Ensju mobile app, which sends no marketing.

6. How We Share Information

Apart from integrations you authorize yourself (described below), we share information only with the service providers ("sub-processors") that help us operate the Service, each bound by contract to protect it and to use it only on our instructions. They fall into a few categories:

• Authentication and billing — to sign you in and process payments;
• Infrastructure and hosting — to run the application, database, and probe network;
• Communications — to deliver the email, SMS, and newsletter messages you configure or request;
• Observability — to manage operational logs (with personal data such as IP and email addresses redacted before they are shipped);
• Mobile app updates — to deliver over-the-air updates to our mobile companion app.

The complete, current list of our sub-processors — naming each provider, what it does, the data it receives, and its location — is maintained at ensju.com/legal/subprocessors. We update that page whenever we add, remove, or replace a sub-processor.

Some supporting tools are self-hosted by 17 Solutions on our own infrastructure rather than run by an outside vendor — our website analytics (Umami) and the anti-abuse CAPTCHA on our public forms (mCaptcha). The data they process stays on our systems and is not shared with a third-party analytics or CAPTCHA provider.

Integrations you authorize are different. If you connect a third-party application to your account, for example an AI assistant through our MCP integration, that application receives the organization data you direct it to read, under the permissions you approve on the sign-in screen, for as long as you keep it connected. Such applications act on your instructions, not ours: they are not our sub-processors, and their handling of the data they receive is governed by their own terms and privacy policies. The integration is read-only, and credentials stored in the Service (such as notification channel secrets) are never included in what it can read. You can disconnect an application in that application at any time; the sign-in token it holds expires within about 24 hours, and an organization administrator can end its access by removing the member from the organization, effective within seconds.

We may also disclose information when required by law, to enforce our agreements, or to protect the rights, property, or safety of our users or the public. If 17 Solutions is involved in a merger, acquisition, or sale of assets, your information may transfer as part of that transaction; we will notify you, and any successor will remain bound by this Policy.

7. Data Retention

We retain account and billing records for as long as your account is active and for a reasonable period afterward to meet legal, tax, and accounting requirements. Monitoring history is retained according to your plan's retention window. Encrypted backups are kept on a rolling schedule. When you delete your account or ask us to delete your data, we remove your personal information and service data within 30 days, except where longer retention is legally required.

8. Data Security

We protect your information with industry-standard safeguards, including: encryption of all network traffic in transit (TLS); encryption of stored notification credentials with AES-256-GCM; hashing of agent enrollment tokens; access controls and least-privilege practices; and routine patching and security review. No method of transmission or storage is ever completely secure, and while we work hard to protect your information we cannot guarantee absolute security.

9. Mobile App

The Ensju mobile companion app (Android and iOS) is view-only for your monitoring data: it signs you in with Clerk and reads from the same API you use on the web, and creating or editing monitors, channels, billing, and organization settings stays on the web. The one change it makes on its own is registering itself to receive push notifications, described below.

What we store on your device. The Clerk session token, in the operating system's encrypted secure store (iOS Keychain with the WHEN_UNLOCKED_THIS_DEVICE_ONLY accessibility class, which keeps it on this device and out of iCloud Keychain replication; Android EncryptedSharedPreferences, excluded from Android Auto Backup). Signing out, deleting your account, or uninstalling the app removes the token. The app also keeps, in ordinary app storage (excluded from Android Auto Backup), your display preferences and a small push-registration record: this installation's push token, its registration id, and the organization it was registered into. That record is cleared when this phone is removed from alerts, which signing out does, and uninstalling the app removes everything the app stored.

What we do NOT collect. No device advertising identifiers (Apple IDFA / Google AAID), no precise or coarse location, no contacts, photos, microphone, or camera access, no clipboard reads. There are no third-party analytics, attribution, or crash-reporting SDKs in the mobile app, and we do not track you across other apps or websites.

Permissions. Network access, to talk to the Ensju API, and notifications. The notification permission is optional and is never requested at install time: the app explains why and then asks the operating system for it only after you have signed in, so that alerts about your own monitors can reach this phone. Declining it, or revoking it later in your device settings, leaves the rest of the app working normally — and on Android the permission the system prompt grants is POST_NOTIFICATIONS, nothing more. No other permission is requested.

Over-the-air updates. When the app launches it checks our update service (Expo Application Services / EAS Update) for a newer JavaScript bundle. That request necessarily discloses your device's IP address, platform, and app version to the update service so it can deliver the correct update; the data is used only to serve app updates — not to profile, advertise to, or track you. EAS Update delivers code: it is not an analytics, attribution, or crash-reporting SDK, so the statement above still holds.

Push notifications — what we store. Push is off until you allow notifications when the app asks. Once you do, the app registers the device with us and we store: the push token the operating system issued for this installation (routed through Expo — an opaque address for this one app on this one device, and nothing else), the platform, the device name you supply or accept, the app version, and the dates the device was registered and last delivered to. Nothing about the device's other apps, its location, or its identity is collected.

Push notifications — what travels in one. A push carries the alert itself: a short title and line of text naming the monitor, server, heartbeat, domain, or dependency and what happened to it, plus a link that opens the right screen in the app. That text necessarily passes through Expo and, from there, Apple Push Notification service (iOS) or Firebase Cloud Messaging (Android) on its way to your device — the same path every push notification on those platforms takes. Those services are listed on our Sub-processors page.

Push notifications — how long we keep it. The registration is kept while the device stays registered. Removing the device in the app, signing out of the app, or deleting the push channel on the web (which removes every device attached to it) deletes it immediately, and deleting your account deletes it with everything else. If the app cannot reach us when you sign out, it tells you, and the registration stays until the device or the push channel is removed. If the notification service tells us a device is gone (uninstalled, or notifications revoked), we stop sending to it and delete the registration 30 days later. Delivery records, which exist so we can detect those dead devices, are kept for 7 days.

Push notifications — how to turn it off. Any of these ends it: turn notifications off for Ensju in your device's system settings; remove the device from the app; or delete the mobile-push channel under Notifications in the web app, which deregisters every phone attached to it. No alert is ever sent to a device that has no registration.

10. Cookies

Inside the Service (the signed-in app) we use only the cookies necessary to operate it — principally the session cookies set by our authentication provider to keep you signed in — with no advertising cookies, third-party ad-network trackers, or cross-site tracking. Our public marketing pages additionally load a third-party visitor-identification script (Leadsy, described under “Information We Collect”) that may set its own cookies; it is not present in the signed-in app or the mobile app.

11. Your Rights

Depending on where you live, you may have the right to access, correct, export, restrict, or delete your personal information, and to object to certain processing. You can update much of your information directly in the app, or exercise any of these rights by emailing privacy@ensju.com. We will respond within the timeframe required by applicable law, and we will not discriminate against you for exercising your rights.

Account deletion. You can delete your Ensju account at any time from the in-app Settings page (web: Settings → Danger zone; mobile companion: Settings → Account management → Delete account). Deletion is self-serve, immediate, and irreversible: active subscriptions are cancelled, any organizations where you are the only member are deleted together with their monitors, servers, channels, status pages, incidents, and subscribers, and your sign-in is removed. We send a confirmation email to your address on file. We retain billing records only to the extent required by tax and accounting law.

12. International Users

The Service is operated from the United States, and your information is processed there. If you access the Service from outside the United States, you consent to that processing.

13. Children

The Service is not directed to children and is not intended for anyone under 16. We do not knowingly collect information from children. If you believe a child has provided us information, contact us and we will delete it.

14. Changes to This Policy

We may update this Policy from time to time. We will post the revised version with a new "Last updated" date and, for material changes, notify you by email or in the app.

15. Contact Us

Questions or requests: privacy@ensju.com, or 17 Solutions LLC, 361 Falls Rd. #663, Grafton, WI 53024, United States.