MAAKFIT Privacy Policy

MAAKFIT is a digital fitness and nutrition app operated by Abdelhakim Ait Boukrim, acting as an individual operator and not as a registered company. Public location: MAG 5, Dubai South, Dubai, United Arab Emirates.

Privacy contact: support@maakfit.com using the Privacy category on the Contact page.

We collect what is needed to provide the service: name and account data, email, phone if supplied, age or date-related profile input, gender, goals, training days, training time, measurements, and preferences.

Data you choose to enter may include workout logs, weights, reps, effort, hydration activity, progress and uploaded photos, nutrition preferences, allergies, intolerances, and disliked foods.

We collect membership and billing status, necessary transaction identifiers, device/browser and session data, limited security logs, and necessary cookies or local storage.

Microphone/camera permission is requested only for a feature that uses it.

To operate the account, personalize the experience, assign training and nutrition, track progress, and support billing and account needs.

To operate billing, renewal reminders, security, and fraud prevention.

To improve the product. We do not sell personal data.

MAAKFIT does not store full card numbers or CVV in the app database. A future approved payment provider will process those details.

We may store transaction identifiers, amount, currency, status, plan, and dates needed to manage the subscription.

Progress photos are private by default. Upload is not marketing consent.

We do not automatically use photos in ads, social media, before/after campaigns, or public testimonials.

Any before/after marketing consent is separate, explicit, optional, and not pre-checked. Refusal does not affect the account, program, or subscription.

Progress photos and uploaded files are privately stored and limited to the account holder and authorized staff when needed for support or service operation.

The service may use automated rules and calculations to personalize plans and present analytics and progress.

We do not use progress photos or sensitive data for marketing without separate, explicit consent.

Operational analytics may improve the service and security. We do not expand advertising tracking without a clear basis.

Marketing consent is optional and separate from Terms acceptance, purchase, and service communications.

Refusing marketing does not block a paid plan. You may opt out later.

Security, billing, renewal reminders, material legal changes, and account notices are not marketing.

We do not sell personal data.

We use Supabase for authentication, database, and storage; Vercel to host the application; and Resend for service email. Their roles or replacements may change with an updated policy.

When payments are enabled, limited data may be shared with third-party payment providers under their own terms and privacy notices. Authorized operations and support staff receive only the access needed to provide the service.

We apply reasonable technical and organizational safeguards. We do not claim 100% security.

Passwords are handled by the auth system and are not stored in plaintext.

You may request access, correction, deletion, restriction, objection, or withdrawal of optional consent, subject to applicable law. Sensitive requests may require identity verification.

Delete account ≠ cancel renewal ≠ refund request.

We retain data only as long as reasonably necessary for the purposes described, legal obligations, dispute resolution, fraud prevention, and security. A detailed retention schedule will be reviewed after entity and jurisdiction are finalized.

V1 is 18+. If we learn of a minor account, we will close it under a reasonable process.

Data may be processed by international providers. We do not make false data-residency claims.

This Policy is governed by the laws of the United Arab Emirates as applicable in the Emirate of Dubai. The courts of Dubai, United Arab Emirates have jurisdiction, subject to mandatory rights that cannot be waived. It is available in Arabic and English; Arabic prevails if interpretation differs. Version v1.0. Effective date: October 1, 2026.