Privacy policy

In this policy, the user means the person using Pearform, and the developer means the controller identified below.

1. Controller

The controller is Kristian Kähkönen, an individual developer based in Finland who develops and operates Pearform personally. If you have any questions or need support, you can contact the developer at [email protected].

2. How Pearform handles data

Pearform stores app content on the user's device. The developer operates a single server endpoint, used only when the user chooses to redeem an access code; it holds no app content and no user accounts.

Android automatic backup is enabled for Pearform. If backup is turned on in the user's device settings, Android may back up app content and settings to the user's Google account. The developer does not receive or have access to those backups.

The developer receives personal data when the user chooses to send feedback by email or to redeem an access code, and can access limited information made available through Google Play, as described below.

3. Purpose and legal basis

App content is used on the user's device to provide Pearform's features.

Feedback correspondence is processed to respond to the user and investigate or fix reported problems. The legal basis is the developer's legitimate interest in providing support and improving Pearform (Article 6(1)(f)). Sending feedback is voluntary; without the user's message and contact details, the developer may be unable to answer the request.

Purchase information is used to provide Premium and handle purchase-related support. The legal basis is performance of the Premium purchase contract (Article 6(1)(b)). Premium can also be temporarily activated with an access code.

Access code redemption is processed to check the code the user enters, activate Premium on the user's device and prevent misuse of access codes. The legal basis is the developer's legitimate interest in providing the feature the user requests and in preventing misuse of codes (Article 6(1)(f)). Redeeming a code is voluntary and not required to use Pearform or Premium.

4. Data content

App content stored locally: habit plans and activity records, journal notes and mood entries, the name entered by the user, and app settings. This content may also be included in Android automatic backups or files the user chooses to export.

Feedback correspondence: the user's email address, message and any attachments, together with the app and Android versions added to the feedback email. The feedback feature opens the user's email app; the message is sent only if the user chooses to send it. The developer receives app content only if the user includes it in the correspondence.

Purchases: the app receives Premium status and a purchase token from Google Play. The developer can view an order number, product, amount, country and date through Google Play.

Access code redemption: when the user chooses to redeem an access code, the code, the app version, the Android version and the app language are sent over an encrypted connection to the developer's server. The server returns a signed access grant, which is stored on the device with the app settings. The developer records the app version, the Android version and the app language, to diagnose redemption problems. The developer's server does not store the IP address. The hosting provider and Cloudflare process it to deliver the request and limit repeated attempts.

The app uses notification, exact alarm, run-at-startup and internet permissions. Internet access is used only for optional code redemption. Google Play features can communicate with Google.

5. Sources

App content comes from the user's entries and activity in Pearform. Feedback correspondence comes from the user. Code redemption data comes from the user's device when the user redeems a code. Purchase information and other information available in Google Play come from Google Play.

6. Service providers and transfers outside the EU or EEA

Email: feedback emails are received and stored in the developer's Microsoft Outlook mailbox. Microsoft processes email data to provide the service and may process it outside the EU or EEA, including in the United States. Microsoft describes its transfer safeguards, including the EU–US Data Privacy Framework and EU standard contractual clauses where applicable, in the Microsoft Privacy Statement.

Server hosting: the developer's server runs on Oracle Cloud Infrastructure in a data centre in the EU / EEA. Oracle processes code redemption requests, including the IP address, to deliver them to the server. Oracle describes its processing and any transfers outside the EU or EEA in the Oracle Services Privacy Policy.

Cloudflare: requests to the developer's server pass through Cloudflare, which processes the IP address and request details to deliver the request, protect the server and limit repeated attempts. Cloudflare may process data outside the EU or EEA, including in the United States. Cloudflare describes its transfer safeguards, including the EU–US Data Privacy Framework and EU standard contractual clauses where applicable, in the Cloudflare Privacy Policy.

Google services: Google processes data for its services under Google's Privacy Policy. This includes Premium purchases through Google Play Billing, in-app rating and update prompts, diagnostics the user chooses to share with Google, and Android automatic backup. Google may process data outside the EU or EEA using the safeguards described in its policy.

Ratings and reviews submitted through Google Play may be public and visible to the developer. Closed-test feedback is shared privately with the developer. The user can manage or delete reviews through Google Play. Update checks involve device and app information. The developer may also view aggregated crash reports through Google Play if the user shares diagnostics with Google. Google's documentation describes data handling for in-app reviews and in-app updates.

Android automatic backup: when device backup is enabled, Android can upload app data to Google's backup service and restore it when the user reinstalls Pearform or sets up another device. This happens through Android, without sending the backup to the developer. The user can manage backup through the device's backup settings, as explained in Google's Android backup guidance.

Manual backups and sharing: backup files, CSV exports and share cards are saved or shared to a destination chosen by the user. If the user chooses a cloud service or sends a file to someone, that recipient receives the selected content and the receiving service's privacy policy applies.

7. Retention and deletion

Feedback correspondence is kept while the matter is open and deleted when it is resolved and the correspondence is no longer needed for related support. The user may request earlier deletion, subject to applicable legal exceptions. Deleted Outlook messages may remain recoverable for a limited period under Microsoft's retention rules.

App content remains in Pearform's local storage until the user deletes it, uses Reset app or uninstalls the app. Those actions do not necessarily delete existing Android backups or exported or shared copies. Android may restore previously backed-up content after reinstallation. The user can manage cloud backups separately through Android or Google backup settings and delete exported files from their saved locations.

Google determines retention within its own services, including Google Play purchase records and Android backups. Purchase details included in feedback correspondence follow the correspondence retention rule above.

For each access code, the developer's server keeps a redemption count and the time of each redemption, with the app version, the Android version and the app language. These records contain no personal data. The access grant on the device follows the rules for app content above and may be included in Android automatic backup.

8. Protection

App content is stored in Android's app-private storage, which restricts access by other apps. The journal lock uses Android's screen lock or biometric prompt. Pearform does not receive or store biometric data.

Code redemption uses an encrypted connection. Access grants are digitally signed, so they cannot be forged or altered, and the developer's server holds no app content.

Only the developer uses the Outlook mailbox to handle feedback; Microsoft also processes messages to provide and secure the email service. Android backups are protected by Google's backup service and the user's device and account security settings. Exported or shared copies are subject to the protections of their destination.

9. User rights

For personal data the developer processes, the user may request access, rectification, erasure or restriction, and object to processing based on legitimate interests, by emailing [email protected]. These rights apply subject to the conditions in the GDPR. Data portability applies where processing is automated and based on consent or contract; it does not apply to feedback correspondence processed solely under legitimate interests.

The user may complain to the Finnish Data Protection Ombudsman.

The user controls local app content and can edit or delete it in Pearform, take a copy with Back up now, or clear local app content with Reset app. The developer cannot access or delete the user's Android backups or exported copies. The user can manage data held by Google through the relevant Google account and service settings.

The developer does not use the user's personal data for profiling or automated decisions with legal or similarly significant effects.

10. Children

Pearform is not directed at children under 13. The local storage, Android backup and feedback practices described in this policy apply to its users.

11. Changes

Changes are published at pearform.app/privacy with a new effective date. This policy will be updated before new features change how personal data are handled.