Fianso

Independent software

LocalInk / Information

Privacy Policy

What LocalInk stores, what it does not collect, and when data leaves the app.

Effective 19 August 2026

Effective date: 19 August 2026

LocalInk is designed around a simple promise: your journal stays yours. This policy explains what the supported Android, iOS, and iPadOS applications store, what they do not collect, and what happens when you choose to export, back up, lock, contact support, or purchase LocalInk Pro.

LocalInk is published under the Fianso brand by Sofiane Łaba, its data controller, at Leśmiana 9/29, 80-280 Gdańsk, Poland. Product and support information is available at fiansodev.com, and privacy questions can be sent to support@fiansodev.com.

Summary

  • LocalInk does not require a LocalInk account.
  • LocalInk does not operate a server for journal content or provide cloud synchronization.
  • LocalInk does not include advertising, tracking, or analytics SDKs.
  • Fianso does not sell personal data or disclose journal content to advertisers or analytics providers.
  • Journal entries and related journal metadata are stored locally in an encrypted database on your device.
  • Journal data leaves LocalInk only when you intentionally create an export or backup. Separate technical or contact data may be processed when you visit the Fianso website, contact support, or use store billing, as described below.
  • Google Play and App Store Pro entitlements are separate. A journal backup does not contain or transfer a Pro entitlement.

Journal data stored on your device

LocalInk stores the content needed to provide the journal, including entry text, titles, journal dates, edit history, Trash state, optional mood and tag context, and locally calculated writing statistics. The journal database is encrypted with SQLCipher.

  • Android: the database encryption key is protected using Android Keystore. Android automatic backup and device-transfer backup are disabled for LocalInk's private data.
  • iOS and iPadOS: a random database encryption key is stored as a non-synchronizing Apple Keychain item using the WhenUnlockedThisDeviceOnly accessibility class. LocalInk applies file protection to its private journal storage and marks that storage for exclusion from device and iCloud backups. Apple treats backup-exclusion metadata as guidance, so LocalInk does not present Apple automatic backup or device migration as a supported way to recover the journal. Create a portable .localink backup if you need a restorable copy.

This data stays in LocalInk's private application storage unless you explicitly choose an export or backup destination. LocalInk does not upload journal content to a Fianso server.

Exports and portable backups

When you create an HTML or PDF export or a portable .localink backup, Android's system file picker or Apple's document picker lets you choose the destination. LocalInk writes the file to that user-selected destination and does not upload it to a LocalInk server. The provider you select may store the file locally or synchronize it through iCloud Drive or another third-party storage service selected by you.

HTML, PDF, and .localink backup files are readable and unencrypted. Anyone with access to them may be able to read your journal. HTML and PDF files are readable reports and cannot be restored into LocalInk. A .localink backup is a ZIP-compatible archive whose journal data can be extracted and read; a verified backup can be used to restore or move a journal between compatible LocalInk editions. You are responsible for protecting these files after saving or sharing them.

The .localink file contains journal data, not a Google Play or App Store Pro entitlement. Importing a backup does not grant, remove, or transfer Pro access.

Optional App lock

If you enable App lock, LocalInk asks the operating system to authenticate you using an available device credential or supported biometric method. Android may use a device credential or supported biometric method. iOS and iPadOS may use Face ID, Touch ID, or the device passcode through Apple's LocalAuthentication framework.

LocalInk receives the authentication outcome and limited status or error information from the operating system. Fianso does not receive biometric templates, your PIN, pattern, password, passcode, or other device credentials. When App lock is enabled, LocalInk also covers journal content in the app switcher. App lock is a user-interface privacy gate, not a separate encryption-key lock, and it cannot prevent screenshots or every form of capture. Enabling it is not consent to process personal data for another purpose.

LocalInk Pro and store billing

LocalInk Pro is an optional one-time purchase. The store through which you buy Pro handles payment and associates the entitlement with the account used in that store.

  • Android: Google Play Billing provides LocalInk with product information, purchase state, and the purchase token needed to verify, acknowledge, and restore the Google Play entitlement.
  • iOS and iPadOS: StoreKit provides signed product and transaction information that LocalInk processes on the device to verify current entitlement and restore the App Store purchase. LocalInk stores only a local Boolean entitlement cache; it does not store an App Store receipt, transaction identifier, purchase token, Apple Account identifier, or payment details.

LocalInk does not receive payment-card details, your Google or Apple password, or journal data through store billing. A later successful store check can update or remove the local entitlement cache following a refund, revocation, or account change. Billing information is not included in journal backups or exports.

LocalInk does not send StoreKit transaction information from the app to a Fianso-operated server. Apple may separately provide Fianso with seller-facing sales, proceeds, refund, tax, or financial reports through App Store Connect. Those reports do not contain journal content.

Google Play and App Store purchases are separate. Buying Pro on one store does not automatically grant Pro on the other store, and Fianso does not operate an account system that can combine or transfer store entitlements.

Support and feedback

LocalInk can open your external email application with a support address, subject, and limited diagnostic template such as the LocalInk version and build number. LocalInk does not send the message itself. You decide whether to send it and what to include. If you send an email, Fianso receives the sender name and email address, message, and any app, device, or operating-system information you include. Do not email journal entries, exports, backups, passwords, device credentials, or payment information.

Legal bases and limited data processing

Most processing described in this policy happens entirely on your device. Fianso has no remote access to your local journal content, local journal metadata, App lock authentication data, or user-selected export and backup files. The legal bases below describe processing connected with store billing, support, website operation, and legal obligations.

  • Store billing: product and entitlement information processed on the device is used as necessary to provide, verify, acknowledge where applicable, and restore the Pro purchase under Article 6(1)(b) GDPR. This information is needed only if you buy or restore Pro. Apple and Google may separately provide seller-facing records as described in this policy.
  • Support correspondence: if you contact support, Fianso processes the sender name and email address, message, and any app, device, or operating-system version information you choose to provide to respond and provide support under Article 6(1)(b) GDPR. Article 6(1)(f) GDPR applies only where continued processing is necessary to protect service security, prevent abuse, or establish, exercise, or defend legal claims. Contacting support is optional.
  • Website access and security logs: the OVHcloud hosting service automatically creates technical access and security logs that may include an IP address, date and time, requested URL, user-agent information, and security events. Fianso relies on Article 6(1)(f) GDPR to keep the public website reliable and secure. The legal pages do not use analytics, advertising trackers, tracking pixels, or cookies.
  • Website theme preference: if you choose light or dark mode on the Fianso website, only that preference is stored in your browser's local storage so the website can remember its appearance. It is not used for analytics, advertising, profiling, or tracking.
  • Legal and accounting records: if Fianso actually receives transaction, invoice, tax, or dispute information and Polish or EU law requires its retention, it is processed under Article 6(1)(c) GDPR. This does not mean that Fianso receives payment-card details, store-account passwords, or journal content.

Fianso does not use personal data for automated decision-making or profiling.

Recipients and international transfers

  • Google Play handles optional Android Pro purchases and acts under its own terms and privacy policy. Google Play Billing does not receive journal content from LocalInk.
  • Apple and the App Store handle optional iOS and iPadOS Pro purchases and act under their own terms and privacy policy. LocalInk does not send journal content to Apple for billing. Apple may separately make seller-facing sales, refund, proceeds, tax, and financial reporting available to Fianso.
  • OVHcloud provides website hosting, DNS, and email services to Fianso. It may process website access and security logs and support emails as a service provider. OVHcloud states that it uses contractual safeguards, including Standard Contractual Clauses where required, for relevant access or processing outside the EEA.
  • A storage provider selected by you through the system document picker may receive an export or backup at your direction and process it under that provider's own terms. Fianso does not select that provider or receive the file.
  • Personal data may be disclosed to public authorities or professional advisers only where necessary to comply with law or to establish, exercise, or defend legal claims.

Google and Apple may process store data outside your country under their respective privacy frameworks and legally recognized transfer safeguards. Provider terms and safeguards may change; current information is available in their privacy policies.

Permissions and platform access

LocalInk requests only platform capabilities needed for features you choose to use.

  • Android: biometric or device authentication is used for optional App lock, and Google Play Billing is used for an optional Pro purchase. The production manifest does not request general Internet, network-state, advertising ID, location, broad storage, media, camera, microphone, contacts, calendar, or notification permission.
  • iOS and iPadOS: LocalAuthentication is used for optional App lock, StoreKit is used for an optional Pro purchase, and the system document picker is used for user-selected files. LocalInk does not request App Tracking Transparency, location, photo-library, camera, microphone, contacts, calendar, or notification permission and does not include analytics, advertising, tracking, telemetry, or networking SDKs.

Retention and deletion

Journal data remains on the device until you edit or delete it, empty Trash, enable optional Trash cleanup, reset LocalInk, clear the app's data where the platform permits, or uninstall the app. Reset LocalInk destroys the local journal encryption material and initializes a fresh empty encrypted journal. User-created files outside the app—such as backups and readable exports—are not deleted by an in-app reset or uninstall.

The minimal cached store entitlement may survive an in-app journal reset because it represents a store entitlement rather than journal content. On Android, uninstalling or clearing app data removes the local cache; the entitlement can be restored from Google Play using the same Play account. On iOS and iPadOS, LocalInk does not rely on app deletion, offloading, Apple device backup, or Keychain behavior as journal recovery. The App Store entitlement can be restored when the same Apple Account still has a valid purchase, but journal recovery requires a usable portable .localink backup.

Support correspondence is retained until the request is resolved and for follow-up reasonably connected to that request. It is retained longer only where necessary to comply with a legal obligation, protect service security, prevent abuse, handle a complaint, or establish, exercise, or defend legal claims, and is then deleted or anonymized. Website access and security logs are retained under the OVHcloud service's applicable schedule; OVHcloud's published general schedule describes service-dependent retention of up to 12 months. Fianso does not create a separate website analytics or visitor-profile database. Transaction, tax, invoice, or dispute records actually received by Fianso are kept only for the period required by applicable law or while a related claim can be pursued or defended.

Your GDPR rights

Where the GDPR applies and subject to its conditions and exceptions, you may request access to, rectification or erasure of, or restriction of processing of your personal data. You may also have a right to data portability and a right to object to processing based on legitimate interests.

You manage local journal data directly in LocalInk. Because Fianso cannot remotely access the journal database or identify its contents, Fianso generally cannot fulfil a remote request concerning that local data. Fianso will not collect additional identifying information solely to identify journal data that it cannot identify. Requests concerning information Fianso actually holds, such as support correspondence, can be sent to support@fiansodev.com.

You also have the right to lodge a complaint with the President of the Personal Data Protection Office (Prezes Urzędu Ochrony Danych Osobowych, UODO) in Poland or another competent supervisory authority.

Children

LocalInk is designed and marketed for adults aged 18 and older. It is not directed to children.

Security limitations

No software can guarantee absolute security. A compromised, rooted, or jailbroken device; screenshots; screen recordings; third-party keyboards or accessibility services; deliberately exported files; temporary copies created during file handling; disclosure of device credentials; or a storage provider selected by you may expose journal content. LocalInk covers journal content in the app switcher when App lock is enabled, but cannot prevent every form of capture or disclosure. Keep your operating system and app store updated and protect exported files.

Changes to this policy

If LocalInk's data practices change, this policy and the applicable Google Play Data safety or App Store App Privacy declaration will be updated before the changed behavior is released. The effective date above identifies the current version.

Contact

For privacy questions or requests, contact support@fiansodev.com.