Effective date: 8 October 2026
Publisher / developer: Hakan Gezmeli — Individual Developer
Contact: diagniq.app@gmail.com
Colla (“the app”) is a photo collage editor for Android and iOS. You choose photos already on your device, arrange them into a collage, and save or share the result. The app has no user account and no Colla-operated server. All photo editing happens on your device.
This policy explains the limited data involved in running the app and the one third-party service the app uses (RevenueCat, for purchases).
When you add photos to a collage, Colla opens your operating system’s own photo picker (the iOS photo picker / the Android photo picker). That picker runs outside the app. Colla receives only the specific image files you select and never gets ongoing or full access to your photo library.
Selected photos are read into memory for editing. Colla does not copy your selected source photos into its own long-term storage, and does not upload them anywhere.
Cropping, positioning, backgrounds, borders, layout, and rendering are all performed locally on your device. Your photos are not sent to Colla or to any third party as part of editing or exporting.
When you tap Save, the finished collage image is written to your device’s operating-system photo library using the OS “add to photo library” function. On iOS this uses add-only photo permission. Colla does not create albums and does not read back your library.
A copy of each exported collage, plus a small thumbnail and a timestamp, is also kept inside the app’s private storage to populate the in-app “Recent Creations” strip. This data never leaves your device. See section 10 for how to remove it.
Colla stores the following on your device only, using the platform’s standard key–value preference storage and the app’s private file storage:
None of this identifies you, and none of it is transmitted off the device by Colla.
On Android, Colla sets android:allowBackup="false". The local data in
section 5 is not included in Android’s cloud backup / restore. It stays on
the single device where it was created.
Colla offers an optional one-time purchase that unlocks “Colla Pro” features. It is not a subscription and does not renew. Purchases are processed by:
Colla never sees or stores your payment card details. Your relationship for billing and refunds is with Apple or Google under their terms and privacy policies.
Colla uses RevenueCat (RevenueCat, Inc.) as its purchase-infrastructure provider. For the data described in this section, Colla — the developer named at the top of this policy — is the data controller, and RevenueCat is a data processor acting on Colla’s behalf.
The app contacts RevenueCat when it starts, to check whether “colla_pro” is active, and again when you buy or restore Colla Pro. The start-up check happens whether or not you have bought anything.
Why this data is processed
What is processed
How the record is identified
Requests about this data
Send any request about the purchase data RevenueCat processes for Colla — access, correction, or deletion — to Colla at diagniq.app@gmail.com, not to RevenueCat. RevenueCat’s own privacy policy refers end users to the app developer for such requests. Because the record is anonymous, we need a way to find it. The order number on your App Store or Google Play receipt is one option; if you do not have it, write to us anyway and we will look for another way to match your record.
RevenueCat’s privacy policy is at https://www.revenuecat.com/privacy.
Purchase data is the one thing the developer does receive. RevenueCat makes the data in section 7.1 available to the developer through its dashboard: the purchase history recorded against each anonymous App User ID, and statistics built from it, such as the number of purchases and revenue.
The only network activity caused by the app is its communication with RevenueCat and the app stores described in section 7.
Colla is a general-audience utility and is not directed to children. It does not knowingly collect personal information from children. Colla has no account and no profile; RevenueCat holds an anonymous purchase record (section 7.1). Colla does not present itself as a child-directed app in either store.
Colla keeps app data in the operating system’s per-app private storage. Purchase and entitlement calls to RevenueCat and to the app stores are made over encrypted (HTTPS/TLS) connections provided by those SDKs. No system is perfectly secure, and the app cannot secure data held by Apple, Google, or RevenueCat.
Colla itself performs no server-side processing and operates no data centre.
RevenueCat states that it stores the data it processes on Amazon Web Services (AWS) data centres in the United States. The data in section 7.1 is therefore sent to and stored in the United States, wherever you live.
Where Apple or Google process purchase data, that processing may occur in countries other than yours, under those providers’ own safeguards.
Depending on where you live, you may have rights to access, correct, or delete personal data, or to object to certain processing.
If this policy changes, the updated version will be posted at its published location with a new effective date. Material changes will be indicated there.
For privacy questions or requests relating to Colla, contact diagniq.app@gmail.com.