1. Scope
This policy explains how the GENEVIEVE App™ Dog Park website and future mobile applications handle information relating to users, dog profiles, park visits, journey planning, supervision confirmations, social-affinity relationships, compatibility and heat assessments, incidents, maintenance, subscriptions and support.
2. Information that may be collected
- Account and contact information supplied by a user.
- Owner-controlled dog profile, behavioural, health, vaccination, document-reminder, photograph and emergency information.
- Voluntary, time-limited park check-ins and check-outs, owner-supervision confirmations, current dog status and optional approximate or precise location where a user elects to participate.
- Journey, route, heat, weather, surface, shade, water and hazard inputs.
- Compatibility predictions, prospective recommendations, affinity relationships, observed outcomes and private relationship-removal feedback.
- Lost/found, incident, witness, maintenance and council/operator notice records.
- Subscription status and transaction references supplied by Apple, Google Play or Stripe. Full payment-card details are not intended to be stored by GENEVIEVE App™.
- Technical and security logs when production services are enabled.
3. Purposes
Information may be used to provide requested functions, secure accounts, synchronise data, calculate decision-support outputs, deliver owner-selected alerts, administer subscriptions, investigate misuse, respond to support, maintain park operations, improve the service using permitted feedback and comply with law.
4. Visibility and role controls
Public dog information, private owner information, restricted emergency information and park-operator information must remain separated. Park superintendent views should use anonymous trends and facility information and should not expose microchip numbers, medical records or owner contact information without a justified, authorised and audited emergency purpose.
5. Voluntary check-in data
Check-in and check-out are optional in the current community pilot. The app records an expected visit length and automatically expires the record to reduce stale presence information. A user may continue without checking in. Production analytics should distinguish voluntary estimates from official attendance data.
6. Location and weather
Precise location is optional. Manual weather entry remains available. When a user enables location and requests current weather, the browser may send latitude and longitude directly to the configured weather provider. The current web build is configured for Open-Meteo. Production hosting, maps, email, analytics, authentication and notification providers must be identified before launch.
7. Security and retention
Production services should use appropriate access controls, encryption in transit, credential management, logging, backup and retention rules. Information no longer required for a lawful purpose should be deleted or de-identified, subject to lawful incident, payment or dispute retention.
8. Access, correction and deletion
Users can export or delete local browser data from the app. Production accounts must provide in-app deletion and a public web deletion request path. Users should be able to correct owner-entered data and challenge or update inferred behavioural information.
9. Complaints
A public support email and complaint process must be published before launch. Privacy complaints should be assessed and answered within a reasonable period.
Operator: Tracey Ann Kennedy trading as GENEVIEVE App™. Public support email: [ADD PUBLIC SUPPORT EMAIL BEFORE LAUNCH]. Public website: [ADD VERIFIED DOMAIN BEFORE LAUNCH].