ItemPin / 1.0
Data collection questionnaire
A reference based on the current app’s data flows: local storage, voluntary transfers and App Store privacy disclosure.
On this page
1. Storage and transfers
| Feature | Data and recipient | Your control |
|---|---|---|
| Local storage | Items, photos, quantities, notes, reminders and recognition results stay on this device. Creating records does not automatically send them to the developer. | Manage and delete records; export backups when needed. |
| Cloud recognition and tests | Submitted photos, language, category/field definitions, instructions, model parameters and credentials go directly to the configured API. Tests use generated images. The recipient can receive network information. | Enable separately after configuring; disable recognition or remove the key. Provider rules apply to data already sent. |
| ISBN lookup | Off by default. A requested lookup sends the ISBN to Open Library; the recipient may receive IP, time and app identification. | Enable or disable online lookup in Me; book details can still be entered manually. |
| Family sharing | Selected records, photos, member identifiers and sync information travel between approved local-network devices via the creator, without a developer cloud relay. | Manage scopes, members and leaving. Leaving does not erase copies already received by others. |
| Backups and subscriptions | Backups go to the location you choose; cloud-drive rules apply. Apple handles subscriptions; the app verifies access locally and sends no receipt to a developer server. | Keep or delete backups yourself; manage subscriptions through Apple. |
| Support email | When you contact us, the developer and email provider receive your address, message and attachments to handle your request. | Do not send API keys or unrelated personal information; you can make data rights requests. |
2. Basis for the App Store questionnaire
Apple’s disclosure considers data retained after leaving the device. Consult its guidance for classification and exceptions. This source-based reference is not a published privacy label.
| Questionnaire item | Current basis for an answer |
|---|---|
| Is data collected? | The overall answer awaits verification of third-party practices. Local storage alone is not developer collection; optional online features cannot simply be treated as “no collection”. |
| Photos or Videos / Other User Content | Assess these types if a cloud API retains submitted photos or custom text beyond the request. The app uses them for recognition, not developer advertising. |
| Search History / Identifiers / Other Data | Check retention and use of ISBN logs, API account/authentication records and network information such as IP before classifying them. An API key is not automatically a device ID. |
| Is it linked to identity? | Local family identifiers and API accounts are distinct. Providers may associate requests with accounts; not all services are confirmed to be unlinked. |
| Is it used for tracking? | The formal source has no advertising/analytics SDK, advertising-ID access or developer advertising profiles. Independent provider uses still need review; no promise covers every custom endpoint. |
| Purchases, contact and support | Purchase receipts are handled locally and are not automatically sent to the developer. Support email creates correspondence; assess email addresses, support content and attachments against actual handling and retention. |
3. Evidence needed before submission
- Retention, purposes, account linkage and deletion for photos, text and network logs at each preset API, actual plan and proxy.
- Handling of ISBN requests and network logs at Open Library, and the actual support-email workflow.
- Complete App Store Connect using the verified data types and purposes. This page does not replace the questionnaire or publishing action.
Data types and disclosure rules ↗ · Manage App Privacy in App Store Connect ↗
Support and privacy contact
Email us with questions, feedback or data rights requests.