Privacy Policy

KarPing APR (“KarPing APR”, “the App”) is provided by KarPing AI Solutions LLP (“KarPing”, “we”, “us”, or “our”).

We respect your privacy and have designed KarPing APR to operate primarily on your device. This Privacy Policy explains what information the App accesses, how that information is used and stored, when information may be passed to another application at your request, and the choices available to you.

By using KarPing APR, you acknowledge the practices described in this Privacy Policy.

1. About KarPing APR

KarPing APR is a parking-location recall application designed to help you save the location of a parked vehicle and navigate back towards that location.

The App may use your device's location and motion or orientation sensors to provide these functions.

KarPing APR is designed as a local-first application. The current version does not require a KarPing account and does not upload your saved parking information to servers operated by KarPing AI Solutions LLP.

2. Information the App Accesses

Depending on the features you use and the permissions you grant, KarPing APR may access or process the following information.

2.1 Location Information

KarPing APR may request access to your device's precise location and/or approximate location.

Location is used to:

• determine your position when you save a parking location;
• store the position of your parked vehicle;
• determine your current position when you use the Find Vehicle feature;
• calculate distance and direction towards your saved vehicle location; and
• improve the usefulness and confidence of directional guidance.

The App may also process information associated with a location fix, such as location accuracy and the time at which the parking location was saved.

KarPing APR does not request background-location permission. Location is used for the App's foreground parking and vehicle-finding functions.

2.2 Device Orientation and Heading Information

KarPing APR may access device motion, orientation, compass, rotation-vector, or similar sensor information to determine the direction in which your device is facing.

This information may be combined with location information to provide directional guidance towards your parked vehicle.

Sensor and heading information is processed locally on your device and is not stored as a history of your movements.

2.3 Parking Information You Provide

You may optionally provide information about your parking location, including:

• floor or level;
• pillar, landmark, or other location reference;
• parking notes; and
• a parking photograph.

This information is used solely to help you identify and return to your parked vehicle.

2.4 Parking Photographs

If you choose to take a parking photograph, KarPing APR launches a compatible camera application installed on your device.

The photograph used by KarPing APR is stored within the App's private internal storage.

KarPing APR does not request access to your general photo library solely for this feature.

Temporary photo files created during an interrupted or cancelled camera workflow may be retained briefly to support recovery of the camera operation. Abandoned temporary photo records are automatically treated as stale after a limited period and become eligible for deletion.

2.5 Parking Date and Time

The App stores the date and time associated with a saved parking location. This information is used to show when the parking location was recorded.

3. How Your Information Is Stored

Saved parking information is stored locally within KarPing APR's private application storage on your device.

This may include:

• latitude and longitude;
• location accuracy;
• parking date and time;
• floor or level;
• pillar or landmark;
• notes; and
• the URI or reference to an optional parking photograph.

Parking photographs are also stored in the App's private internal storage.

The current version of KarPing APR does not provide cloud synchronisation of saved parking information.

4. Firebase Analytics and Information Collected

KarPing APR uses Google Analytics for Firebase to understand how the App is used and improve reliability and usability. Analytics may automatically collect app-instance identifiers, app and device information, app lifecycle and engagement events, and approximate geographic information derived from network information (such as a masked IP address). This information is transmitted to Google for analytics processing.

The App also records usage events such as saving or clearing a parking location, saving parking details, adding a parking photograph, starting Find Vehicle, sharing a parking location, and opening History. A parking-save event may include numerical indicators of whether details or a photo were added and a numerical save count.

Our custom analytics events do not include saved GPS coordinates, precise parking positions, parking names, floor or pillar details, parking notes, or photographs. The App does not set an Analytics user ID based on a KarPing account; no account is required.

Advertising ID collection is disabled in the App's Analytics configuration, advertising-related permissions are removed from its Android manifest, and ad-personalization signals are disabled by default. Firebase Analytics may still use a non-advertising app-instance identifier for measurement. The App does not display advertisements.

Analytics collection starts automatically when the App is used; this version does not provide a separate in-app Analytics opt-out. Users may contact us with privacy questions. Google's processing and retention of Analytics data follow the applicable Google services terms and our Analytics configuration. Analytics is not a backup or synchronization service for your parking history.

Further information: Firebase Privacy and Security and Google Privacy Policy.

5. External Maps and Sharing

When you choose to open a saved location in an external maps or navigation application, the App passes the selected parking coordinates to that application through an Android intent. The external app's handling of the information is subject to its own privacy practices.

When you explicitly use Share Parking Location, the App creates a share message containing a map link with saved coordinates and the parking time; depending on the parking record, it may also contain its name and optional parking details. You select the recipient or destination application. These transfers are initiated by you, not automatic Firebase Analytics uploads.

6. External Camera Applications

When you choose to take a parking photograph, KarPing APR may interact with a camera application available on your device.

The App provides that camera application with temporary permission to write the requested photograph to a specific private file made available through Android's secure file-sharing mechanism.

The camera application is provided by your device manufacturer or another third party and may be subject to its own privacy policy and practices.

7. Google Play Services and Android Platform Services

KarPing APR uses Android platform services and Google Play Services location functionality to obtain device position where available. Those services may perform network-based processing according to the applicable device and Google settings and privacy practices.

The App itself does not submit your saved parking record to a KarPing-operated server. Firebase Analytics is a separate Google service described in Section 4.

8. Sharing of Information

KarPing AI Solutions LLP does not sell your saved parking information. The App does not automatically send saved parking coordinates, notes, or photos to Firebase Analytics or to a KarPing-operated server.

Google processes the analytics information described in Section 4 on our behalf for measurement. Information may also be passed to an external maps, camera, messaging, or sharing application when you initiate the corresponding action. Once the external application receives it, its own privacy terms apply.

9. Android Backup and Device Transfer

The App configures Android backup and device-transfer rules to exclude its Room database directory, the specified parking-location DataStore file, and the private parking-photo directory. These exclusions are designed to avoid backing up or transferring sensitive saved parking information through the covered Android mechanisms.

Device/platform implementations and backups created before these exclusions may differ; the App cannot retroactively erase an earlier device backup. Other non-excluded application settings may remain eligible for Android backup.

10. Data Retention

Saved parking records and photographs are stored locally. Clearing the currently active parking location ends the active session, but a previously saved record may still appear in History until it is deleted or removed by the App's history-retention rules.

KarPing APR retains the five newest non-kept history records and permits records marked as kept to remain protected from automatic history trimming. Trimming occurs when another parking record is saved. You may delete individual history records yourself, including their associated application-owned photograph.

Temporary abandoned camera captures can become eligible for cleanup after approximately 24 hours. This does not mean a saved parking record is automatically deleted after 24 hours.

Firebase Analytics information is retained and processed under the applicable Google Analytics configuration and retention policies; deleting a local parking entry does not automatically delete analytics events already transmitted to Google.

11. Deleting Your Information

You may clear your current parking location in the App, delete individual records from History, remove application data through Android Settings, or uninstall KarPing APR. Clear Parking is not the same as deleting all History records.

The App does not require a KarPing account and does not maintain a KarPing-operated online copy of your parking records. For questions about personal data handled through Analytics, contact contact@karping.co. We will assess requests subject to the technical capabilities and applicable legal requirements of the services involved.

12. Permissions

The App may request Android Approximate Location or Precise Location permission for its foreground parking and vehicle-finding features. You can refuse or change these permissions in Android Settings. The App does not request background-location permission.

It also has Internet and network-state access used by Firebase Analytics and underlying services. Advertising ID and Android AdServices advertising/attribution permissions are excluded from the current release manifest.

13. Security

We use private application storage, restricted photo URI sharing, backup exclusions, limited analytics event parameters, and the available transport security of Google services. Advertising ID collection and ad-personalization signals have been disabled as described above.

Information transmitted by Firebase Analytics is protected in transit using Google's supported transport safeguards. No software, storage, or network system can guarantee absolute security.

14. No Continuous Location Tracking

KarPing APR is not designed as a continuous background location-tracking service. The current version does not request Android background-location permission and does not maintain a history of your movements for KarPing AI Solutions LLP.

15. Children

KarPing APR is a general-purpose utility application and is not specifically directed at children.

16. Changes to the App or Privacy Practices

KarPing APR may evolve over time. If a future version changes how personal or sensitive information is accessed, transmitted, collected, stored, used, or shared, this Privacy Policy will be updated as appropriate.

17. Changes to This Privacy Policy

We may update this Privacy Policy from time to time to reflect changes to KarPing APR, our privacy practices, legal or regulatory requirements, or platform requirements. The revised version will show a new effective date.

18. Contact Us