Privacy

This sample notice is dated September 1, 2026 and describes the fictional Tern service. The demonstration does not connect to a live app or checkout. Its app links use placeholder addresses. This text must be matched to a real service’s data handling before publication.

Information an account needs

In a working service, we would collect an account email, member names, alert phone numbers and billing contact details. We would store check URLs, check settings, response results, heartbeat times and incident updates. Support messages would include the information you choose to send us.

Avoid putting personal information in check names, query strings or public incident updates. Where a check needs a credential, use a token limited to that check’s purpose. A status page is public, including any service names and incident text you publish there.

Why we use it

We would use account information to provide access, route alerts and answer support requests. Check results would support incident confirmation, response-time charts, reports and exports. Billing records would support subscriptions, refunds and required accounting. A final notice would state the legal basis for each use, including contract performance, legal obligations and any assessed legitimate interests.

Account data, check history and incident records would be stored in the EU in Frankfurt. Monitoring workers in Frankfurt, London, Virginia, Oregon, Singapore and Sydney would process the endpoint and settings needed to run checks. Monitoring requests may therefore reach your service from outside the EU.

Alert providers would receive the contact details and message content needed for email, SMS or phone delivery. Your payment provider would process card details; Tern would keep the invoice and payment reference rather than the full card number. A real notice must identify providers and explain any international transfer arrangements.

Retention and choices

Business includes 13 months of check history. Other plan retention periods would be stated in account settings before purchase. We would remove results after their retention period and explain how long deleted information remains in backups. Accounting records may need to remain longer than an account under applicable requirements.

You could change contact details, remove members and export available results from the app. Requests for access, correction or deletion could be sent to hello@tern.example.com. We would verify account ownership before releasing or deleting information and explain any records we must retain.

This demonstration site

The theme as supplied does not enable analytics or a contact form service. A deployed service must document its actual cookies, hosting logs and optional integrations. Adding analytics requires updating this notice and providing any choices required for that use. Contact hello@tern.example.com with privacy questions; do not include passwords or API tokens in your message.