Privacy Policy

Effective and last updated: August 14, 2026

This policy covers Prizmaly's website and mobile applications, with detailed disclosures for Hamen below. Hamen is designed to keep listening activity on your device. Hamen does not sell personal data, display advertising, access your microphone, record audio, access HealthKit, or transmit health or wellness information from your listening activity. RevenueCat processes an anonymous installation/customer identifier and limited technical app, device, and store information when Hamen starts. Purchase and subscription information is also processed when Hamen checks, purchases, renews, restores, or synchronizes Premium access. On iOS, Hamen uses Meta technologies to measure advertising performance and limited conversion events, subject to the privacy controls described below. Hamen does not send listening choices, listening history, health or wellness information, or Apple profile details to these advertising providers. If you submit a careers application, we process the contact details, work information, message, and CV or résumé you choose to provide as described below.

Scope and operator

The Hamen-specific sections of this policy apply to the Hamen mobile application for Android and iOS, including the package and bundle identifier com.prizmaly.hamen. The section titled “Other Prizmaly services” covers prizmaly.com and Prizmaly apps that do not provide a more specific notice. The data controller and operator is PRIZMALY YAZILIM TICARET LIMITED SIRKETI (“Prizmaly”, “we”, “our”, or “us”). For privacy questions or requests, contact info@prizmaly.com.

Information kept only on your device

Favorites, listening history, onboarding choices, listening-plan progress, timer settings, and playback preferences are stored locally on your device. Hamen does not transmit this information to Prizmaly or to RevenueCat, use it to build a health profile, or sync it to a Prizmaly server.

On Android, you can erase this information, including onboarding and playback settings, with Menu → Reset local data. The Android app does not offer account sign-in.

On iOS, Sign in with Apple is optional. If you use it, Apple authenticates you and Hamen may receive an Apple user identifier and, when Apple provides them, your name and email address. Hamen stores those details only on that device; it does not transmit them to Prizmaly servers, RevenueCat, or Meta, and it does not create a Prizmaly server account. Menu → Delete Account removes the locally stored Apple profile, favorites, listening history, listening-plan data, and listening statistics from that device. It does not delete or rotate Hamen's anonymous RevenueCat customer record.

Uninstalling Hamen also removes its local app data, subject to your device and operating-system backup settings. Resetting local data, deleting the local iOS profile, or uninstalling does not by itself erase purchase records held by an app store or RevenueCat.

Purchases and subscription access

When Hamen offers Premium purchases, Google Play or Apple processes the payment under its own privacy policy. Hamen does not receive or store your full payment-card or bank-account details.

We use RevenueCat as a service provider to verify purchases, unlock Premium features, restore access, prevent purchase fraud, provide customer support, and understand subscription performance. Hamen configures RevenueCat when the app starts, including before a purchase is made, so RevenueCat can check available Premium products and the current entitlement status. RevenueCat may process:

Hamen does not send RevenueCat your name, email address, phone number, Apple profile details, listening choices, microphone audio, or health information. On iOS, RevenueCat may receive the iOS identifier for vendor (IDFV) and the current App Tracking Transparency authorization status as part of ordinary SDK operation. Only after you authorize App Tracking Transparency does Hamen send RevenueCat the Facebook SDK anonymous identifier or ask RevenueCat to collect Apple's advertising identifier (IDFA). RevenueCat's authorized-device collection also registers device, IP-address, and IDFV attributes for attribution. When the Meta dashboard integration is enabled, RevenueCat may then send limited trial, subscription, renewal, and one-time-purchase conversion events to Meta for advertising measurement and optimization; Hamen configures that integration not to deliver these advertising conversion events when ATT is not authorized. On Android, Hamen does not set advertising or attribution identifiers or RevenueCat customer attributes. RevenueCat acts on our instructions as a service provider; its processing is also described in the RevenueCat Privacy Policy.

On Android, Google Play Billing automatically sends Google limited technical context and billing-operation diagnostics. This can include the Hamen package and version, Billing Library version, Android version, device brand or model and build information, a random billing-client session value, billing API outcomes, service-connection issues, error or response codes, and operation timing or latency. Google uses this information to operate, improve, and troubleshoot Google Play Billing.

Analytics, diagnostics, and advertising

Hamen does not display third-party advertising or use a standalone crash-reporting service. Embedded service SDKs may process limited SDK crash or diagnostic information for security and app functionality as described in their privacy notices. RevenueCat performs the subscription analytics described above, and Google Play Billing processes the Android billing-operation diagnostics described above.

When configured, the Meta SDK processes the Facebook SDK anonymous identifier and limited app, device, network, event, and SDK diagnostic information. Hamen sends Meta app-activation, tutorial-completion, paywall-view, and checkout-initiation events. A checkout-initiation event can include the selected App Store product identifier, price, and currency. Hamen disables Meta's automatic in-app-purchase logging; RevenueCat is the sole source of trial-start, initial-purchase, renewal, subscription-conversion, and one-time-purchase events sent server-side to Meta when that dashboard integration is enabled. Hamen does not include listening choices, frequencies, goals, sessions, listening-plan choices, listening history, Apple profile details, or health or wellness information in these events.

Hamen requests Apple's App Tracking Transparency permission on iOS. Apple's advertising identifier is collected only if you authorize that request; denying it does not restrict any app feature. RevenueCat still receives the authorization status. If you deny the request, Hamen does not send the Facebook SDK anonymous identifier to RevenueCat and does not authorize RevenueCat to deliver Hamen's server-side advertising conversion events to Meta. Meta may still process limited app-scoped or aggregate App Events without IDFA where permitted. App Tracking Transparency controls cross-app tracking; it does not itself disable all app-scoped or aggregate measurement. You can change the permission later in iOS Settings. Meta's processing is described in the Meta Privacy Policy. If you intentionally choose Hamen's Facebook sharing option, Meta also processes that user-directed share under its own terms and privacy policy. If the Facebook dialog is unavailable, Hamen may show the iOS system share sheet; the destination service you choose receives the link and any text you elect to share under that service's own terms and privacy policy.

Hamen does not request microphone or device-location permission, capture or upload microphone recordings, or collect precise location. Except for service providers' IP-derived country or coarse location, it does not collect approximate location. It does not collect contacts, browsing history, messages, photos, videos, or personal audio files. Hamen does not access HealthKit or transmit health and fitness data off-device.

Why we process purchase, attribution, and conversion information

We process purchase information to perform the Premium service you request, restore purchases, maintain service security, respond to support and deletion requests, comply with store and legal obligations, and evaluate subscription performance. Where applicable, the legal bases are performance of a contract, our legitimate interest in operating and securing Hamen, and compliance with legal obligations. We process attribution and conversion information to measure campaign effectiveness, prevent duplicate or fraudulent attribution, and optimize our marketing. Where applicable, we rely on consent for tracking that requires consent and on our legitimate interests for non-tracking, app-scoped, or aggregate measurement where permitted.

Sharing and international processing

We do not sell personal data for money. Our disclosure of the identifiers and conversion information described above to Meta for advertising measurement and optimization may be considered "sharing" or targeted advertising under some privacy laws. Purchase information may be processed by Google Play, Apple, and RevenueCat for store payment, entitlement, support, fraud-prevention, subscription analytics, billing operation, improvement, and troubleshooting. On iOS, Meta may process the limited attribution and conversion data described above for campaign measurement and optimization. These providers may process information in countries other than yours and apply their own legal safeguards for international transfers. We may also disclose information when required by law or to protect users, Hamen, or our legal rights.

Retention and deletion

On-device Hamen data remains until you reset it or remove the app. On iOS, the locally stored Apple profile remains until you use Menu → Delete Account or remove the app. Purchase and entitlement records are retained only as long as needed for access restoration, support, fraud prevention, accounting, store, and legal obligations. Store transaction records controlled by Google or Apple are subject to those companies’ retention rules.

On Android, to request deletion of the RevenueCat customer record associated with this Hamen installation, open Menu → Request Data Deletion. Hamen prepares an email containing the automatically generated anonymous RevenueCat App User ID needed to locate the record; this is the Hamen Support ID. You can also email info@prizmaly.com and include that Support ID. We process valid requests within applicable legal deadlines unless retention is required by law.

On iOS, Menu → Delete Account deletes the local profile and local listening data described above. It does not delete or rotate Hamen's anonymous RevenueCat customer record or remotely delete RevenueCat, Meta, Apple, or App Store records. To request deletion of a RevenueCat record associated with this Hamen installation, use Menu → Contact Us or email info@prizmaly.com. We may ask for the app version, approximate installation or purchase date, device details, or an App Store transaction reference strictly as needed to verify the request and locate the relevant record. Do not send payment-card or bank-account details. RevenueCat and Meta retain provider records according to their service settings and policies, including as needed to provide purchase verification, attribution and analytics, prevent fraud, and meet accounting or legal duties. Requests concerning data controlled by Meta can also be made through Meta's privacy controls described in its privacy policy.

If you contact us for support or deletion, Prizmaly receives the sender email address, message and free-text content, and any information you choose to include. Hamen's prepared Android deletion email also includes the app/package name, app version and build, Android version, and the anonymous Hamen Support ID when available. We use this correspondence and technical context only to respond, locate the relevant provider record, prevent abuse, and meet legal obligations. We process valid requests within applicable legal deadlines.

Deleting customer data does not cancel an active subscription. Manage or cancel subscriptions separately in Google Play or the App Store.

Your rights

Depending on where you live, you may have rights to access, correct, delete, restrict, or object to processing, to obtain a portable copy of covered data, or to complain to a data-protection authority. Contact us to exercise a right. The Android app does not create an account, and the optional iOS Apple profile is stored locally rather than in a Prizmaly account system. Because RevenueCat normally identifies an installation with an anonymous App User ID, we may need the Hamen Support ID or other limited transaction information to find the relevant provider record.

Security

Hamen minimizes collection and uses encrypted HTTPS connections for purchase, attribution, sharing, and event communication with service providers. No system can guarantee absolute security, but we limit access and use reasonable administrative and technical safeguards appropriate to the information processed.

Job applicants and careers enquiries

Prizmaly processes information submitted through the careers form for recruitment purposes. The separate Applicant Privacy Notice explains the controller, exact applicant data, purposes, collection method and legal bases, recipient categories, international processing, retention, and applicant rights. That notice governs the careers-form processing.

Other Prizmaly services

Prizmaly's website and apps other than Hamen are also designed to minimize collection. Depending on the service and the notice shown in that app, they may process anonymous crash reports or feature-usage counts, information you voluntarily provide such as an email address, and purchase history supplied by Apple App Store or Google Play. They may use Apple or Google for payments and Firebase Crashlytics for anonymous crash reporting. Most app data remains on the device; where a service needs server-side storage, Prizmaly uses encrypted connections and reasonable access controls.

Prizmaly does not sell personal data or use it for unrelated advertising or profiling. A product-specific in-app notice or store disclosure controls if it describes a narrower or different data flow. You may contact info@prizmaly.com to ask about, access, correct, or delete covered information associated with another Prizmaly service.

Children

Hamen is not directed to children under 13, and we do not knowingly collect personal information from children. If you believe a child has provided covered information, contact us so we can investigate and delete it where required.

Changes

We may update this policy when Hamen, our providers, or legal requirements change. We will post the revised effective date here and provide additional notice when required.

Contact

PRIZMALY YAZILIM TICARET LIMITED SIRKETI
Privacy Support
info@prizmaly.com