Skip to content
PPantry Chef

Privacy Policy

How Pantry Chef processes account and recipe information, uses service providers and handles privacy requests under POPIA.

Last updated:

1. Responsible party and Information Officer

Global Application Solutions (Pty) Ltd ('GASCO'), registration 2001/006292/07, is the responsible party operating PantryChef under the Protection of Personal Information Act 4 of 2013 (POPIA). Registered office: 255 Anna Wilson Street, Kilnerpark, Pretoria, Gauteng, 0186, South Africa. Corporate contact: https://gasco.digital/contact. Send PantryChef privacy enquiries to support@pantrychef.co.za. Information Officer: [PLACEHOLDER: confirm the appointed officer and applicable registration details]. These PantryChef-specific disclosures apply to recipe, account and optional Anthropic processing; policies for GASCO’s other services do not replace them.

2. Information we collect

We process account details such as name, email address and authentication information; recipes and recipe photos you save; pantry, meal-plan and shopping-list information; consent preferences; and technical information reasonably needed to operate and secure the service.

Information is collected directly when you register, sign in, save content or contact support. Recipe imports also collect the source content you submit or ask us to fetch. Sign-in and security records can include IP addresses, browser/user-agent information and session times. Password-based sign-in stores password hashes, not plaintext passwords. The current account form does not request a telephone number, identity number or card details.

We record content-free Claude usage information, such as timestamps, import type, result category, token counts and estimated cost, for limits, billing safeguards and support. We do not intentionally include recipe text, photos, API keys or raw provider responses in that usage history.

We already hold account plan, trial and usage-limit information. Paid checkout is not active, and there is no live paid order history in this checkout flow. When paid billing is enabled, necessary payment metadata may include transaction references, provider customer/subscription references, billing interval and payment status. PayFast will handle the payment details; Pantry Chef will not store your card number or card security code.

4. Claude recipe imports and your choice

Claude is used only to read a recipe you submit through a link or recipe image, not for unrelated AI tasks. With consent, selected source-page recipe content or a resized recipe image stripped of embedded metadata may be sent to Anthropic. The image can still contain visible personal information, so check it before uploading.

You can withdraw Claude consent using the available import consent controls. Withdrawal stops future Claude processing; it cannot undo processing already carried out. Free website parsing or local OCR can be offered where supported and is labelled separately. Already saved recipes remain subject to your normal account controls.

Recipe imports use Anthropic’s standard commercial API retention arrangement, not a zero-data-retention agreement. API inputs and outputs are not used for model training by default and are normally deleted by Anthropic within 30 days, with longer retention possible for flagged content or legal requirements. A material change to the consent disclosure requires renewed consent before further Claude processing.

5. Who receives information

Pantry Chef is self-hosted on infrastructure at xneelo in South Africa. Uploaded recipe cover photos are stored on the Pantry Chef server. Account sign-in uses the application’s email/password authentication service. Operational email is used for verification, password resets and service notices. Anthropic processes consented Claude imports; PayFast is the intended processor for payments once enabled, not an active checkout provider yet. Providers may process information according to their role, agreements and legal obligations. [PLACEHOLDER: confirm backup provider, backup locations and expiry schedule, operational email provider and processing locations, and the deployed provider agreements.]

A recipe-link import contacts the source website; it will receive normal network-request information. We do not sell your personal information. Information may be disclosed where lawfully required or reasonably necessary to protect rights and investigate abuse, subject to applicable safeguards.

Service providers receive only the information reasonably needed for their role and must be subject to appropriate confidentiality, security and operator arrangements where required by POPIA. Any lawful business transfer must include safeguards for personal information and appropriate notice; it is not permission for unrelated advertising or unrestricted reuse.

6. Cross-border transfers

Some providers may process information outside South Africa. Where POPIA section 72 applies, we must use an appropriate lawful basis and safeguards for that transfer, such as adequate protection, a binding agreement or another permitted basis.

[PLACEHOLDER: list the actual provider countries and applicable transfer safeguards after confirming hosting, email, authentication, payment and Anthropic arrangements.]

7. Retention and deletion

Recipes and related account data are generally retained while your account remains open, including on Free after a paid subscription ends, subject to the proposed inactivity policy below. You can export recipes and request account deletion. Subscription cancellation does not itself delete an account.

Planned inactive Free-account policy: a Free account may be deleted after 12 months without use, with at least 30 days’ advance warning by email so you can return to the service or export your recipes. Automatic inactivity deletion is not currently enabled. [PLACEHOLDER: confirm how signed-in activity is measured, how returning to the service resets inactivity, notice delivery and the deletion process before enabling this policy.]

Content-free Claude usage history is kept for 90 days. Necessary financial and legal records may need to be retained longer after billing starts. [PLACEHOLDER: confirm lawful financial-record retention, security-log retention, deletion turnaround, and the backup expiry/deletion schedule.]

Information legally required for disputes, fraud prevention or compliance may be restricted and retained for the necessary period rather than immediately erased. We will explain applicable exceptions when responding to a deletion request.

8. Security

We use reasonable technical and organisational measures appropriate to the information and risks, including access controls and protected communications. No online service can guarantee absolute security. Keep your account password secure and report suspected misuse to support@pantrychef.co.za.

Where required, a security compromise will be reported to the Information Regulator and affected people in accordance with POPIA. [PLACEHOLDER: confirm the incident-response contact and process.]

9. Your rights and requests

Subject to applicable law, you may request access to your personal information, correction, deletion, objection to processing, or withdrawal of optional consent. You can export recipe data in JSON on every plan, including after cancellation. Exporting recipes is not the same as receiving a complete personal-information access response.

Contact support@pantrychef.co.za to exercise privacy rights. We may reasonably verify your identity without collecting excessive information. Our support acknowledgement target is 24–48 business hours, excluding weekends and South African public holidays; this is not a promise to complete a deletion or access request within that period. [PLACEHOLDER: verify operational capacity, legally applicable response deadlines, prescribed forms and any lawful fees before publishing a final request-handling timeframe.]

You may complain to South Africa’s Information Regulator. Official information and complaint channels are available at https://inforegulator.org.za. You do not have to obtain our permission before contacting the Regulator.

10. Cookies, notices and updates

The application uses an essential Better Auth sign-in cookie and service-worker asset caching. No optional analytics or advertising tracker is configured in the reviewed application. The Cookie Policy explains the actual storage, its purposes, duration and browser controls. Any future non-essential tracking must be disclosed and any required consent obtained before it runs.

The current email/password session is configured for a seven-day lifetime, refreshed during continued use. No optional theme-preference persistence is enabled in the active application. Blocking essential cookies can prevent sign-in and protected features from working. Device/session records and operational security monitoring are distinct from optional advertising tracking.

We will send service communications only, such as account, security, support, inactivity notices and, once enabled, billing messages. We will not send optional marketing emails under this policy. Material privacy changes will be explained through an appropriate notice, and this page’s Last updated date will change.