Privacy Policy

Last updated: 16 July 2026  ·  Effective: 16 July 2026

This Privacy Policy explains what personal data we process, why, who we share it with, and the rights you have. It covers the apps published by Magoflow — including Amity (iOS and Android) and Spanbe — together with the magoflow.com website and related APIs (collectively, the "Services").

If you use a feature that involves wellness, nutrition, allergy, calorie, weight, or similar information, please also read our Consumer Health Data Privacy Policy.

1. Who we are

The Services are operated by Magoflow, the trading name of IT SERVICES MAREK PIETKIEWICZ ("Magoflow", "we", "us", "our"). For the purposes of the EU General Data Protection Regulation (GDPR), the UK GDPR, and other privacy laws that apply to the relevant Service, market, or processing activity, Magoflow is the data controller of the personal data described in this policy unless we say otherwise for a specific feature or channel.

Legal entity and registered address: IT SERVICES MAREK PIETKIEWICZ, NIP 5542598947 / REGON 341623872, ul. Irysowa 16, 86-031 Osielsko, Poland.

Privacy contact: [email protected]. General support: [email protected].

2. Scope: our apps and website

This policy applies when you:

• download, install, or use one of our apps — including Amity (a local-first focus and screen-time app for iOS and Android) and Spanbe (a meal-planning and nutrition app) — or any other Magoflow app or service that links to this policy;
• visit or interact with magoflow.com or our APIs; or
• contact us for support or other reasons.

Some apps publish app-specific legal documents (for example, Spanbe's privacy policy and related documents at spanbe.com). For those apps, the app-specific documents apply in addition to this policy and, where they conflict for that app, the app-specific documents prevail. Each app collects only the data its own features need — the sections below indicate which practices apply to which app.

Our apps are tools that you use on your own device, for yourself. They are not parental-control or employee-monitoring products, and they are not designed to let one person monitor another. Where you create your own configuration locally on your device, you control that information directly.

3. The data we collect and why

3.1 Information you provide

• Account / sign-in data. If you create an account or sign in, we process your email address and, depending on the method you choose, an identifier from Sign in with Apple or Google Sign-In (and, where you allow it, your name). If you use email/password, we store your email and a hashed password (we never store your password in plain text). Some apps (such as Spanbe) require an account for cloud features; others (such as Amity) can be used without an account.
• Onboarding and profile answers. During setup an app may ask you things such as a first name or nickname, an optional age, your language, and your goals. In Amity, we also optionally ask your gender (female, male, non-binary, or prefer not to say) — this is purely to help us make the app better for everyone, it's not tied to your identity, and you can skip it. This profile is stored on your device to personalise the app and is not collected by us in normal use. In Spanbe, your meal-planning inputs (such as dietary preferences, ingredient exclusions and allergies, calorie targets, and activity level) are stored with your account so your plans can be generated and synced — see Health & other sensitive data.
• Content you create in an app. In apps with cloud features, content such as saved meal plans, shopping lists, quick meals, progress entries, ratings, and feedback is stored with your account so those features work across sessions and devices.
• Support communications. If you email us, we receive your message, your email address, and anything else you include.

3.2 Information created on your device (local-first features)

Where a feature is designed to be local-first, its data lives only on your device (using secure on-device storage), and we do not receive, store, or have access to it unless you separately send it to us (for example, by attaching a screenshot to a support email). In Amity this includes: the apps and websites you choose to block, your streaks, and your settings (theme, language, notification style). Your blocking profiles and onboarding answers are also stored on your device, but see Section 3.4: the analytics we collect include some values from them — for example whether Sleep Time is on and the hours you chose, the length of a daily limit, and which onboarding steps you completed. Those events never identify which app or website a rule applies to. Where any of our apps describes a feature as on-device or local-only — for example, analysing documents or files you import — that processing likewise happens entirely on your device and the underlying content is not transmitted to us.

3.3 Subscription and purchase data

Our apps offer optional paid subscriptions. Purchases made in the apps are processed by Apple (App Store / StoreKit) and Google (Google Play Billing), and managed through our subscription provider RevenueCat. If we later add another payment method, the purchase flow will identify the relevant provider and its terms before checkout. We receive your subscription status, plan, entitlements, trial dates, refund/revocation status when provided by the store, and a pseudonymous app-user identifier (which may be linked to your account identifier or email). We do not receive your full payment card number or bank-account details for App Store or Google Play purchases. See our Subscription Terms & Refunds.

3.4 Diagnostics, analytics, and crash reports

To keep our apps working and improve them, we may collect limited diagnostic information through Google Firebase (Analytics and Crashlytics) and, where enabled, our own diagnostics endpoint. This may include:

• app events such as completing onboarding, viewing the paywall, starting a trial, or using a feature — including which steps of onboarding you complete (for example, that you set a goal or answered the gender question, but never the content of your answers), so we can see where people drop off and improve the flow. In Amity, this never includes the identities of the apps you block;
• crash reports and technical error logs (including a redacted error message, the type of failure, app version, device model, and operating-system version);
• a Firebase messaging token, but only where you enable notification features and the platform provides one;
• approximate, network-derived location (such as country/region, inferred from IP address) and coarse device/locale information.

We configure these tools for product and stability purposes only. We do not use the Advertising Identifier (IDFA/GAID) for tracking, and our iOS privacy manifests declare that our apps do not track you. Before transmission, diagnostic payloads are sanitised to redact file paths, email addresses, tokens, and similar sensitive values.

3.5 Website and API data

When you use magoflow.com, our apps' backends, or our APIs, we process:

• Account data (email and hashed password) if you register;
• Security and audit logs, including your IP address, user-agent (browser/device string), the event (for example registration, login success/failure, token refresh), and timestamps;
• Anti-abuse data used for rate-limiting (a short-lived record keyed to your IP address and the endpoint);
• Session tokens (access and refresh tokens) needed to keep you signed in.

Our website and APIs run on Cloudflare. Cloudflare processes connection data (such as IP addresses) to deliver and protect the service. Our magoflow.com account database is hosted in the European Union. App backends may also use Cloudflare and database providers such as Neon to store the account content described in Section 3.1.

3.6 AI-powered features

Some apps include AI-powered features — for example, Spanbe generates meal plans and recipes. To provide such a feature, we send the inputs the feature needs (for example your dietary preferences, ingredient exclusions, and calorie targets — not your name or email address) to our AI service providers, currently OpenAI, Groq, and Google, which process them on our behalf to generate the content you request. We configure these integrations to use business/API terms that are intended to restrict provider use of customer API content for general model training, but the relevant provider terms and technical configuration govern in practice. Image-search providers (such as Pexels and Pixabay) may receive generic search terms, recipe names, or similar content prompts to find illustrative photos. Please do not type personal data you do not want processed into free-text AI inputs.

4. Screen Time, app-usage, and accessibility data (Amity)

On iOS, Apple's Screen Time framework is designed so that your usage data is not made available to us. On Android, app-open events are evaluated on the device in the moment and are not logged to a server. Your selection of apps to limit on iOS is stored as an opaque token that cannot be read by us.

5. Device permissions we may request

Each app requests only the permissions its features need. Amity may request:

You can change or revoke these permissions at any time in your device settings; some features may then stop working.

Notifications are optional. You can complete onboarding and use Amity's core blocking, website-filtering, purchase, restore, subscription, and complimentary-access features without granting notification permission. If you decline, Amity will not repeatedly force you to enable notifications. You can enable them later in your device settings, manage supported reminders in Amity's settings, and turn reminder scheduling off without disabling blocking.

Some platforms may still show system-generated indicators for an enabled feature, such as a foreground-service notification on Android. Those platform indicators are separate from optional reminders, and a Firebase messaging token is processed only where notification functionality is enabled and the platform provides one.

Other apps request permissions in context — for example, notifications for reminders or, where a specific feature you choose to use needs it, the microphone, camera, or motion & fitness data. The app explains the purpose at the point of request, and we do not access these sensors in the background.

6. Health, financial, and other sensitive data

We treat the following categories of data with extra care. We do not sell them, we do not use them for third-party advertising, and we do not use them to build unrelated marketing profiles. Depending on the feature, we use them to provide the feature you requested, keep the service secure, answer support requests, maintain legally required records, and otherwise as described in this policy:

• Wellness and nutrition data (Spanbe). Dietary preferences, ingredient exclusions and allergies, calorie and weight goals, and activity level are used only to generate and manage your meal plans and related features. Depending on your region and the specific processing, the legal basis may be contract, explicit consent collected separately at the point of use, or another lawful basis described in Section 8. We do not intend passive data entry by itself to stand in for any separate explicit consent the law requires. If you withdraw a consent that a cloud feature depends on, we may stop that feature, delete or de-identify existing synced wellness records tied to it, or make them unavailable except where we must retain them for legal, security, or accounting reasons.
• Wellbeing data (Amity). Your goals, commitments, and blocking configuration are stored on your device, as described in Sections 3.2 and 4. Some setting values from them — such as a daily limit’s length or your Sleep Time hours — are included in the analytics described in Section 3.4, never the identity of a blocked app or website.
• Documents and financial information. Where an app offers analysis of documents or statements you import and describes that feature as on-device, the content is processed locally on your device and is not uploaded to us; any insights shown are produced on the device. If a future feature ever required server-side processing of such content, the app would say so clearly and ask for your consent first.
• Voice and audio. If a feature uses your microphone (for example speech practice), the app will tell you at the point of use what is captured and where it is processed. We do not record audio in the background.
• Special-category data we do not ask for. Please do not send us data revealing racial or ethnic origin, political opinions, religious beliefs, genetic or biometric data, or details of diagnoses or medical treatment through ordinary support channels or free-text fields unless we explicitly ask for it in a protected workflow designed for that purpose.

7. How we use personal data

• to provide, operate, and secure our apps, website, and APIs;
• to create and manage your account and keep you signed in;
• to generate the content and features you request (including AI-powered features);
• to enable and manage subscriptions, store-managed introductory trials, billing status, and restores;
• to send notifications and reminders you have requested;
• to diagnose crashes, fix bugs, monitor stability, and improve features;
• to prevent, detect, and investigate fraud, abuse, and security incidents (including rate-limiting);
• to respond to your support, rights, deletion, refund, and complaint requests;
• to keep records showing what consents, withdrawals, notices, and rights requests were given or handled; and
• to comply with legal obligations and enforce our terms.

8. Legal bases for processing (GDPR / UK GDPR)

Where we rely on legitimate interests, we have balanced them against your rights and freedoms. You may object to such processing (see "Your rights").

9. Recipients, service providers, and platform partners

We do not sell your data. We disclose limited personal data only to service providers and platform partners who help us run our apps and website, process purchases, generate content you request, provide sign-in and infrastructure, deliver support, or comply with law. Depending on the service and the context, a provider may act as our processor/service provider, an independent controller, or both for different steps. The table below is a summary rather than a full contract matrix.

Where a provider processes personal data for its own purposes, its own privacy notice and terms also apply to that processing. We may also disclose data to professional advisers, auditors, insurers, or authorities where reasonably necessary to establish, defend, or comply with legal rights and obligations.

We may also disclose data where required by law, to protect our rights or users' safety, or in connection with a merger, acquisition, or sale of assets (in which case we will notify you and this policy will continue to apply, or you will be told of any change).

10. We do not sell or "share" your personal data

We do not sell your personal data, and we do not "share" it for cross-context behavioural advertising, as those terms are defined under the California Consumer Privacy Act (CCPA/CPRA) and similar US state laws. We have not sold or shared personal data in the preceding 12 months, including data of consumers under 16.

11. International data transfers

Our magoflow.com account database is hosted in the European Union. Some of our providers (such as Google/Firebase, RevenueCat, Apple, Cloudflare, Neon, and our AI providers OpenAI and Groq) are based in or process data in the United States and other countries. Depending on the provider, service, and country involved, international transfers may rely on the European Commission's Standard Contractual Clauses, the UK International Data Transfer Addendum, an adequacy decision, a provider's Data Privacy Framework participation where applicable, or another lawful transfer mechanism then in force. The mechanism can vary by provider and may change over time.

You can contact us at [email protected] to request a summary of the safeguards we currently rely on for the transfer relevant to your data.

12. How long we keep data

• On-device data remains until you delete it, reset the app, or uninstall it. You control it.
• Account data and app content (for example saved meal plans, preferences, and synced records) are kept while your account is active and then deleted, anonymised, or de-identified after a verified deletion request, subject to any legal hold or required retention described below.
• Security/audit logs (including IP address and user-agent) are generally kept for up to 12 months and then deleted or anonymised unless we need longer retention for an active security matter, dispute, or legal obligation. Rate-limit records are usually pruned within minutes or hours.
• Diagnostics and analytics are retained for the period configured in the relevant service or provider. For Firebase, that may mean aggregate analytics for up to about 14 months; crash data and raw troubleshooting records are usually kept for a shorter operational period.
• Support emails and attachments are usually kept until the request is resolved and then for up to 24 months to manage follow-up, establish a record of what happened, and defend legal claims, unless a longer period is required by law or a dispute.
• Consent, withdrawal, and rights-request records are kept for as long as needed to show what choice was made, when it was made, and how we responded, and may be retained for the limitation period applicable to the related claim or compliance duty.
• Purchase, entitlement, tax, and accounting records may be retained by Apple, Google, RevenueCat, and us for the statutory retention period that applies to the relevant purchase channel and trader.
• Backups are overwritten on a rolling basis and may continue to contain isolated copies for a limited period after deletion until the relevant backup cycle expires, unless a legal hold requires otherwise.

13. Security

We use technical and organisational measures to protect personal data, including transport encryption (HTTPS/TLS) for all network traffic, industry-standard password hashing (PBKDF2-SHA256 for magoflow.com accounts; app accounts use the hashing built into our authentication providers), on-device storage, parameterised database queries, rate-limiting, and least-privilege access. No method of transmission or storage is completely secure, but we work to protect your information and to respond appropriately to any incident, including notifying you and regulators where the law requires.

14. Your privacy rights

Depending on where you live, you may have some or all of the following rights:

• Access — a copy of the personal data we hold about you;
• Rectification — correct inaccurate or incomplete data;
• Erasure — delete your data ("right to be forgotten");
• Restriction — limit how we process your data;
• Portability — receive your data in a portable format;
• Objection — object to processing based on legitimate interests;
• Withdraw consent — at any time, where we rely on consent; and
• Appeal or complain — challenge certain decisions where the law gives you that right, or lodge a complaint with a supervisory authority (see below).

To exercise any right, email [email protected] or use the Data & Account Deletion page. We may ask for information reasonably needed to verify your identity, authority, and the scope of your request, but we try not to ask for more than is necessary. We respond within the time the law requires (generally one month under the GDPR/UK GDPR, or 45 days under many US state laws, extendable where permitted), explain material refusals where required, and do not discriminate against you for exercising your rights. You may use an authorised agent where the law allows.

15. United States — state privacy rights

If you are a resident of California, Virginia, Colorado, Connecticut, Utah, Texas, Oregon, Montana, or another US state with a comprehensive privacy law, you may have rights to know/access, delete, correct, and obtain a portable copy of your personal information, and to opt out of the sale of personal information, "sharing" for cross-context behavioural advertising, and certain profiling. We do not sell or share personal information and do not use it for targeted advertising, so there is currently no sale, sharing, or targeted-advertising processing for a browser opt-out preference signal to stop. You may still exercise your other rights via [email protected]. California residents may also request information under California's "Shine the Light" law. We will not discriminate against you for exercising any right.

15.1 Categories of personal information (California notice at collection)

In the past 12 months we have collected the following categories of personal information, from you and your device, for the business purposes described in Sections 7–8, and disclosed them only to the service providers in Section 9 (never sold or "shared"):

15.2 Sensitive personal information

We do not collect sensitive personal information for the purpose of inferring characteristics about you. Where an app collects wellness or nutrition preferences that may be considered sensitive (see Section 6), we use them only to provide the service you request — a purpose permitted by the CPRA — and never for advertising or profiling, so the "right to limit" is not triggered. We do not knowingly process such data beyond providing the service you requested.

15.3 Consumer health data (Washington, Nevada, and similar laws)

Where laws such as Washington's My Health My Data Act, Nevada's consumer health data law, or similar laws apply, some of the wellness and nutrition information described in Section 6 may qualify as "consumer health data". Our standalone Consumer Health Data Privacy Policy provides the additional categories, sources, purposes, sharing disclosures, rights, consent, withdrawal, and appeal information relevant to that data.

16. Children's privacy

Our Services are not directed to children under 13. If an app, feature, or store listing states a higher minimum age, that higher age controls. Some Services or features, especially those involving nutrition, wellbeing, or purchases, may be intended for adults or for teens using the Service with a parent or guardian where local law allows. We do not knowingly collect personal data from anyone below the minimum age applicable to the relevant Service in their country. If you believe someone below that age has provided us personal data, contact [email protected] and we will review and delete it where required.

17. Cookies and similar technologies

Our website uses only strictly necessary storage (such as a sign-in session token and your light/dark theme preference) and security cookies set by Cloudflare. We do not use advertising or third-party tracking cookies on the website. For details and how to control them, see our Cookie Policy.

18. Automated decision-making and AI

We do not make decisions producing legal or similarly significant effects about you based solely on automated processing, and we do not profile you for advertising. AI-generated content (such as a suggested meal plan) is informational, is produced only at your request, and you remain free to accept, edit, or ignore it.

19. Other countries and regions

We try to honour the privacy rights described in Section 14 for all users, wherever you live, subject to local law. Residents of Brazil, Canada, Australia, New Zealand, Japan, South Korea, Singapore, Switzerland, Türkiye, India, and other markets may have additional local rights or complaint routes. Use the contact details below and we will route the request under the law that applies to the relevant Service, market, and processing activity. Where local law requires a separate addendum, representative, or market-specific notice, we may publish it for the relevant Service or region instead of trying to compress every local rule into this one umbrella policy.

Without limiting the above, users in the following regions may in particular have local rights and regulator routes:

• Brazil (LGPD). You have rights of confirmation, access, correction, anonymisation, deletion, portability, and information about sharing, and you may complain to the ANPD.
• Canada (PIPEDA and Québec Law 25). You may access and correct your personal information and withdraw consent. Our person in charge of personal-information protection is reachable at [email protected]; you may complain to the Office of the Privacy Commissioner of Canada or the Commission d'accès à l'information du Québec.
• Australia and New Zealand. You may request access and correction under the Australian Privacy Principles or the NZ Privacy Act and complain to the OAIC or the Office of the Privacy Commissioner (NZ).
• Japan (APPI), South Korea (PIPA), Taiwan, Hong Kong (PDPO), and Singapore (PDPA). You may request disclosure, correction, suspension of use, or deletion of your personal data as provided by local law.
• Switzerland (FADP). The rights and safeguards described for the EEA apply equivalently; the competent authority is the FDPIC.
• Türkiye (KVKK). You may exercise the rights in Article 11 of the KVKK through the contact below.
• India (DPDP Act). You may access, correct, and erase your data and nominate another person to exercise your rights; our grievance contact is [email protected].

If the law of your country gives you additional rights, you can exercise them through the same contact. Where a right depends on residency or other conditions, we may ask for the information needed to verify it.

20. Changes to this policy

We may update this policy from time to time. Changes take effect on the effective date shown above. When we make a material change, we will update the "Last updated" date and, where required or appropriate, provide prominent notice in the app, on the website, or by email before or when the change takes effect. We do not rely on continued use by itself as consent to materially new consent-based processing; if a new consent is legally required, we will ask for it separately before carrying out that processing.

21. Contact, representatives & complaints

Data controller: Magoflow, the trading name of IT SERVICES MAREK PIETKIEWICZ — [email protected].

Legal entity and address: IT SERVICES MAREK PIETKIEWICZ, NIP 5542598947 / REGON 341623872, ul. Irysowa 16, 86-031 Osielsko, Poland. General support: [email protected]. Legal notices: [email protected].

If we appoint a UK or other local privacy representative for a specific Service, region, or processing activity, we will publish the current details in the relevant notice or market-specific addendum. We have not designated this page itself as the appointment notice for any such representative.

We have not appointed a Data Protection Officer for the Services described here. Privacy questions and complaints should be sent to [email protected].

Complaints. If you are in the EEA or UK and believe we have not handled your data properly, you can complain to your local data protection authority (in Poland, the President of the Personal Data Protection Office, uodo.gov.pl; in the UK, the Information Commissioner's Office, ico.org.uk). We would appreciate the chance to address your concerns first.