Privacy Policy

Summary

• chekma's core data is stored locally on your device.
• chekma does not currently use user accounts, cloud sync, or a developer-operated backend for your goal data.
• chekma does not upload your goals, marks, text entries, photos, audio recordings, observation sessions, or custom icons to the developer.
• Day exports are created locally and shared only when you choose a destination in the iOS share sheet.
• Release builds may show ads through Google Mobile Ads. Google may process advertising, device, diagnostics, performance, and interaction data as described below.

Information Stored on Your Device

Depending on how you use the app, chekma may store the following information locally:

• goals, including their names, colors, icons, ordering, creation dates, pinned state, and archive status;
• successful and unsuccessful marks, comments, and timestamps;
• text entries added to a goal's timeline;
• photos added from the camera or photo library, including optimized local copies and previews;
• audio recordings, their duration, and timestamps;
• observation sessions, including start and end times, used to calculate how long you observed a goal;
• app settings and local usage state, such as language, appearance, day boundary, time format, onboarding state, and Live Activity preferences; and
• custom SVG icons that you choose to import. Accepted SVG files are validated and converted into local image variants for display in the app and its Live Activity. The source icon is not uploaded to the developer.

Some local display data, such as custom goal icon variants, may be stored in an iOS App Group container shared between the main chekma app and its widget or Live Activity extension. This sharing occurs on your device and is used only to provide chekma features.

Camera, Photo Library, and Microphone

chekma may request access to:

• the camera, when you choose to capture a photo for a goal timeline;
• the photo library, when you choose an existing photo; and
• the microphone, when you choose to record an audio entry.

chekma requests these permissions only when they are needed for an action you initiate. Photos and audio recordings added to chekma are stored locally and are not uploaded to the developer.

You can review or revoke these permissions at any time in iOS Settings. If a permission is denied or revoked, the related capture feature may not be available, while the rest of the app will continue to work.

Live Activities and Dynamic Island

chekma may use iOS Live Activities and Dynamic Island to show active goals and session information and to let you add marks from the Lock Screen. Information needed to render the Live Activity may include a goal's name, icon, color, recent mark results, current selection state, and the Live Activity start time.

Live Activity actions can also open chekma directly to its camera or microphone flow. chekma does not use remote push updates for its Live Activity. Live Activity information is generated from data stored on your device and is not sent to a developer-operated server.

Exporting and Sharing a Day

When you choose to export a day, chekma creates a PNG image containing the goal name and icon, the date, tracking-day number, and a visual summary of successful and unsuccessful marks for that day. Exports for the current tracking day also include the export time. The export does not include timeline text entries, photos, or audio recordings.

You can choose a Compact, Medium, or Expanded export layout. The selected layout changes only the image dimensions and arrangement; every layout contains the same types of summary information described above.

The image is created in the app's temporary local storage and is passed to the standard iOS share sheet. chekma does not choose a recipient or upload the image to the developer. You decide whether and where to share or save it. The app schedules its temporary copy for deletion when the share sheet closes. A copy saved or sent to another app or service is then handled under that recipient's or service's own privacy practices.

Advertising and Consent

Release builds of chekma may show banner and interstitial ads through Google Mobile Ads (AdMob). Depending on the SDK configuration, your device settings, your region, and your privacy choices, Google Mobile Ads may automatically process:

• IP address, which may be used to estimate a device's general location;
• device identifiers, including an advertising identifier when available;
• advertising data, such as ads shown to the device;
• app and ad interactions;
• crash logs and diagnostics; and
• performance information such as app launch time, hangs, and energy use.

Google may use this information to provide, limit, measure, secure, and improve advertising and related services. Ads may be personalized, non-personalized, limited, or used only for technical delivery depending on the choices and requirements that apply to you.

chekma uses Google's User Messaging Platform to request and manage advertising privacy choices where required. If a privacy-options entry is available for your region, you can open Settings > Advertising privacy > Manage privacy choices in the app to review or change those choices.

After any required consent flow and before Google Mobile Ads is initialized, chekma requests permission through Apple's App Tracking Transparency framework when your tracking choice has not already been recorded. If you choose Ask App Not to Track, or if tracking is restricted, all app features remain available and Google Mobile Ads cannot access the iOS advertising identifier. Ads may still be shown in a non-personalized or limited form. You can review or change the app's tracking permission in iOS Settings.

chekma does not provide your locally stored goal content, text entries, photos, audio recordings, observation sessions, or custom icons to Google Mobile Ads.

For more information, see:

• Google Privacy Policy
• Google Mobile Ads SDK data disclosure
• Google advertising controls

Analytics and Diagnostics

chekma does not currently use a separate analytics or crash-reporting service operated by the developer. Google Mobile Ads may process diagnostics, performance information, and interactions for its own advertising and analytics purposes as described above.

Apple may separately provide aggregated App Store or operating-system analytics to developers according to your device and App Store privacy settings. That processing is governed by Apple's terms and privacy policies.

Data Sharing and Sale

The developer does not sell your personal information.

Goal data and media stored locally in chekma are not intentionally shared with the developer or with Google Mobile Ads. Advertising-related information may be processed by Google as described in the Advertising and Consent section.

Where chekma shares user data with a service provider, the provider is required to handle that data under its published privacy terms, applicable law, and protections that are the same as or equivalent to those required by this Policy and applicable App Store rules.

Data Retention and Deletion

Your locally stored chekma data remains on your device until you delete the relevant entry or goal in the app or remove the app from your device. Deleting a goal also removes its associated locally managed timeline entries and observation sessions. Locally managed photo, audio, and unused custom icon files are removed when the corresponding data is deleted or cleaned up by the app. Temporary day-export files are scheduled for deletion after the iOS share sheet closes.

Advertising-related information is retained by Google according to Google's own policies and controls.

Because chekma does not currently operate user accounts or a backend for goal data, the developer does not hold a server-side copy of your local goal data and cannot retrieve or delete that data on your behalf.

Your Choices and Rights

You can:

• delete individual entries or goals in the app;
• delete all locally stored app data by removing the app from your device;
• revoke camera, photo library, microphone, and tracking permissions in iOS Settings;
• review or change available advertising privacy choices in chekma Settings or through Google's advertising controls; and
• contact the developer about this Policy or a privacy request.

Depending on where you live, you may have additional rights concerning personal information processed by Google or another service provider. Requests relating to data held by those providers may need to be submitted directly to them.

International Processing

Google and its service providers may process advertising-related information in countries other than the country where you live. Their processing and international transfers are governed by their terms, privacy policies, and applicable legal safeguards.

Security

chekma relies on iOS application storage and platform protections for locally stored data. No method of storage is completely secure, so you should protect access to your device and keep iOS up to date.

Children

chekma is not intended for children under 13. The developer does not knowingly collect personal information from children through a chekma account or backend, because the app does not currently provide those services.

Future Features

If chekma adds cloud sync, user accounts, subscriptions, a developer-operated backend, additional advertising providers, or other features that change how information is processed, this Privacy Policy will be updated before or when those features become available.

Changes to This Policy

This Privacy Policy may be updated from time to time. The current version will be posted at this URL with a revised effective date.

Contact

For questions about this Privacy Policy or a privacy request, contact support@chekma.app.