ParkPin Privacy Policy

1. Overview

ParkPin is provided by OZMANOZCO. This policy explains what information the app processes, why it is used, and how you can contact us.

ParkPin does not require an account to run the core pick experience. Photos and camera frames used for picking are processed within the app flow to detect faces and choose a winner.

2. Information We Process

Depending on the features you use, the app may process the following categories of information:

• camera frames or photos you provide for live pick or photo pick
• face detection results such as face bounding boxes, temporary tracking identifiers, and winner highlight regions used to run the selection flow
• local pick history stored on your device, including pick time, mode, candidate count, winner thumbnail, locally stored source image, and blur setting
• app settings and local state such as ad timing or review-related preferences stored on your device
• crash logs, analytics events, and basic device or app information used for stability and usage analysis
• advertising identifiers and ad interaction signals used to deliver or measure ads

3. Permissions and Device Access

The app asks for device access only when needed for features you choose to use:

• camera permission for live pick mode or when you capture a photo in the app
• access to a gallery image that you explicitly choose through the system picker
• temporary local file creation when the app prepares a result image for the system share sheet
• on iOS, tracking permission may be requested to support relevant advertising and ad measurement

4. How We Use Information

We use processed information for the following purposes:

• to detect faces on device and fairly run the winner selection flow
• to show pick results, preserve local history, and let you reopen prior records on your device
• to render a share card or result image and hand it to the system share experience when you choose
• to configure app behavior such as ads or rollout controls through remote configuration
• to diagnose crashes, improve performance, and understand aggregate usage patterns

5. Face Data

This section specifically describes how ParkPin handles face data.

• What face data the app processes: camera frames or photos containing faces, detected face bounding boxes, temporary tracking identifiers used during the pick flow, winner highlight regions, winner thumbnail images, and locally stored source images used for result history or optional sharing.
• How face data is used: to detect faces on device, count candidates, run the random selection flow, display winner highlights, create winner thumbnails, save local result history, and generate a result image when you choose to share.
• What ParkPin does not do with face data: ParkPin does not use face data to identify a real person, perform face recognition, create biometric templates, authenticate users, or sell face data.
• Sharing and storage: face data is processed on device and is not sent to OZMANOZCO servers. Face data used for picks and history is stored only on your device, including local app storage, the local history database, and temporary files created for sharing. Face data is not shared with AdMob, Firebase Analytics, Firebase Crashlytics, or Remote Config. If you explicitly use the system share feature, the result image you choose to share is transferred to the third-party app or service you select.
• Retention: live camera frames are processed in memory and discarded after processing. When a pick result is created, the app stores related local history data and result assets on your device until you delete the history, clear app data, or uninstall the app. Temporary share files may remain until your device or operating system removes them.

6. Sharing and Third-Party Services

We do not sell personal information. Limited data may be processed by service providers that help us operate the app.

Face data described in Section 5 is not shared with our analytics, advertising, crash reporting, or remote configuration providers.

The following third-party services may process data on our behalf:

• Google AdMob (advertising)
• Firebase services (Analytics, Crashlytics, and Remote Config)

7. Data Retention and Deletion

Core pick data and history are stored locally on your device unless you remove them, clear the app, or uninstall the app.

Shared result images may be written to a temporary local file before the system share sheet opens. Those temporary files may remain until your device or operating system clears them.

Analytics, crash, and ad-related data may be retained by the relevant service providers according to their own policies.

8. Children's Privacy

The app is not directed to children under 13, and we do not knowingly collect personal information from children under 13. If you believe a child provided personal information, contact us so we can review and respond appropriately.

9. Security

We use reasonable administrative, technical, and organizational safeguards to protect the information processed for the app. No method of transmission or storage is perfectly secure, but we work to reduce risk appropriate to the app.

10. Changes to This Policy

We may update this policy when the app, our services, or legal requirements change. The revised version will be posted on this page with an updated effective date.