Privacy Policy

1. Controller and privacy contact

RecipeGain is a product operated by Oleksandr Kanalosh Buildora, a sole proprietorship operated by Oleksandr Kanalosh in Poland.

Privacy questions and data-rights requests can be sent tooleksandr@recipegain.app.

This policy applies to recipegain.app and to RecipeGain applications for Android and Windows. The stable store-listing URL ishttps://recipegain.app/privacy/.

3. Data stored locally by the applications

RecipeGain is offline-first. Depending on your use, local application data can include ingredient and recipe names, categories, purchase quantities and prices, recipe composition and yields, preparation time and labor inputs, selling prices and tax inputs, Food Cost and profitability calculations, production-calculation history, settings, drafts and local entitlement state.

This business data is stored on your device. RecipeGain does not automatically upload your recipe library, ingredient prices or production calculations to the RecipeGain billing verifier.

The Android app also stores a randomly generated RecipeGain installation identifier and signed Premium entitlement lease in application support storage. Clearing application data or uninstalling the application removes this local state subject to normal operating-system behavior.

4. Android billing and Premium verification

Google Play purchases

Android Premium is sold through Google Play. Google Play handles the store account, payment method and payment transaction under Google's own terms and privacy rules. RecipeGain does not receive your payment-card or bank details.

To verify a subscription, the Android app sends the following over HTTPS to the RecipeGain billing verifier: the Google Play purchase token, package identifier, Premium product identifier, monthly base-plan identifier and the RecipeGain installation identifier.

The verifier uses the Google Play Developer API to check subscription status, product/base-plan identity, entitlement expiry and acknowledgement state and to acknowledge an entitled purchase when required. Google Play therefore processes the purchase token and subscription metadata as part of the verification request.

If verification succeeds, RecipeGain returns a cryptographically signed Premium lease bound to that installation. The app stores the signed lease locally and validates it before granting Premium.

Google Play reviewer access

Google Play reviewers may use a dedicated reviewer credential supplied in the protected Play Console review instructions. When a reviewer activates that path, the app sends the reviewer credential, package/product/base-plan identifiers and the RecipeGain installation identifier to the same verifier over HTTPS. The verifier compares the credential with a server-side secret and, if valid, returns a signed reviewer Premium lease. The reviewer path does not create a purchase.

Verifier storage boundary

The RecipeGain verifier is designed as a stateless service. Its application code does not create a user profile or customer database and does not persist purchase tokens, reviewer credentials or installation identifiers as application records. These values are processed to answer the current verification request.

The verifier runs on Google Cloud infrastructure. Google Cloud and Google Play may process technical request, security and operational metadata and retain logs according to the applicable service configuration and their terms. RecipeGain does not intentionally log request bodies containing purchase tokens or reviewer credentials.

5. Website and calculator information

The RecipeGain website is static-first. Website calculators perform their calculations in your browser and do not send the calculator values to a RecipeGain calculation backend.

Related calculator pages may use browser session storage to carry an exact result between pages. That state stays in your browser and is not a cloud recipe library.

Firebase Hosting and network infrastructure must process technical request information to deliver and protect the site. This can include IP address, time, requested URL, browser or user-agent information, response status and security or diagnostic metadata.

RecipeGain currently does not run website advertising tracking or a RecipeGain analytics measurement layer and does not intentionally set analytics or advertising cookies.

6. Backups, imports, exports, PDFs and sharing

Backup, Recipe Transfer, PDF and operating-system share/send functions are initiated by you. When you save or send a file outside RecipeGain, the destination you choose can receive and retain that copy under its own terms and privacy practices.

Deleting data inside RecipeGain does not delete copies you previously exported or shared elsewhere.

7. Information you send to RecipeGain

If you contact RecipeGain by email, RecipeGain receives the information you choose to provide, such as your email address, message, attachments and technical details. Please avoid sending recipe databases or other sensitive business data unless necessary for support.

8. Purposes and legal bases

Where the GDPR applies, RecipeGain processes personal data only with an appropriate legal basis. Depending on context:

• website delivery, security and abuse prevention rely on legitimate interests in operating and protecting the service;
• purchase verification and Premium entitlement processing are necessary to provide the purchased service and may also rely on legitimate interests in preventing fraud and unauthorized access;
• reviewer verification relies on legitimate interests in enabling secure app-store review without weakening production entitlement controls;
• support processing is based on taking requested steps, performing a service relationship or legitimate interests in responding to users;
• information may be processed where necessary to comply with legal obligations; and
• consent will be used where applicable law requires consent for a future optional processing feature.

9. Service providers, recipients and disclosures

Information can be processed by Google services used to operate RecipeGain, including Firebase Hosting, Google Cloud Run and Google Play, to the extent needed for website delivery, subscription verification, security and store operation. Email providers process support correspondence. Destinations selected by you process files or content you explicitly share with them.

RecipeGain may also disclose information where required by law or where necessary to establish, exercise or defend legal rights or protect users, the service or others.

RecipeGain does not sell personal information and does not share personal information for cross-context behavioral or targeted advertising.

10. Retention and deletion

Local application data

Local recipe/business data, the installation identifier and locally stored signed entitlement remain on the device until changed or deleted through the application/operating system, application data is cleared, or the app is uninstalled, subject to operating-system backup behavior. Signed entitlement leases also contain their own expiry boundaries.

Billing verifier

The verifier has no RecipeGain customer-account database and does not persist verification request bodies as application records. Google Cloud and Google Play can retain technical/security logs and transaction records according to their service configuration, legal obligations and platform rules.

Website and support

Browser session storage is controlled by your browser. Hosting/security logs are retained according to operational needs and provider settings. Support correspondence is retained only as long as reasonably necessary to answer the request, maintain security, resolve disputes and meet legal obligations.

11. Security

Billing and reviewer verification uses HTTPS. Premium leases are cryptographically signed and bound to the RecipeGain installation identifier. Private signing material and the reviewer credential are kept outside the application and public repository.

Reasonable technical and organizational measures are used for information RecipeGain receives, but no storage or transmission method can be guaranteed completely secure.

12. Your privacy rights

Where applicable law gives you rights of access, correction, deletion, restriction, objection, portability or withdrawal of consent, you can contact RecipeGain using the email above. Most recipe/business data is controlled directly on your device.

You may lodge a complaint with a competent data-protection authority, including the President of the Personal Data Protection Office (Prezes Urzędu Ochrony Danych Osobowych) in Poland, or the authority available to you under applicable law.

Requests concerning data independently controlled by Google Play, an operating system, an email provider or another third-party service may also need to be directed to that provider.

13. International processing

Website hosting, Google Cloud, Google Play, email/support infrastructure and destinations selected for sharing can process information in countries other than your own. Where RecipeGain is responsible for an international transfer, safeguards required by applicable law will be used.

14. Children

RecipeGain is a business recipe-costing utility and is not directed to children under 13. RecipeGain does not operate a child-focused account service.

15. Changes to this policy

RecipeGain will update this policy when data practices materially change, including before activating analytics, crash reporting, advertising, cloud accounts/synchronization or another processing capability that is not described here.

Privacy questions or requests:oleksandr@recipegain.app.