Privacy Policy
Provider: MightyS Team
In short
Pulse does not set cookies in apps, does not store IP addresses of app users, and does not collect advertising or device identifiers; from the IP address our server keeps only the country, worked out at the moment a signal is received. If an app sets a user identifier, our SDKs hash it on the device and our server hashes it again with a salt unique to that app. If it does not, our server forms a visitor code that is valid for one day only, so people can be counted without any stored identifier. Data is stored on Hetzner servers in Falkenstein, Germany (EU) and deleted automatically after the period set by the customer's plan. For your Pulse account we keep only what we need to run it, such as your email address, and we never sell data.
Full text
Last updated: 15 November 2026
This policy explains what data MightyS Pulse ("Pulse") handles and why. It has two parts that are kept separate on purpose:
- Part A covers data about our customers: the developers and teams who sign up for Pulse, and visitors to our website. For this data we are the controller.
- Part B covers data that our customers' apps send to Pulse about the people who use those apps ("end users"). For this data our customer is the controller and we are the processor. We handle it only on our customer's instructions, as set out in the Data Processing Agreement.
If you use an app that sends data to Pulse and you have a question about that data, please contact the app's developer first. They decide what is collected and can act on your request. You can also contact us and we will pass your request on.
Who we are
Controller for Part A and processor for Part B: MightyS Team, contact@mightys.dev.
Contact for privacy questions: contact@mightys.dev.
Part A: Data about our customers
A1. What we collect and why
| Data | Where it comes from | Why we use it | Legal basis |
|---|---|---|---|
| Email address, and a normalized form of it (lower case, without "+" tags; for Gmail also without dots) | You, when you sign in | To create your account, send sign-in codes and service notices, and to keep one Free plan per person | Contract; legitimate interest in preventing abuse of the Free plan |
| One-time sign-in codes | Generated by us | To sign you in. We store only a hash of the code. A code is valid for 10 minutes and can be tried at most 5 times | Contract |
| Sign-in provider identifier and verified email (Google, Apple, GitHub) | The provider, when you choose to sign in with it | To link the provider to your account. We link automatically only when the provider says the email is verified. An Apple private relay address is treated as a normal email | Contract |
| Organization, team members and roles, apps and their names, app keys, plan and plan version, reservations | You, when you use the dashboard | To provide the service | Contract |
Session cookie (pulse_session) |
Set by our dashboard | To keep you signed in. It is the only cookie we set | Contract; strictly necessary |
| Hashed IP address at sign up | Your connection, when you create an account | To limit how many accounts can be created from one network in 24 hours and to spot repeated Free accounts. We never store the raw IP address. We store a keyed hash (HMAC) made with a secret only our server knows, and delete it after 30 days | Legitimate interest in preventing abuse |
| Review records for possible repeated Free accounts | Our own checks, which compare normalized email, hashed sign-up IP, email domain and usage near the Free limit | So that a person can review groups that look like one person with many Free accounts. Nothing is blocked automatically. Decisions are made by a person and logged | Legitimate interest in preventing abuse |
| App bundle identifier and, for Android, a hash of the app signing certificate | Sent by our Unity SDK only when the developer turns this option on | To recognize the same publisher across Free accounts, as a signal for manual review. This identifies an app, not an end user | Legitimate interest in preventing abuse |
| Usage information: signals per account and app, formats and SDK versions used, storage size, sign-ups and activity per day | Our servers | To run the service, enforce plan limits, plan capacity, set prices and see how Pulse is used | Contract; legitimate interest |
| Feature votes | You, when you vote for a coming feature | To decide what to build next | Legitimate interest |
| Support messages | You, when you write to us | To answer you | Contract; legitimate interest |
| Visit statistics for our website and dashboard (see A6) | Your browser, when you open our pages | To know how many people visit, which pages they read and how many of them go on to sign up | Legitimate interest |
| Billing data (once paid plans start) | The merchant of record (see A3) | To know which plan you paid for and until when | Contract; legal obligation |
We do not use third party analytics, advertising or tracking on our website or dashboard, and we do not load fonts or scripts from other sites when our pages open. We count visits with Pulse itself, as described in A6.
A2. Email
We send emails for sign-in codes and links, important notices about your account and plan, and, when billing opens, messages about your reservation. We send these emails through Resend (Resend, Inc., United States company; sending region Ireland (EU)), from the sending domain send.pulse.mightys.dev. To deliver an email, Resend receives the recipient email address, the content of the email (for example a one-time sign-in code or sign-in link) and delivery metadata such as timestamps and delivery status. Resend does not receive any analytics signal data. We do not send marketing emails without your consent.
A3. Payments (future)
Paid plans are not available yet. When they are, payments will be handled by a merchant of record: Paddle. The merchant of record sells the subscription to you and is the controller of the payment data it collects, such as your card or PayPal details, billing address and tax information. Its own privacy policy applies to that data.
We will never see or store your full card number. From the merchant of record we expect to receive the information we need to manage your plan: a customer and subscription reference, the plan and price you bought, payment status, amounts and currency, and the date your paid period ends.
A4. How long we keep it
- Account data: for as long as your account exists. After the account is closed it is deleted within 30 days, except what we must keep by law.
- Sign-in codes: 10 minutes, then unusable.
- Email delivery logs at Resend: for the period set by Resend's own log retention.
- Hashed sign-up IP: 30 days.
- Records of admin changes to plans and settings: kept permanently, because they are our record of what changed and why.
- Billing records: as long as tax and accounting law requires.
- Support messages: 24 months after the last message.
- Server backups: our hosting provider makes a daily backup of the server and keeps the seven most recent ones. Data that we delete leaves the backups when they are replaced, within about eight days.
A5. Who we share it with
We share data only with the service providers listed in the "Subprocessors" section below, with the merchant of record when billing starts, and with authorities when the law requires it. We do not sell personal data.
If Pulse is transferred to a successor, for example a company we form to run it, your data would be transferred with it. The successor would have to keep the promises in this policy, and we would tell you before the transfer.
A6. Visitors to our website
Our website and dashboard do not use third party analytics, advertising or tracking, and they set no cookie other than the session cookie described in A1, which is set only when you sign in. Your browser necessarily sends its IP address and usual request headers to our server when a page loads; access logging on our web proxy is turned off, so these are not written to an access log.
We count visits to our website and dashboard with Pulse itself, the same way our customers count use of their apps. When a page opens, it sends a signal with the path of the page (for example /pricing/), the name of the site that linked to it (only the host, such as example.com, never the full address), and a random session identifier that changes after 30 minutes without activity. A few clicks are counted the same way: Start free, Sign in, choosing a plan, opening a package page, the contact address and the code tabs in the docs. The dashboard also counts, without any detail about you, when its sign-in page opens, when an account is created and when a new app receives its first signal. No cookie is set for this, no user identifier is sent, and nothing links these signals to your account. Our server derives a country from the IP address when a signal arrives and then discards the address, as described in B2. Your browser keeps a short queue of signals not yet sent, and your choice if you turn counting off, in its local storage for our site. To stop being counted in a browser, open https://pulse.mightys.dev/?count=off; to be counted again, open https://pulse.mightys.dev/?count=on.
A7. Automated decisions
We do not make decisions about you that are based only on automated processing and that have legal or similarly significant effects. Checks for repeated Free accounts only prepare cases for review; a person decides, and the decision is logged.
Part B: Data our customers send about their end users
In this part, "you" means the end user of an app that uses Pulse, and "customer" means the developer of that app.
B1. Our role
Our customer decides whether to use Pulse, what to send and why. We process that data only to provide Pulse to the customer: to receive it, store it, summarize it and show it to the customer. We do not use it for our own purposes, we do not combine it across customers, we do not sell it and we do not use it for advertising.
B2. What an app can send
Pulse accepts signals in its own format (v1) and in two compatible formats used by other analytics SDKs. Every signal is sent with the app's key, which tells us which app it belongs to. The fields are:
| Field | Required | What it is |
|---|---|---|
| Timestamp | Yes | When the event happened, in UTC. It must be no older than 30 days and no more than one hour in the future |
| Type | Yes | The name of the event chosen by the developer, for example level.complete. Up to 200 characters |
| Value | No | One number chosen by the developer |
| Debug flag | No | Whether the signal came from a development build |
| Session ID | No | A random value created by the SDK for one run of the app. Our SDKs start a new one after 30 minutes without activity |
| User hash | No | A hashed user identifier, sent only if the developer sets one. Our SDKs compute a SHA-256 hash of the identifier on the device and never send the raw identifier. When no identifier is sent, our server stores a daily visitor code instead, described below |
| Platform, OS name, OS version | No | For example mobile, iOS, 18.0 |
| App version and build number | No | The version of the app |
| Device model | No | A model code such as iPhone16,1 |
| Locale | No | Language and region setting, such as sr-RS |
| SDK name and version | No | Which SDK sent the signal |
| Properties | No | Key and value pairs chosen by the developer (by default up to 32 are kept). Values are text or numbers |
In the compatible formats, the same kinds of fields arrive under different names, and system information can arrive inside the properties. One compatible format has no user identifier at all.
Added by our server
| Field | What it is |
|---|---|
| Country | A two letter country code (ISO 3166-1, such as DE), derived by our server when the signal is received. It is looked up from the IP address of the connection in a geolocation database stored on our own server (DB-IP IP to Country Lite). No other service is contacted. The IP address is discarded right after the lookup; only the country code is stored with the signal |
Our Unity SDK can also send the app's bundle identifier and, on Android, a hash of the app's signing certificate, but only if the developer turns this on. These describe the app, not you.
What Pulse does not collect
- No IP addresses are stored. Your device's IP address is necessarily visible to our server while a request is being received, as with any internet connection. Our server does not write it to the database, our ingest code does not log it, and access logging on our web proxy is turned off. When a signal is received, our server uses the IP address once to look up the country in a local database, then discards it; only the country code is stored. We do not determine a city, region or precise location.
- Daily visitor code. When an app or browser sends no user identifier, our server forms a visitor code from the network address and device or browser details, using a key that is valid for one day and deleted when the day ends (UTC). The address itself is not stored, and codes of different days cannot be linked, so a person is counted at most once per day and app.
- No cookies, advertising identifiers (such as IDFA), vendor or hardware identifiers, or persistent device identifiers are collected by our SDKs.
- No fingerprinting: our SDKs do not collect screen, font, canvas or similar information.
- No page URLs, referrers, page titles or automatic clicks. Our SDKs send only events the developer chooses to track.
- No raw user identifiers. If a developer sets one, our SDKs hash it on the device first.
A browser may send its usual User-Agent header with a request. Pulse does not use it to fill any field, and it is not part of the stored signal.
Developers control the properties and event names. Our documentation tells developers not to put personal data there, but we cannot check what they choose to send. If you think an app sends personal data about you, please contact its developer.
B3. How we protect identifiers
- User hash. If an app sends a user hash, our server hashes it again before storing it: SHA-256 of the received value combined with a random salt that is unique to each app, shortened to 16 bytes. The salt is kept on our server. The value we receive is never stored. The same person therefore gets a different stored value in every app, and the stored value cannot be matched to the original identifier without the salt.
- Session ID. Our server replaces the session ID with a hash made from the app's ID and the session value, shortened to 8 bytes. The raw session ID is not stored. This hash is scoped to one app but does not use a secret salt.
- A hashed identifier is still a pseudonymous identifier. It can link several events from the same device session or the same user within one app. That is why we treat Part B data as personal data.
B4. Where it is stored and how long
Signals are stored in our databases on servers of Hetzner Online GmbH in Falkenstein, Germany (EU).
We keep two kinds of data:
- Raw signals (each signal as listed above, with the hashed identifiers): deleted automatically when they reach the age set by the customer's plan, counted from the time of the event.
- Daily summaries: counts per day by event type, app version, OS, OS version, device model, locale, platform, ingest format and SDK and country, plus estimated numbers of distinct users and sessions per day. They do not contain properties. The distinct estimates are compact counting structures built from the hashed identifiers; for small numbers of users or sessions such a structure can contain hashes derived from those hashed identifiers. Daily summaries are deleted automatically after the period set by the plan.
These periods are part of each plan and are shown on the live pricing page. The period that applies to a signal is recorded when the signal is stored, so data that is already stored keeps the period it was stored with if the customer later changes plan.
We also keep a monthly count of signals per app and account, without any end user data, to apply plan limits.
If an app sends no signals for 12 months or longer, we may warn the customer by email and then delete its raw signals.
B5. Deletion
- When a customer's plan period ends for a signal, it is deleted automatically, as described above.
- When a customer deletes an app or closes their account, we delete its data within 30 days.
- Requests from end users. Because we store only salted hashes and no names, emails or IP addresses, we usually cannot find your data from your name or email. The app's developer can help, because only the developer knows which identifier their app uses. When a developer asks us to delete the signals of one user, we do it by hand and aim to finish within 30 days.
B6. Rights of end users
Depending on where you live, you may have the right to access, correct, delete or restrict the use of your data, to object, and to receive a copy of it. For Part B data, please send these requests to the developer of the app. If you send one to us, we will forward it to the developer and help them answer it as described in the Data Processing Agreement.
On your device, apps that use our SDKs can offer an opt-out. When it is on, the SDK stops collecting, clears any signals that have not been sent yet and stops sending. Signals already sent cannot be recalled by the SDK.
B7. Data kept on your device
Our SDKs keep a queue of unsent signals on the device so that they can be sent later if there is no connection. In a browser this is in local storage; in Node.js and Unity it is a file. The queue is not encrypted. It holds at most the newest signals up to a set count and age (by default 1000 signals and 7 days). Our SDKs never store the raw user identifier in this queue.
Shared sections
Subprocessors
| Provider | Purpose | Location |
|---|---|---|
| Hetzner Online GmbH | Server hosting for the website, dashboard, databases and ingest | Falkenstein, Germany (EU) |
| Resend (Resend, Inc.) | Delivery of transactional email (sign-in codes and links, invitations, service notices) from send.pulse.mightys.dev. Data processed: recipient email address, email content such as one-time sign-in codes and links, delivery metadata such as timestamps and delivery status. Part A only; no analytics signal data. Retention: Resend's own log retention | United States company; sending region Ireland (EU). Resend processes this data under its own data processing terms |
| Paddle (from when billing starts) | Payments, invoices, sales tax (Part A only). It acts as an independent controller for payment data | United Kingdom and other countries where the Paddle group operates, under Paddle's own terms |
| Google, Apple, GitHub | Optional sign-in, only if you choose it (Part A only). Each acts under its own terms and privacy policy | United States and other countries where these companies operate |
The transfer basis for each provider is listed in Annex 3 of the Data Processing Agreement. We will update this list before we add a new subprocessor that handles Part B data, as described in the Data Processing Agreement.
Security
We use these measures, described in more detail in the Data Processing Agreement: salted hashing of user identifiers, hashing of session identifiers, no storage of IP addresses, separate keys for each app, automatic deletion by retention period, databases that are not exposed directly to the internet in our standard setup (only our web proxy accepts connections), and no logging of request bodies, identifiers or keys by our ingest code. Our SDKs send data to an HTTPS address by default. No system is perfectly secure; if a breach affects your data, we will act as described in the Data Processing Agreement and the law.
International transfers
Our servers are hosted by Hetzner in Falkenstein, Germany (EU), and the data stays there. The service is operated from Serbia, which is outside the European Economic Area; our administrative access from Serbia is covered by the EU Standard Contractual Clauses in the Data Processing Agreement. Some providers listed above may process customer account data in other countries, under their own terms. Resend (Resend, Inc., United States company; sending region Ireland (EU)) processes the email address and email content needed to deliver our emails.
Your rights as a customer (Part A)
You can ask us for access to your data, to correct or delete it, to restrict or object to its use, and for a copy of it. You can also complain to a data protection authority, for example the Commissioner for Information of Public Importance and Personal Data Protection in Serbia, or the authority where you live in the EU. Write to contact@mightys.dev. We will answer within 30 days.
Where we rely on your consent, you can withdraw it at any time; this does not affect what was done before. Where we rely on our legitimate interest, you can object, and we will stop unless we have strong reasons that the law accepts. Before we act on a request, we may ask you to confirm that you control the email address of the account, so that we do not give your data to someone else. Requests are free of charge, unless they are clearly unfounded or excessive.
Residents of other regions
Some laws outside Europe, for example the privacy laws of some US states, give you rights such as knowing what data is collected, asking for deletion and opting out of the sale or sharing of personal data for targeted advertising. We do not sell personal data and we do not share it for targeted advertising, in Part A or in Part B. You can use the rights above by writing to contact@mightys.dev, and we will not treat you differently for doing so.
Children
Pulse is a service for developers and is not meant for children. You must be at least 18 to create an account. Developers whose apps are used by children are responsible for following the laws that protect them.
Changes to this policy
We will post changes here and update the date at the top. For important changes we will email account owners before they take effect.
Contact
MightyS Team, contact@mightys.dev
Questions about this document: contact@mightys.dev