Privacy Policy

Plena is provided by Captiogia Ltd, a company registered in England and Wales. References to “Plena”, “we”, “us” and “our” in this policy mean Captiogia Ltd.

We are the controller of the personal information processed in connection with the Plena mobile application and getplena.com. This policy explains what information we process, why we process it, the organisations that receive it, and the choices and rights available to you.

For privacy enquiries or requests concerning your personal information, contact hello@getplena.com.

Account information. When you register, we process your email address, name, account identifier and account creation date. Where available, we receive profile information from your chosen sign-in provider, including a profile image URL. If you use Apple’s Hide My Email feature, we receive the relay address supplied by Apple.

Firebase Authentication manages your sign-in credentials. We do not receive your Google or Apple password.

Preferences and nutrition information. We process the preferences you provide, including dietary restrictions, allergies, intolerances, excluded ingredients, preferred foods and cuisines, cooking preferences and nutrition goals. Allergy and intolerance information may constitute health information. Some dietary information may reveal religious beliefs.

Recipes, plans and other content. We process ingredients and instructions submitted for recipe generation, saved and favourited meals, meal plans, ratings and calculated nutrition information. Shopping lists, saved searches and some preferences are stored locally on your device. Information submitted through scanning, dictation or recipe-generation features may also be processed by our servers and providers.

Support and feedback. If you contact us or submit feedback, we process your message and relevant account details. In-app feedback also includes your account identifier, email address, feedback category, app version and device platform.

Purchase information. Apple or Google processes payments for purchases made through their stores. We do not receive your payment card details. RevenueCat manages subscription entitlements and processes purchase history, product identifiers, subscription status and customer identifiers associated with your Plena account.

Usage and diagnostic information. We use Firebase Analytics and Firebase Crashlytics to understand app usage and investigate faults. These services process information such as app interactions, screen views, purchase events, saved recipe names, installation identifiers, device and operating-system information, and crash reports. We associate certain records with your Plena account identifier.

We also maintain account usage counters to apply the limits associated with your plan.

Technical records. Our infrastructure processes IP addresses and technical information associated with requests. Application logs may also include account identifiers, submitted ingredients, dietary filters, generated results and error information.

Notifications. Notification services process device registration identifiers and, where applicable, push tokens to deliver notifications. A history of notifications received by the app is stored locally on your device.

Website enquiries and waitlist registrations. If you join the waitlist, we process your email address, the source of your registration and its date. We use this information to send the Plena availability updates you requested. You may ask to be removed by emailing us.

Camera, photo-library, microphone and speech-recognition access is used for the features you choose to activate. Where operating-system permission is required, the app requests it before accessing the relevant resource.

When you scan a photograph, the selected image is transmitted to our backend and an AI provider to identify ingredients or shopping-list items. Plena’s extraction endpoint processes the image temporarily and does not create a saved photograph in your account.

This does not mean that every organisation involved deletes the image immediately. AI providers and diagnostic services may retain request content as described below.

Voice input uses your device’s speech-recognition service, which may process audio on Apple’s or Google’s servers. Plena does not record or retain the audio. The recognised text, or portions requiring further interpretation, may be transmitted to our backend and AI provider to identify ingredients.

Extracted ingredients and recognised text may subsequently be retained where you save them in a list, search, recipe or other app content.

You may manage device permissions in your device settings. Declining a permission prevents the associated capture feature from operating but does not require you to grant unrelated permissions.

We use Anthropic’s commercial API for recipe generation and ingredient extraction. Depending on the feature, requests include ingredients, recipe instructions, dietary preferences, allergies, intolerances, exclusions, nutrition requirements or a selected image.

We do not deliberately include your name, email address or Plena account identifier in recipe-generation prompts. However, text or images you submit may themselves contain identifying information.

Anthropic’s commercial services do not use inputs or outputs for model training by default. Its standard API retention arrangements allow inputs and outputs to be retained for up to 30 days, with exceptions for legal requirements, policy enforcement and other applicable arrangements. Anthropic’s training policy, API retention information.

We also use LangSmith, operated by LangChain, to record AI request and response traces for troubleshooting and evaluating recipe quality. Traces may contain submitted ingredients, dietary or health information, image content, and generated responses. LangSmith’s standard trace retention periods are 14 days for base traces and 400 days for extended traces. Information copied into evaluation datasets is subject to separate retention arrangements. LangSmith retention information.

Development and internal testing may use OpenRouter to route requests to alternative model providers. It is not the provider configured for the production service.

AI-generated recipes and nutrition information may be inaccurate. Plena is not a medical service. Check ingredients and allergen information independently where necessary, and seek professional advice concerning medical dietary requirements.

We do not use AI to make decisions about you that produce legal or similarly significant effects.

We process personal information to:

• Create and maintain your account and authenticate access.
• Generate and personalise recipes and meal plans.
• Store supported account content and make it available across your devices.
• Provide ingredient extraction and voice-input features.
• Manage subscription entitlements and usage limits.
• Deliver notifications and communications you request.
• Respond to support enquiries and feedback.
• Analyse app usage, investigate faults and improve the service.
• Protect the service against abuse, fraud and security incidents.
• Meet applicable legal obligations.

Where UK or EEA data protection law applies, our legal bases include performance of our contract with you, consent, legitimate interests and compliance with legal obligations.

Our legitimate interests include securing the service, preventing abuse, resolving faults and improving its operation. Where consent is required for device access, communications or another processing activity, that consent may be withdrawn.

Where we rely on consent to process health information or other special-category information, the consent must be explicit. Providing this information is optional. You may remove it from your preferences or contact us to withdraw consent and request deletion. Withdrawal does not affect the lawfulness of processing carried out beforehand.

Device permission and consent to the processing or disclosure of personal information are separate matters.

We use the following providers in operating Plena:

We require providers acting on our behalf to protect personal information consistently with this policy and applicable data protection requirements. Their access is limited to the purposes for which they provide their services.

Apple, Google and other organisations may also process information independently when you use their own services. Their privacy notices apply to that processing.

We use USDA FoodData Central as a source of food and nutrition reference information. We do not deliberately send account information to the USDA.

We may disclose information where required by law, to establish or defend legal claims, or where necessary to protect the service or others. Information may also be transferred as part of a business reorganisation or sale, subject to applicable safeguards and notice requirements.

We do not sell personal information or disclose it to data brokers.

Our backend is hosted on Google Cloud infrastructure in Belgium. Other services may process information in different locations, including the United States. Our LangSmith configuration uses its European endpoint; this does not establish that all related processing occurs exclusively within the EEA.

Where a transfer requires protection under UK or EEA data protection law, we use an applicable transfer mechanism, such as an adequacy arrangement or approved contractual safeguards.

You may contact us for information about the safeguards applicable to a particular transfer.

We retain account information and saved account content while your account exists, subject to your requests to remove supported content or delete the account.

Other records have different retention arrangements:

• AI request content and traces are subject to the provider arrangements described in section 4.
• Analytics records are retained under the retention settings configured for the relevant Analytics service.
• Firebase Crashlytics retains crash reports and associated identifiers for 90 days before beginning removal from its systems. Firebase retention information.
• In-app feedback is included in account exports and deleted when you delete your account. Support correspondence submitted separately may remain to investigate the enquiry and maintain related correspondence; you may request its deletion separately.
• Purchase records may be retained to administer purchases, refunds, disputes and applicable accounting obligations.
• Infrastructure logs and backups are retained according to their configured rotation and retention arrangements.
• Waitlist registrations remain separate from app accounts and may be removed by contacting us.

When deciding whether continued retention is necessary, relevant factors include the purpose of the record, unresolved support or security matters, applicable legal obligations, and whether the information can instead be deleted or anonymised.

Deletion of your Firebase Authentication account does not, by itself, delete or anonymise historical records held by other services.

You may delete your account using Profile → Delete Account in the app or request deletion at getplena.com/delete-account.

The website process sends a confirmation link to the address associated with your account. Deletion proceeds after you open the link and confirm the request.

The account-deletion process removes your Firebase Authentication record, profile and saved account content, daily usage records, meal plans, ratings and in-app feedback from the account stores covered by that process. Deletion is permanent.

After account content is removed, a temporary security marker prevents late requests from recreating it. This marker contains no profile content and is scheduled for automatic removal after two hours; database cleanup is asynchronous and may take longer.

Local information is cleared by the in-app deletion process where supported. A request made through the website cannot directly erase information stored on every device. You may also remove locally stored information through the app or your device’s controls.

Account deletion does not automatically remove all historical support, diagnostic, AI-processing or purchase records. The retention arrangements in section 8 apply. You may contact us to request deletion of remaining personal information, subject to applicable exceptions.

Deleting your account does not itself cancel an automatically renewing subscription. Manage cancellation through the App Store or Google Play.

Depending on the law applicable to you, you may have rights to access your personal information, obtain a copy, correct inaccuracies, request deletion, restrict processing, object to processing, and withdraw consent.

Contact hello@getplena.com to exercise these rights. We may request information reasonably necessary to verify your identity. We will respond within the period required by applicable law, normally one month for requests under UK or EU data protection law. Where a permitted extension is necessary, we will explain it.

Rights are subject to applicable conditions and exceptions. If we cannot fulfil a request in whole or in part, we will explain the reason.

You may complain to the relevant data protection authority. In the United Kingdom, this is the Information Commissioner’s Office. EEA residents may contact their local supervisory authority.

We do not discriminate against individuals for exercising applicable privacy rights.

We use technical and organisational measures intended to protect personal information, including encrypted connections, authentication, access controls and app-integrity checks. No service can guarantee complete security.

The app stores session information, preferences and local content on your device. Analytics and other SDKs also use installation identifiers and related storage technologies.

The website does not use advertising cookies, behavioural analytics or session-replay tools. Our hosting infrastructure still processes the technical information required to deliver and protect the website.

Plena is not directed at children under 13, and we do not knowingly collect personal information from them.

Additional requirements may apply where a young person cannot independently consent to a particular processing activity under local law. If you believe a child has provided personal information in circumstances where it should not have been collected, contact us.

We may update this policy when our services, processing activities or legal requirements change. The revised version will be published at getplena.com/privacy with an updated date.

Where required, we will provide additional notice or obtain fresh consent before introducing a new processing activity.

For questions about this policy or requests concerning your personal information, contact hello@getplena.com.