Pulse Privacy Policy

1. Who operates Pulse

Mark Mottian is the independent developer responsible for Pulse. Daepoimyr is a publishing brand, not a registered company. Questions or privacy requests may be sent to pulse.gameplay.team@gmail.com.

2. Information stored on your device

Depending on the features and platform you use, Pulse stores game progress, level completion and progression, scores and accuracy, your Daily first-run result, preferences and settings, your analytics-consent choice, notification preferences and reminder time where applicable, an opaque installation identity, a signed entitlement cache, and Pulse Premium progression in the Android app.

This local information supports gameplay, preferences, reminders, and offline entitlement checks where applicable. It is not cloud account sync. It normally remains until you clear Pulse's local app or site data or uninstall the app, subject to browser, operating-system, backup, or device behavior outside Pulse's control. Web progress remains in local site storage.

3. Optional analytics

On Web, Pulse sends a limited set of product usage events to a dedicated Supabase-hosted ingestion service only after you expressly allow analytics. This helps us understand engagement, diagnose usage patterns, and improve Pulse. Events cover sessions, Home and Levels visits, Core starts, attempts, results and explicit exits, Daily starts and results, tutorial completion, user-initiated Daily/Core sharing actions, coarse incoming share attribution, and fixed categories of major runtime errors. They may include level or Daily identifiers, attempt counts, accuracy, share surface and first-run/replay type, and app version. They do not include tap coordinates, free-form error text, personal referral identifiers, or saved progress files. Web does not initialize GameAnalytics.

Only after Web consent is allowed, Pulse creates a random anonymous analytics identifier in local site storage, separate from game progress. Clearing site data resets it. Before consent, or after a decline, Pulse creates no Web analytics identifier and sends no analytics requests. Withdrawing consent stops future analytics transmission and removes the local Web analytics identifier without clearing gameplay progress. Analytics failures do not affect play. Pulse does not fingerprint your browser or use analytics for advertising, cross-site profiling, or sale of personal information.

In the Android app, Pulse uses GameAnalytics only if you are at least 18 and expressly allow analytics. GameAnalytics does not initialize or transmit analytics while your age is unknown, you are under 18, you prefer not to say, or your consent is unknown or declined. Analytics is not required to play, and eligible adults can change their choice later in Settings.

The Android age check evaluates the date of birth locally and stores an age category, not the date of birth. Pulse does not send the date of birth to GameAnalytics.

When enabled in the Android app, analytics may include gameplay and activity events, session information, progression and interaction events, the Pulse build or app version, device model, platform and operating-system metadata, pseudonymous random app, session and event identifiers, Google App Set ID when available, and coarse geographic information that GameAnalytics derives from IP or network information. Purchase and restore interactions and limited purchase or entitlement states, such as pending, purchased, verifying and verified, are also sent after analytics consent. These events and identifiers help understand engagement, gameplay and the purchase flow, diagnose patterns, and improve Pulse. Pulse does not send purchase tokens, receipts, order IDs or payment details to GameAnalytics.

Pulse does not provide GameAnalytics with your real name, a Pulse account email address, phone number, contacts, or precise GPS location. Pulse does not request Android's advertising-ID permission and is not configured to intentionally collect the Google Advertising ID.

4. Pulse Premium and Android purchases

Pulse Premium is an optional, one-time, non-consumable in-app product in the Android app that unlocks 100 levels. Google Play processes the payment. Pulse does not receive or store your payment-card details. Web does not offer Pulse Premium commerce.

To verify, acknowledge, restore, and maintain legitimate ownership, Pulse and its backend process information such as the product ID, Google Play purchase token during verification, a stored hash of that token, purchase and acknowledgement state, Google Play order ID when returned, purchase time, an opaque installation identity or hash, entitlement status, entitlement issuance or expiry information, and related security and audit lifecycle events. The backend also processes relevant refund, revocation, voided-purchase, and reported purchase lifecycle changes using Google Play Real-time Developer Notifications and Voided Purchases reconciliation.

Purchase and entitlement checks, including automatic ownership reconciliation, are separate from optional analytics and can run when analytics is off. Declining analytics does not disable the verification needed to provide or restore Premium access.

5. Play Integrity and security checks

Supported Android builds use the standard Google Play Integrity service for sensitive commerce flows. Integrity checks help prevent fraud, verify purchases, and assess app and device authenticity. Pulse and its backend may process an integrity token, request details, verification results, and related technical and security information for those purposes. Google performs part of this processing. Pulse does not receive your Google password. Web does not use Google Play Integrity.

6. Daily Pulse backend

Pulse uses Supabase-hosted backend infrastructure to retrieve Daily puzzles. No Pulse account is required. When your device or browser requests a Daily puzzle, routine service information may be processed, including request time, IP or network information, technical request metadata, and operational logs. This information is used to deliver, secure, maintain, and troubleshoot the service—not for advertising.

7. Notifications

On supported native builds, if you enable Daily reminders, Pulse schedules them locally on your device using your selected preferences and time. Pulse does not currently use remote push notifications or a remote push token for Daily reminders. You can change reminders in Settings and control notification permission through your device settings. Web does not use notification APIs.

8. Sharing gameplay results

On supported native builds, when you choose to share a Daily result, Pulse creates the share content locally and opens the system share sheet. On Web, you may choose to preview, share, copy a link to, or download a locally generated Daily or Pulse Core result card. Pulse does not automatically upload the card to a Pulse social server. A native share action hands the content to the app or service you choose; that recipient has its own privacy practices, which Pulse cannot control after handoff.

Web share links carry only a coarse source value, daily-share or core-share, and no personal referral identifier. Pulse analyzes incoming share attribution only when you allow optional analytics. Sharing itself does not require analytics consent and introduces no advertising tracking.

9. Support communications

If you contact support, you voluntarily provide your email address, message, and anything else you choose to include, such as device model, operating-system version, browser, Pulse version, or issue context. This information is used to respond, troubleshoot, protect the service, and keep an appropriate support record.

Do not send passwords, payment-card information, raw purchase tokens, Integrity tokens, service-account credentials, private keys, or other private credentials. See the Pulse Support page for help.

10. Why information is processed

Pulse processes information as needed to provide game features; save settings and progress; deliver Daily puzzles; schedule local reminders where supported; process and restore native entitlements; prevent fraud and misuse; protect app, device, and backend integrity; operate, troubleshoot, and improve Pulse; provide optional consent-based Web and native analytics to understand engagement and improve the game; respond to support requests; meet legal obligations; and establish or defend legal claims.

11. Service providers

Pulse relies on the following providers, which process information under their own applicable terms and privacy commitments:

• Google — Google Play distribution and Billing, Play Integrity, purchase lifecycle information, and support email hosting.
• Supabase — backend infrastructure for Daily Pulse and native commerce verification, plus dedicated first-party Web analytics ingestion and storage after Web consent.
• GameAnalytics — optional analytics on supported native builds after consent only; it is not initialized by Web.
• GitHub Pages — hosting this legal and support site. GitHub states that it logs visitors' IP addresses for security.
• Cloudflare — hosting the app-linked information pages at pulse.daepoimyr.com/app/. Hosting services can process routine request information such as IP addresses to serve and secure their services.

These legal pages contain no tracking scripts or analytics and intentionally set no cookies. Hosting providers may still process routine technical information needed to serve and secure their services.

12. No sale and no targeted advertising

Pulse does not sell personal data, contains no advertising, and does not use personal data for targeted advertising.

13. Retention

Retention depends on the type of information and why it is needed. Local data generally remains until you clear the app or site data or uninstall Pulse. Pulse's Supabase analytics storage has an active 90-day deletion schedule for optional Web analytics events. Optional Android analytics is retained according to the developer's GameAnalytics configuration and applicable GameAnalytics terms. Retention of backend operational, security, commerce and support records depends on operational and provider settings and the purpose of the record, including entitlement administration, refunds or revocations, fraud prevention, security, support, and applicable legal or dispute requirements. Hosting providers may separately retain routine request metadata such as IP/network information and timestamps for operations and security. Contact the developer about retention for a specific record.

14. International processing

Pulse's service providers operate internationally. Information may therefore be processed in countries other than your own, where privacy laws may differ. Providers use the locations and transfer safeguards described in their terms, privacy notices, and data-processing commitments.

15. Your choices and rights

• On Web and supported native builds, play without analytics, decline analytics, or change your analytics choice in Settings. Withdrawing Web consent stops future analytics transmission and removes the local Web analytics identifier.
• On supported native builds, enable or disable Daily reminders and manage notification permission.
• Choose whether and where to share a Daily or Pulse Core result when sharing is available.
• Clear local Pulse data through browser, app, or device settings, or uninstall Pulse.
• Use the applicable platform-store controls for native purchases and payment information.
• Contact the developer to ask about access, correction, deletion, restriction, objection, or withdrawal of consent where applicable law provides those rights.

Because Pulse has no account and uses opaque or pseudonymous identifiers, the developer may need enough information to verify and locate a record and may not be able to link every record to you. Some information may be retained where reasonably necessary for security, fraud prevention, transaction records, legal compliance, or legal claims. You may also have the right to complain to your local data-protection authority.

Turning Android analytics off stops future optional analytics delivery; it does not itself delete previously delivered records or records needed for purchase verification. See the data deletion request instructions. Do not send passwords, purchase or Integrity tokens, payment-card details or private keys.

16. Children's privacy and audience

Pulse is a general puzzle game and is not specifically designed or directed at children under 13. Its intended Google Play audience is ages 13–15, 16–17, and 18 and over. If you believe a child under 13 has provided personal information directly to the developer, please contact the developer so the matter can be reviewed and appropriate action taken.

17. Security

Reasonable technical and organizational measures are used to protect information, including encrypted network connections, token hashing where described, signed entitlement data, Google Play purchase verification, and Play Integrity checks. No method of storage or transmission is completely secure, so absolute security cannot be guaranteed.

18. Changes to this policy

This policy may be updated when Pulse, its providers, or legal requirements change. The revised policy will be posted at this URL and the “Last updated” date will change. Material changes may also be communicated in the app or through another appropriate channel where required.

19. Contact

For privacy questions, rights requests, or support, email Mark Mottian at pulse.gameplay.team@gmail.com.