Last updated: 29 August 2026
ImagePinly is built so your library stays on this device. There are no ImagePinly accounts and no ImagePinly cloud for your notes.
The app stores locally: projects, notes (photos), pin positions and details (title, description, category, optional link, optional voice note), categories, and settings. Photos and voice recordings are kept in the app's private storage. A local database holds titles, locations, comments, dates, and pin data. ImagePinly does not upload this library to ImagePinly servers.
Camera or the photo library is used only when you add a note. The microphone is used only when you record a voice note on a pin. Those files remain on the device unless you export or share them.
Backup writes a file you save where you choose. Restore reads a file you pick. ImagePinly does not keep a copy of that file on our servers.
Share as ImagePinly creates an encrypted note file and hands it to the system share sheet. You choose where it goes. Photos, pin text, and voice notes inside cannot be unpacked or opened as a zip. Only ImagePinly can unlock the file and import it so the other person can keep editing.
Share as Image sends a picture of the note the same way. That picture cannot be imported as an editable note.
ImagePinly does not host shared files. The app you share to (mail, messaging, files, and so on) has its own privacy policy.
Almost all features work offline. If you paste a YouTube link on a pin and the device is online, the app may fetch a title and thumbnail from YouTube's public oEmbed API so a preview can be shown. That happens only for that action. Other web links are stored on the device; opening a link uses the device browser.
Before sharing a picture, the app may check that a network connection exists. That check does not send your note to ImagePinly.
Crash reports, described in section 6, are the only other network use that can leave the device without you choosing to share or export.
On Android, ImagePinly uses Firebase Crashlytics, a Google service, so we can see when the app crashes or stops responding and fix those bugs.
We use it only to keep the app stable. A report can include a technical stack trace, app version, device model and OS version, whether the build is Dev or Prod, short diagnostic logs around the crash, and a random install ID. That ID is not an ImagePinly account and is not used to identify you as a person.
We do not use Crashlytics as analytics of how you use the app. We do not use it to track screens, taps, or features you open. We do not use it for advertising, marketing, profiling, or remarketing. We do not sell crash data.
Crash reports do not include your projects, photos, pin titles or descriptions, categories, links, voice notes, backups, or shared files.
ImagePinly does not include a usage-analytics SDK (for example Google Analytics). On iOS, ImagePinly does not include Firebase Crashlytics.
Crash reports are sent only when the device can reach the network. If you are offline, they wait and send later. Google processes this diagnostic data under Google's privacy policy for Firebase.
The app reads the clipboard only when you tap Paste in a pin link field.
No sign-in, no advertising, no usage-analytics SDK, no tracking pixels, and no sale of personal data. Your library is not uploaded to ImagePinly. Crash reporting is limited to the diagnostics in section 6.
The operating system may include app files in its own phone backup. That is controlled by the OS, not by an ImagePinly cloud.
The app is not directed at children under 13. We do not collect your library on our servers.
If this policy changes, the copy in the app will be updated.
For privacy questions, use the ImagePinly listing on the store where you installed the app.