privacy

Privacy Policy

How we collect, use, and protect your data. Written clearly for developers and account holders.

Last updated: October 28, 2026

This Privacy Policy explains how Trigv collects, uses, stores, and shares information when you use our developer notification service — including the Trigv API (api.trigv.com), web dashboard (app.trigv.com), mobile apps, and related services.

1. Who we are

Data controller: Webtions OU (dba Trigv)
Registered address: Sepapaja 6, Tallinn 15551, Estonia
VAT: EE102051737
Governing jurisdiction: Estonia, European Union
Contact: support@trigv.com

Trigv is a developer notification service. You send events from your products (via API, webhook, or SDK); Trigv delivers push alerts to your registered devices and shows a live delivery feed in the dashboard (status and counts, not message text).

Service URL Purpose
Marketing site trigv.com Product information
API api.trigv.com Event ingest and mobile API
Dashboard app.trigv.com Account, billing, channels, live feed
Mobile apps App stores Push notifications and on-device history

2. Two kinds of people (B2B model)

Trigv is primarily a business-to-business (B2B) service for developers and teams.

Account holders (developers)

If you create a Trigv account, sign in to the dashboard, manage a workspace, or send events via API, you are an account holder. We act as the data controller for your account data, billing information, and workspace configuration.

Notification recipients

If you receive a Trigv push notification on a device because a developer added you to their workspace or you installed the mobile app and subscribed to channels, you are a notification recipient. The developer (account holder) decides what content to send. Trigv processes that content only in transit to deliver the push — we do not store notification title, body, or history on our servers (see section 4).

Developers are responsible for ensuring they have a lawful basis to send notifications to their recipients and for any privacy notices they provide to their own users.

3. Our core privacy model

Your notification history lives on your device. We deliver the alert but don't keep the message on our servers.
Data Server Device
Account, workspace, API keys, channels ✓ —
Registered devices, push provider IDs ✓ —
Event metadata and delivery status (35-day retention), usage counters ✓ —
Notification title, message, description, feed history ✗ ✓

When you send an event to Trigv:

  1. We receive the event, including title and message, temporarily.
  2. We deliver the notification content to our push provider (Google Firebase Cloud Messaging) so alerts reach your devices.
  3. We store metadata only on our servers (event type, level, channel, delivery counts, status).
  4. We do not persist notification title, message, description, raw payload, or searchable history on the server.
  5. Your mobile app stores notification content and history locally in SQLite on the device.

This is a deliberate architectural choice, not an afterthought.

4. What we do not store on our servers

We do not store the following on Trigv platform servers:

Event content may pass through our systems briefly during processing and delivery, then is discarded. Only metadata and delivery tracking records remain.

5. What data we collect and why

5.1 Account and authentication data

What: Name, email address, hashed password, email verification status, timezone, profile avatar URL (if provided), login timestamps, and last login IP address. Your dashboard session is kept in a signed cookie in your browser rather than in a session table on our servers (see section 8).

Why: Create and secure your account, authenticate dashboard and mobile app access, send password reset emails, and provide account settings.

Social login (if enabled): Provider name, provider user ID, provider email, avatar URL, and OAuth tokens (encrypted if stored) when you sign in with Google or other supported providers.

5.2 Workspace and product configuration

What: Workspace name, slug, plan, billing status, settings; workspace membership and roles; channel names, slugs, descriptions, colors, and icons; API key names, prefixes, hashed keys, scopes, last-used timestamps and IPs, revocation records.

Why: Operate the service you configure — route events to channels, enforce plan limits, and manage your developer setup.

We store API keys as hashes only. The full key is shown once at creation and cannot be retrieved afterward.

5.3 Devices and notification subscriptions

What: Device name, platform (mobile, web, etc.), app instance ID, FCM push token, app version, last-seen timestamp; subscription links between your devices and workspace channels; mute/stop preferences.

Why: Deliver push notifications to the correct devices and respect your notification preferences (including "stop notifications" and timed pauses).

5.4 Event metadata and delivery tracking

What: Public event IDs, workspace and channel references, event type (e.g. deployment.completed), severity level, processing status, delivery counts, timestamps, idempotency keys, request trace IDs; per-device delivery status, provider references, and error codes/messages.

Why: Enforce usage limits, show the dashboard live feed (metadata only), debug delivery failures, and maintain short-term operational records.

Retention: Event metadata and delivery statuses are automatically deleted after 35 days. We do not store title, message, or description in these records.

5.5 Billing and usage

What: Billing customer and subscription records (via Creem), plan, subscription status, billing period dates, billing email; monthly event usage counters and limits per workspace; payment provider webhook logs (including raw webhook payloads for support and debugging).

Why: Process payments, manage subscriptions and lifetime deals, enforce plan limits, and resolve billing support issues.

5.6 Support, security, and audit logs

What: Records of significant actions (e.g. API key created, rotated, or revoked; subscription cancellation requests and expiry; account deletion and restoration), with IP addresses, user agents, and related metadata where recorded; counters of recent login, sign-up, and password-reset attempts, keyed by IP address or a hash of the email address, used to block repeated attempts; and logs of our email-list sync with Loops (email address, status, and error message).

Why: Security monitoring, fraud prevention, and customer support.

5.7 Marketing site

The site at trigv.com (marketing pages) uses Webtions Analytics and Piqo Analytics for basic page-view and interaction statistics. Webtions records page views via a beacon request and does not write a cookie to your browser. Piqo may set a first-party piqo_visitor cookie on trigv.com to count returning visitors; it does not use advertising cookies. For details, see our Cookie Policy and Piqo’s privacy policy.

Email addresses on our marketing list, and the email address, first name, plan, and billing status of account holders that we use for lifecycle and marketing emails, are stored with Loops (see section 9). Your contact is removed from Loops when your account is deleted. You can unsubscribe from marketing emails using the link in any message.

5.8 Dashboard analytics, error monitoring, and uptime checks

Webtions Analytics also runs on the web dashboard at app.trigv.com, including its sign-in pages, to record page-view statistics. The script loads from dash.webtions.com.

We use Sentry (EU region) to find and fix errors. Error reports are scrubbed of email addresses and inbound webhook tokens before they are sent, and we do not send cookies, query strings, or request bodies. We use Better Stack to check that our public addresses are reachable and to run our status page at status.trigv.com; it only probes our public URLs.

6. On-device data (mobile apps)

The Trigv mobile apps store notification content and history locally on your device using SQLite. This data does not sync to Trigv servers.

Typical local fields include:

You control this data. It remains on your device until you uninstall the app, clear app data, or delete history within the app (where supported). Uninstalling the app removes local notification history from that device.

7. How we use your data

We use collected data to:

We do not sell your personal data. We do not use notification content for advertising or profiling, because we do not retain that content on our servers.

8. Cookies and sessions (dashboard)

When you log in to app.trigv.com, we set a signed, HTTP-only session cookie (trigv_session) to keep you signed in. It holds your user ID, workspace ID, a token version number, and an expiry time. It does not hold your IP address or user agent, and we do not keep a session table on our servers. The session lasts 2 hours, or 30 days if you choose “Remember me”, and ends earlier if you log out.

We also set a CSRF protection cookie (trigv_csrf) and short-lived cookies for one-time messages and for showing a newly created API key or webhook URL once. These cookies are essential for dashboard functionality. We do not use third-party advertising cookies on the Trigv platform dashboard or API.

For cookies on the trigv.com marketing site (Cloudflare, analytics), see our Cookie Policy. If we add optional non-essential cookies in the future, we will update these policies and, where required, obtain consent.

9. Third-party services (subprocessors)

We use trusted third-party providers to run Trigv. They process data on our behalf under their own terms and privacy policies.

Provider Purpose Privacy / terms
Cloudflare Application hosting (Cloudflare Workers), database (D1, EU jurisdiction), queues, key-value storage, DNS and CDN Privacy Policy
Google Firebase Mobile push delivery Privacy · Terms
Creem Payments, subscriptions, and billing Privacy · Terms
Postmark Transactional email (password reset, signup, billing notices) Privacy Policy
Loops Marketing and lifecycle email, subscriber list (processor) Privacy Policy · Terms
Sentry Error monitoring (EU region; reports scrubbed of email addresses and webhook tokens) Privacy Policy · Terms
Better Stack Uptime monitoring and status page (probes our public URLs only) Privacy Policy · Terms
Apple Mobile push delivery; app store distribution Privacy Policy
Google Mobile push delivery; app store distribution Privacy Policy

When you send an event, notification content is transmitted through mobile push infrastructure (Google Firebase Cloud Messaging, and Apple’s and Google’s push services) solely to deliver the alert. Retention on their side is governed by their policies.

Loops. If you receive marketing emails from Trigv or have an account, Loops processes your email address and related contact data on our behalf. See Loops’ privacy policy for how it handles that data.

We may update subprocessors as our infrastructure evolves. Material changes will be reflected in an updated version of this policy.

10. Data retention

Data category Retention period
Event metadata 35 days, then automatically deleted
Delivery statuses 35 days, then automatically deleted
Inbound webhook delivery records 35 days, then automatically deleted
Account, workspace, API keys, channels, devices While your account is active, plus a reasonable period after deletion for backups and legal compliance
Billing records As long as required for tax, accounting, and legal obligations
Dashboard session Signed cookie in your browser, not stored on our servers: 2 hours, or 30 days with “Remember me”, or until you log out
Login, sign-up, and password-reset attempt counters Counted in windows of 10 to 60 minutes; older entries are cleaned up automatically after 24 hours
Password reset tokens Valid for 60 minutes; deleted when used or replaced by a newer request
Billing webhook logs Retained for support and dispute resolution
Audit logs Retained for security monitoring and support; not deleted automatically

To delete your account, contact support@trigv.com. We will delete or anonymize personal data associated with your account, subject to exceptions for data we must retain by law or for legitimate business purposes (e.g. billing records).

Local notification history on your devices is not deleted by us when you close your account — you must remove it by uninstalling the app or clearing local data.

11. International data transfers

Our main database (Cloudflare D1) is pinned to the European Union. Our application code runs on Cloudflare’s global network, so requests may be handled in data centers near the sender, including outside the EU. Trigv and our subprocessors may also process data in countries other than your own, including the United States and the European Union, depending on provider infrastructure. Error reports go to Sentry’s EU region.

Where required by applicable law, we rely on appropriate safeguards for cross-border transfers (such as Standard Contractual Clauses or equivalent mechanisms offered by our providers).

12. Your rights

Depending on where you live, you may have rights regarding your personal data, including:

To exercise these rights, contact support@trigv.com. We will respond within the timeframe required by applicable law (typically one month under GDPR).

You may also:

If you are a notification recipient and believe a developer is misusing Trigv to send you unwanted alerts, contact the developer who added you. You can also contact us and we will review abuse reports.

European Economic Area (EEA) and UK

If you are in the EEA or UK, you have the rights listed above under the GDPR and UK GDPR. Our legal basis for processing typically includes: contract performance (providing the service), legitimate interests (security, fraud prevention, service improvement), and consent (where applicable, e.g. marketing emails).

You may lodge a complaint with your local supervisory authority. In Estonia, this is the Data Protection Inspectorate (Andmekaitse Inspektsioon).

13. Security

We implement technical and organizational measures appropriate to the nature of the data we process, including:

No method of transmission or storage is 100% secure. If you believe your account or API keys have been compromised, revoke affected keys immediately and contact us.

14. Children

Trigv is not directed at children. You must be 18 years or older (or the age of majority in your jurisdiction) to create an account. We do not knowingly collect personal data from children. If you believe we have collected data from a child, contact us and we will delete it.

15. Changes to this policy

We may update this Privacy Policy from time to time. When we do, we will revise the "Last updated" date at the top. For material changes, we will provide notice through the dashboard, by email, or on trigv.com, as appropriate.

Continued use of Trigv after changes take effect constitutes acceptance of the updated policy, unless otherwise required by law.

16. Contact us

Email: support@trigv.com
Postal address: Webtions OU (dba Trigv), Sepapaja 6, Tallinn 15551, Estonia
Website: trigv.com

17. Previous versions

Privacy Policy, version of June 30, 2026 (valid until October 28, 2026)