Back to VozParking

VozParking Privacy Policy

Effective and last updated: June 12, 2026

This policy explains how VozParking processes information when you use the mobile application. Contact us at vozparking@gmail.com with privacy questions.

Information We Process

Voice and AI Processing

Recorded requests are securely uploaded for cloud transcription and response generation. During an active live-conversation session, audio is streamed to the service through LiveKit. VozParking does not intentionally persist raw voice recordings in its Firebase database. Google Gemini processes request content to interpret parking needs and generate responses.

Location

Location access is foreground-only and is used to search for nearby parking and estimate distance or walking time. VozParking does not intentionally create or store a location-history profile.

Service Providers

VozParking uses Firebase for authentication, application data, and cloud functions; Google Gemini for AI processing; Google Maps Platform for parking and place searches; and LiveKit for live audio transport. These providers may process operational or security records under their own retention practices and legal obligations.

Personalization and Retention

Request text and selected parking actions are stored with your account only when personalization consent is enabled. You can change that setting in the app. Account data remains until it is deleted, subject to limited retention required for security, fraud prevention, legal compliance, or service provider backups.

Payments

VozParking does not collect or process real payment card details. Any Apple Pay interaction currently shown in the app is a simulated product experience.

Your Choices

You can deny microphone or location permission and continue using available typed-input features. You may also disable personalization consent. To permanently remove your account and associated VozParking data, use Settings > Delete Account or review the account deletion instructions.

Changes to This Policy

We may update this policy as the service changes. The effective date above identifies the current version.