Privacy Policy
The short version: Petla stores the account, profile, plant, journal, community, subscription, and notification data needed to run the app. We do not sell personal data.
Who we are
Petla is operated by Kameleonic Design, based in England, UK. When this policy refers to "Petla", "we", "us", or "our", it means Kameleonic Design trading as Petla.
Correspondence address: Unit 167204, PO Box 7169, Poole, BH15 9EL.
You can contact us at hello@petla.uk.
What this policy covers
This policy covers the Petla mobile app, the Petla website at petla.uk, and the related support, legal, referral, and account pages we operate.
Data we collect
Depending on how you use Petla, we may collect and store:
- Your email address and Petla account ID for sign-in, account management, password reset, and service access
- Google account sign-in data when you choose Google sign-in
- Profile information such as display name, bio, avatar, location text, and UK postcode
- Plant, garden, journal, community, and swap content that you create in the app
- Photos you upload for avatars, journals, posts, swaps, gardens, and plant identification
- Subscription and entitlement status needed to provide paid features
- Notification-related identifiers and interaction events needed to deliver push notifications
- Operational app activity events, such as journal and notification-open events, that we log to run and improve the service
- Prompts or messages you submit when using Ask Petla, along with related response or usage records needed to operate that feature
How we use your data
We use your data to provide and operate Petla, including account creation, sign-in, profile display, plant care features, journals, community features, swaps, weather-aware reminders, plant identification, subscriptions, push notifications, support, safety, troubleshooting, and fraud or abuse prevention.
Core service providers and processors
Petla uses the following service providers to operate the app:
- Supabase for authentication, database storage, file storage, and backend functions
- Google for Google sign-in when you choose that account login method
- OneSignal for push notification delivery and notification interaction handling
- RevenueCat for subscription management and entitlement syncing
- Google Play and Apple App Store billing systems for in-app subscription purchases and renewals
- Plant.id for plant identification when you submit a plant photo for analysis
- OpenAI and Hugging Face for Ask Petla response generation — your prompts may be processed by either provider depending on system configuration at the time of your request
- Google Vision SafeSearch for moderation checks on community post images
- postcodes.io and Met Office Weather DataHub for postcode-based location lookup and weather-aware features
International data transfers
Some of Petla's service providers are based outside the UK. Where personal data is transferred internationally, Petla relies on the following mechanisms:
| Processor | Location | Transfer basis |
|---|---|---|
| Supabase | EU (Ireland) | UK adequacy regulation — EU/EEA adequate |
| Plant.id | Czech Republic (EU) | UK adequacy regulation — EU/EEA adequate |
| RevenueCat | United States | UK–US Data Bridge or International Data Transfer Agreement (IDTA) |
| OneSignal | United States | UK–US Data Bridge or International Data Transfer Agreement (IDTA) |
| OpenAI | United States | International Data Transfer Agreement (IDTA) |
| Hugging Face | United States | International Data Transfer Agreement (IDTA) |
| Google (Sign-in, Vision, Play) | United States / EU | Google's IDTA-compliant Data Processing Agreement |
| postcodes.io | United Kingdom | No transfer — domestic processing |
| Met Office DataHub | United Kingdom | No transfer — domestic processing |
For provider Data Processing Agreements or privacy addenda, links are available on request at hello@petla.uk.
Photos and plant identification
Photos you upload to Petla are used for the feature you chose, such as avatars, journals, community posts, swap listings, or garden images.
If you use plant identification, the image you submit is sent for processing through Petla's backend to Plant.id. Petla stores the identification result and image hash needed for the feature. The app does not keep the original identification photo as part of the long-term identification cache.
If you upload a community post image, Petla may also send that image through backend moderation checks using Google Vision SafeSearch so we can operate community safety controls.
Social sign-in
If you choose Google sign-in, Petla uses Google through Supabase Auth to complete authentication and create or access your Petla account.
Community and user-generated content
Profile details, community posts, comments, shared garden details, and swap listings may be visible to other users where the relevant feature is designed to be social or public within the app.
Location data
Petla uses approximate location information that you enter, such as a postcode or location text, to support weather-aware reminders, frost alerts, and location display features. For postcode-based weather features, Petla's backend currently uses postcodes.io and Met Office Weather DataHub. We do not state that the app collects precise GPS location in this policy.
Subscriptions
If you subscribe, RevenueCat and the relevant app store billing provider process purchase and entitlement data so Petla can unlock paid features. Petla account deletion does not itself cancel an app store subscription. You must manage or cancel recurring billing in Google Play or the App Store.
Push notifications
If you enable notifications, Petla uses OneSignal to route pushes to your device and associate notification delivery with your Petla account. This may involve app or service identifiers used for push delivery.
Analytics and service operations
Petla does not use a third-party mobile analytics SDK in the audited app build. Petla does log first-party operational events to Supabase, including events such as journal activity metadata and notification-open events.
Ask Petla
If you use Ask Petla, the prompts or messages you submit are sent to Petla's backend to generate a response. Those prompts, related plant context, and response records may be processed or stored through service providers including OpenAI (US) or Hugging Face (US), depending on system configuration at the time of your request. Do not submit sensitive personal data that is not necessary for your request.
Legal bases
Under UK GDPR Article 13(1)(c), we are required to state the specific legal basis for each processing activity:
| Processing activity | Lawful basis | UK GDPR Article |
|---|---|---|
| Account creation, sign-in, and password reset | Performance of contract | 6(1)(b) |
| Profile, community, and swap features | Performance of contract | 6(1)(b) |
| Subscription management (RevenueCat, App Store) | Performance of contract | 6(1)(b) |
| Push notifications | Consent | 6(1)(a) |
| Optional profile details (bio, postcode) | Consent | 6(1)(a) |
| Plant identification (user-initiated) | Performance of contract | 6(1)(b) |
| Ask Petla prompts and response records | Performance of contract | 6(1)(b) |
| Operational event logging and first-party analytics | Legitimate interests | 6(1)(f) |
| Safety, fraud, and abuse prevention | Legitimate interests | 6(1)(f) |
| Community image moderation (Google Vision) | Legitimate interests | 6(1)(f) |
| Legal obligation compliance | Legal obligation | 6(1)(c) |
How long we keep data
We retain data for the periods set out below, or longer where required by law or for the defence of legal claims:
- Account and profile data: Retained while your account is active; queued for deletion within 30 days of account deletion, subject to legal holds.
- Financial and subscription records: Retained for 7 years from the date of the transaction to comply with HMRC record-keeping requirements.
- Community content and UGC: Deleted with your account unless retained under a moderation hold; moderation records retained for up to 12 months.
- Operational log data (event logs): Retained for up to 6 months for service improvement and debugging, then deleted.
- Ask Petla prompts and responses: Petla-stored conversation records retained for up to 90 days; downstream provider retention is governed by OpenAI's and Hugging Face's own policies.
- Backup copies: Purged within 90 days of account deletion.
- Provider-managed records: Governed by each provider's own retention policy (for example, RevenueCat billing history, OneSignal delivery identifiers). Links to provider policies are available on request.
Deletion and export
You can request deletion of your Petla account and Petla-stored data in the app, or through our account deletion page at petla.uk/account/delete. You can also export a JSON copy of your account data from the Settings screen before deleting your account.
Some provider-managed records, such as app store billing history, provider-side service identifiers, or third-party processor records retained under their own policies, may be retained separately under those providers' policies.
Security
Petla is intended to use encrypted HTTPS connections for production traffic. We also rely on our infrastructure providers' security controls for storage and service delivery.
Your rights
Subject to applicable law, you may have rights to access, correct, delete, restrict, object to, or export personal data we hold about you, and to lodge a complaint with the Information Commissioner's Office.
Where we process your data on the basis of consent — for example, push notifications or optional profile details — you have the right to withdraw that consent at any time. You can do this by disabling notifications in your device settings or removing optional profile information in the app. Withdrawing consent does not affect the lawfulness of processing carried out before withdrawal.
To exercise your rights or ask a privacy question, email hello@petla.uk.
Changes to this policy
If we make material changes, we will update the date at the top of this page and publish the revised version here.
Contact
Questions about this policy or how Petla handles data: hello@petla.uk