Privacy
Vero+ Privacy Policy
Mobilogical LLC (“Mobilogical,” “we,” “us”) operates Vero+. This policy describes the information processed by the Vero+ mobile app and its supporting services.
Information Vero+ processes
Anonymous account and app choices
On first production launch, Firebase Authentication creates a random user identifier. Vero+ associates that identifier with your selected home beach, free-feature usage, membership entitlement state, and event-topic choices. Generated and saved plans remain on the device. No in-app profile name or email address is required.
Planner requests
Text you submit to the planner is sent through an authenticated Firebase callable to the Google Gemini API to generate an itinerary. Do not enter sensitive personal information. Vero+ does not store the prompt or generated itinerary on its backend.
Notifications and device information
If a member enables event alerts, Firebase Cloud Messaging provides a device registration token. Vero+ stores the token, platform type, and selected topics. Vero+ does not access your contacts.
Purchases and membership
Apple or Google processes payment. RevenueCat provides Vero+ with product, purchase, expiration, and entitlement status tied to the anonymous Vero+ identifier. Vero+ does not receive your full payment card number.
Backend logs
The app does not include third-party client analytics, attribution, or crash-reporting SDKs. Google Cloud logs backend requests and operational failures for Firebase Functions.
Place photographs
When Vero+ requests a photograph for a published place, its backend sends that place’s Google Place ID to Google Maps Platform. Google returns a short-lived photo address and any source or author attribution required for display. Vero+ does not send your precise location, planner text, name, or email with this request and does not store Google photo files or photo resource names.
Support communications
If you email support, we receive the email address and information you choose to include. This information is not collected through the app unless you choose to contact us.
Why we use information
- Provide saved choices, free limits, plans, and membership access.
- Deliver alerts that you explicitly enable.
- Prevent abuse and enforce paid entitlements server-side.
- Diagnose backend failures.
- Respond to support, correction, privacy, and safety reports.
- Comply with store, accounting, fraud-prevention, and legal duties.
Processors and retention
The following periods are maximum operational targets for Vero+-controlled records. A shorter period applies when you use in-app deletion, except where a processor or store must retain limited records for security, fraud, tax, or legal obligations.
| Processor | Purpose and data | Retention |
|---|---|---|
| Google Firebase Authentication and Firestore | Anonymous UID, home beach, free usage, and entitlement state | Until in-app deletion. |
| Google Gemini API | Planner request processing and generated response | Vero+ does not create a raw-prompt or generated-plan database. Google processes the request under its applicable service terms. |
| Google Maps Platform / Places API | Published place identifier, short-lived place-photo address, and source or author attribution | Vero+ stores the Google Place ID used to identify the listing. Photo resource names and image addresses are requested on demand and are not stored in the Vero+ database. |
| Firebase Cloud Messaging | Registration token and selected alert topics | Until alerts are disabled, membership ends, or in-app deletion succeeds. |
| RevenueCat | Anonymous app user ID, products, transactions, and entitlement | The Vero+ subscriber profile is requested for deletion during in-app deletion. RevenueCat and the app stores may retain limited transaction records as required for financial, fraud, or legal obligations. |
| Google Cloud Logging | Backend security and operational logs | 30 days in the standard Vero+ logging bucket. |
| Apple App Store or Google Play | Download, purchase, subscription, and store-account records | Controlled by Apple or Google under their policies and legal duties; Vero+ account deletion does not delete a store account. |
Sharing and sale
We disclose data only to the processors above, when you direct us, or when required for legal, security, or corporate-transition purposes. We do not sell personal information. We do not share it for cross-context behavioral advertising.
Your choices and deletion
- Notification permission can be changed in device settings, and alert topics can be disabled in Vero+.
- Store subscriptions are managed in the App Store or Google Play.
- In Vero+, open You → Your data → Delete my data and type DELETE. This deletes the anonymous Firebase account, Vero+-controlled Firestore and messaging data, local app preferences, and requests deletion of the RevenueCat subscriber profile. It does not cancel store billing.
- If you cannot access the app, follow the web deletion instructions.
You may also request access, correction, or deletion of support data by emailing drew@mobilogical.com. We may ask for limited information to verify that a request concerns your device or support conversation.
Security and international processing
Vero+ uses transport encryption, authenticated callables, server-side entitlement checks, and restricted provider credentials. No system is perfectly secure. Processors may handle data in the United States and other locations where they operate.
Children
Vero+ is a general-audience local guide and is not directed to children under 13. We do not knowingly request a child’s name, email, precise location, or contacts. A parent or guardian who believes a child provided personal information should contact us for deletion.
Changes
Material changes will be posted here with a new effective date. If a change materially expands data use, we will provide any notice or choice required by applicable law.
Contact
Mobilogical LLC
Florida, United States
drew@mobilogical.com