Data Processing Agreement
Provider: MightyS Team
In short
This agreement covers the data your apps send to Pulse about their end users: you are the controller, MightyS Team is the processor and handles that data only on your instructions. It is part of the Terms of Service and applies automatically when you accept them; no signature is required, and a signed copy is available on request. Annex 2 lists the security measures, and Annex 3 lists the subprocessors with where they are and the transfer basis. We tell you about breaches, help with end user requests, and delete data at the end of its retention period or when you close your account.
Full text
Last updated: 15 November 2026
1. Parties and how this agreement applies
- Controller: the customer who uses MightyS Pulse ("Pulse") for its apps ("Customer").
- Processor: MightyS Team ("Provider"), contact@mightys.dev.
This agreement is an integral part of the Pulse Terms of Service. It applies automatically when the Customer accepts the Terms, and covers all personal data the Customer's apps send to Pulse. No signature is required. A copy signed by the Provider is available on request at contact@mightys.dev.
Terms used. "Personal data", "processing", "controller", "processor", "data subject", "personal data breach" and "supervisory authority" have the meaning given in the GDPR (Regulation (EU) 2016/679) and, where it applies, the Serbian Law on Personal Data Protection. "End user" means a person who uses one of the Customer's apps. "Subprocessor" means another processor the Provider engages to process end user data covered by this agreement.
2. Subject matter, duration, nature and purpose
- Subject matter: receiving, storing, summarizing and displaying usage events ("signals") that the Customer's apps send to Pulse.
- Duration: for as long as the Customer uses Pulse, plus the time needed for deletion under section 10.
- Nature: collection from the Customer's apps (over HTTPS by default), validation, pseudonymization of identifiers, storage, aggregation into daily summaries, display in the dashboard, export at the Customer's request, and automatic deletion.
- Purpose: to give the Customer analytics about the use of its own apps. The Provider does not process the data for its own purposes, except to keep counts of signals per account that are needed to apply plan limits and bill for the service.
3. Categories of data subjects
End users of the Customer's apps and games.
4. Categories of personal data
Only what the Customer's apps send, which can include (field list from the Pulse ingest contract):
- event timestamp, event type, an optional numeric value and a debug flag;
- a session identifier generated by the SDK, stored only as a hash (see section 7);
- an optional user identifier, which Pulse SDKs hash on the device before sending, stored only as a salted hash (see section 7);
- platform, operating system name and version, app version and build number, device model code, locale, SDK name and version;
- custom properties chosen by the Customer (text or numbers);
- the app's bundle identifier and an Android signing certificate hash, when the Customer enables this in the Unity SDK. These identify the app, not an end user;
- a two letter country code, derived by the Provider's server at receipt from the IP address of the connection (see section 7). It is not sent by the app.
Pulse does not store IP addresses and does not collect cookies, advertising identifiers or persistent device identifiers.
Data source for the country code: DB-IP IP to Country Lite, a geolocation database licensed under Creative Commons Attribution 4.0. A copy is stored on the Provider's own server and the lookup runs there. DB-IP receives no data, so it is a data source and not a subprocessor.
Special categories: none are intended. The Customer must not send special categories of data (such as health data), data about criminal offences, or direct identifiers (such as names, email addresses or phone numbers) in any field.
5. Customer's instructions and responsibilities
- The Terms, this agreement and the Customer's settings in the dashboard (apps, plan, data retention given by the plan, deletion, export) are the Customer's documented instructions.
- The Customer is responsible for the lawfulness of the data it sends, for informing its end users, for obtaining consent where required, and for connecting the SDK opt-out to its app's consent or settings where needed.
- The Provider will tell the Customer if it believes an instruction breaks data protection law.
6. Provider's obligations
The Provider will:
- process the data only on the Customer's documented instructions, unless the law requires otherwise (in which case it will tell the Customer first, if the law allows);
- make sure that anyone with access to the data is bound by confidentiality;
- apply the security measures in section 7;
- use subprocessors only as set out in section 8;
- help the Customer answer requests from data subjects (section 9);
- help the Customer with data protection impact assessments and consultations with authorities, as far as reasonable and taking into account the information available to the Provider;
- notify personal data breaches as set out in section 11;
- delete or return data as set out in section 10;
- make available the information needed to show compliance with this agreement and allow audits as set out in section 12;
- not sell the data, not use it for advertising and not combine it with data of other customers;
- tell the Customer without undue delay if it can no longer meet its obligations under this agreement. The Customer may then stop sending data, and may end its use of Pulse if the problem is not fixed within a reasonable time.
7. Security measures
The following measures are in place.
Pseudonymization of identifiers
- User identifiers: Pulse SDKs send only a SHA-256 hash of the identifier. The server hashes the received value again with a random salt that is unique to each app (SHA-256, truncated to 16 bytes). The received value is never written to storage.
- Session identifiers: the server replaces the session value with a SHA-256 based hash scoped to the app (truncated to 8 bytes). The received value is never written to storage. This hash does not use a secret salt.
Data minimization
- IP addresses are not stored with signals. Ingest code does not log IP addresses, request bodies, identifiers or keys. Access logging on the web proxy is not enabled.
- Country only: at receipt, the server looks up the country of the connection's IP address in the local DB-IP database and keeps only the two letter country code with the signal. The IP address is discarded immediately after the lookup. No city, region or coordinates are derived, and no external service is called.
- Pulse SDKs collect no cookies, advertising identifiers, persistent device identifiers, fingerprinting data, page URLs or automatic interactions.
- Limits on input: at most 1000 signals and 1 MB per request, 8 KB of properties per signal, and by default at most 32 property keys per signal. Event names are limited to 200 characters.
Access control and separation
- Each app has its own keys. A signal is accepted only with a known app key, and all stored rows carry the app's ID.
- In the standard setup, only the web proxy accepts network connections; the databases are not exposed directly. Database credentials are not kept in the source repository.
- Dashboard access requires sign-in with a one-time code (stored only as a hash, valid 10 minutes, at most 5 attempts) or a supported sign-in provider. The code or link is delivered by email through the subprocessor Resend (Annex 3). Roles within an organization: owner and member.
- Admin changes to plans and limits require a preview and a written reason, and are recorded in an audit log that is not edited or deleted.
Physical security
- The servers run in a Hetzner Online GmbH data center in Falkenstein, Germany. Physical access control and the protection of the building are provided by Hetzner under its own measures; the Provider has no physical access to the hardware.
Encryption in transit
- Pulse SDKs send data to an HTTPS address by default, and the Pulse website, dashboard and ingest address are served over HTTPS.
Encryption at rest
- Stored data is protected by access control on the server and the separation described above. It is not additionally encrypted at rest.
Retention and deletion
- Each raw signal and each daily summary row stores its retention period when it is written. Raw signals are deleted automatically when their event time passes that period. Daily summaries are kept for a longer period and then deleted automatically. The periods come from the plan; the live pricing page shows them for each plan.
Availability and resilience
- Accepted signals are buffered in memory and written to the database in batches, normally within seconds. An orderly restart drains the buffer before stopping. A crash can lose signals that were accepted but not yet written.
- Rate limits per app and protection against oversized or slow requests.
- Backups: the hosting provider makes a daily backup of the whole server and keeps the seven most recent ones. Signals received after the latest backup can be lost in a server failure.
8. Subprocessors
The Customer gives general authorization for the Provider to use the subprocessors listed in Annex 3, and further subprocessors under the rules below.
The Provider will give the Customer at least 30 days notice of a new subprocessor for end user data, by email or in the subprocessor list of the Privacy Policy. The Customer may object on reasonable data protection grounds. If the parties cannot resolve the objection, the Customer may stop using Pulse and receive a pro rata refund of prepaid fees. The Provider will bind each subprocessor to data protection terms that are at least as protective as this agreement and remains responsible for it.
9. Help with data subject requests
- Pulse does not store names, email addresses or IP addresses of end users, so it usually cannot identify an end user from a request alone. The Customer is best placed to link a request to the identifier its app uses.
- If the Provider receives a request directly, it will forward it to the Customer without undue delay and will not answer it itself, unless the Customer instructs otherwise.
- When the Customer asks for the signals of one user to be found or deleted and gives the identifier its app uses, the Provider does this by hand and aims to finish within 30 days.
10. Deletion and return of data
- During the service, data is deleted automatically when it reaches the retention period of the Customer's plan.
- The Customer can export its data from the dashboard before the end of the service, as CSV.
- When the Customer deletes an app or closes its account, the Provider will delete the related data within 30 days, unless the law requires it to keep some of it. Deleted data leaves the server backups when they are replaced, within about eight days after that.
- At the Customer's request, the Provider will confirm deletion in writing.
11. Personal data breaches
The Provider will notify the Customer without undue delay, and in any case within 48 hours, after becoming aware of a personal data breach that affects the Customer's data. The notice will describe, as far as known, what happened, the data and number of data subjects concerned, the likely consequences and the measures taken or proposed. The Provider will update the Customer as more becomes known and will help the Customer meet its own notification duties.
12. Audits and information
- The Provider will make available the information reasonably needed to show compliance, including this document, a current list of subprocessors and a description of security measures.
- The Customer may audit compliance, by itself or through an independent auditor bound by confidentiality, at most once per year, with at least 30 days notice, at the Customer's cost, unless a breach or an authority requires otherwise.
- The servers are in a data center the Provider cannot enter, so an audit is normally done through written answers to the Customer's reasonable questions and the documents listed above.
13. International transfers
End user data is stored on servers of Hetzner Online GmbH in Falkenstein, Germany (EU). The Provider operates from Serbia and accesses the servers from there for administration and support. That access is covered by the EU Standard Contractual Clauses, which are incorporated into this agreement by reference. The transfer basis for each subprocessor is shown in Annex 3.
14. Liability and order of precedence
Liability under this agreement follows the limits in the Terms of Service, unless the law does not allow it. If this agreement conflicts with the Terms on data protection, this agreement wins. If the Standard Contractual Clauses referred to in section 13 conflict with this agreement, the Standard Contractual Clauses win.
15. Duration, end and survival
This agreement starts when the Customer accepts the Terms and ends when the Provider no longer processes any end user data for the Customer, after the deletion described in section 10. The duties of confidentiality and security continue for as long as the Provider holds any of that data. The Provider may update this agreement under the change rules of the Terms; an update may not lower the protection of end user data without the notice described there.
16. Governing law
This agreement follows the governing law and courts set out in the Terms of Service (Republic of Serbia, court in Belgrade). This does not affect mandatory data protection law, the rights of data subjects or supervisory authorities, or the governing law and forum clauses of the Standard Contractual Clauses.
Annex 1: Details of processing
Parties: section 1 above. Subject matter, duration, nature and purpose: section 2. Data subjects: section 3. Categories of data: section 4. Retention: section 7 ("Retention and deletion") and the plan shown on the pricing page.
Annex 2: Technical and organizational measures
Section 7 above.
Annex 3: Subprocessors
| Name | Service | Data | Location | Transfer basis |
|---|---|---|---|---|
| Hetzner Online GmbH | Hosting of servers and databases for ingest, dashboard and website | End user data covered by this agreement; customer account data | Falkenstein, Germany (EU) | Within the EU, no transfer tool needed. Administrative access by the Provider from Serbia: EU Standard Contractual Clauses (section 13) |
| Resend (Resend, Inc.) | Delivery of transactional email (sign-in codes and links, invitations, service notices) from the sending domain send.pulse.mightys.dev | Customer account data only: recipient email address, email content such as one-time sign-in codes and links, delivery metadata such as timestamps and delivery status. No analytics signal data and no end user data. Retention: Resend's own log retention | United States company; sending region Ireland (EU) | Resend's own data processing terms |
| Paddle (from when billing starts) | Merchant of record: payments, invoices, sales tax | Customer billing data only; no end user data. Paddle acts as an independent controller for the payment data it collects | United Kingdom and other countries where the Paddle group operates | Independent controller under its own terms |
Optional sign-in providers (Google, Apple, GitHub) receive no end user data and are described in the Privacy Policy.
Questions about this document: contact@mightys.dev