Privacy Policy
Effective Date: September 7, 2026 · Last Updated: October 4, 2026
What does all this mean?
Here is the short version. Read the full details below.
No Selling, No Tracking Prompt
We never sell your data or share it with data brokers. We measure our own Meta ads with the Meta SDK, and on iPhone we never ask for tracking permission.
Encrypted and Secure
Encrypted in transit and at rest. Passwords are hashed, never stored in plain text.
Delete Anytime
Delete your account from Settings > Account. Everything is gone 30 days later.
01Introduction
Rizanah (“we,” “us,” or “our”) operates the Rizanah mobile app for iOS and Android and the website at rizanah.com, including the pages that open when a member shares a post, recipe, challenge, or profile link (together, the “Service”). This Privacy Policy explains exactly what personal information we collect, why, who receives it, and the choices you have.
Rizanah LLC is based in Columbus, Ohio, United States.
By using the Service, you agree to the collection and use of information as described in this policy. If you do not agree, please do not use the Service.
02Information We Collect
2.1 Information You Provide Directly
We collect the following personal information when you create an account and use the Service:
| Data Category | Specific Data | Why We Collect It |
|---|---|---|
| Account | Name, email address, password (or a Google or Apple sign-in), username, profile photo, public bio, app language, time zone | Create and sign you in to your account, show who you are in the community, send emails in your language, and count your daily activity in your own day. |
| Body Metrics | Height, weight, date of birth, gender | Calculate calorie and macro targets, build workout plans, and place you in the sisters' or brothers' community. |
| Fitness Profile | Goals, experience level, schedule, equipment, health conditions, injuries, pregnancy status, workout preferences | Build and adjust a workout plan that is safe for you. Health conditions, injuries, and pregnancy status are optional; leaving them blank only limits how much we can adapt the plan. |
| Workout Logs | Exercises, sets, reps, weights, effort ratings, duration, completion, cardio activity type, distance, pace, time, and the GPS route of outdoor cardio sessions | Track progress, adjust future workouts, credit challenges, Ummah Journeys, and Seeds rewards, and draw your own routes in City Glow. |
| Nutrition | Foods, barcodes you scan, calories, macros, meal slots, water, saved meals, recipes and recipe photos, kitchen and grocery lists, fasting settings | Track daily intake against your targets, plan meals, and show fasting status on the right days. |
| Community | Posts and post photos, comments, intentions (niyyah), polls, follows, bookmarks, challenge and journey participation, team membership, reports and blocks | Run the community within your gender community, run challenges and Ummah Journeys, and act on reports. |
| Health App Data | With your permission only: daily steps, weigh-ins and water logged read from Apple Health or Health Connect, and the workouts and weigh-ins you log written back to them | Show your movement without double entry. Each direction has its own switch in Settings > Health sync, and you can revoke access in the Health app or Health Connect. |
| Payment | Processed by Apple, Google, or Stripe. We never see or store card numbers. | Process subscription payments. In-app purchases are handled by Apple and Google through RevenueCat; older web subscriptions by Stripe. |
| Support | Email address, message, the screen you wrote from, your device and app version, and any screenshot you attach | Respond to questions, bugs, and feature requests. |
2.2 Information Collected Automatically
When you use the Service, we automatically collect:
- Device information: device model, operating system version, app version, and app language, attached to analytics events and crash reports.
- IP address: seen by our servers and hosting provider each time the app or website connects. Used for security, rate limiting, and abuse prevention. We do not build a location history from it.
- Product analytics (PostHog): which screens you open, which features you use, session length, and app errors, tied to your account ID and to a few profile facts: gender, current plan ID, subscription status, whether onboarding is complete, and sign-up date. No workout, food, body, or health values are ever sent as analytics.
- Ad measurement (Meta): when you install the app and when you open it, the Meta SDK sends Meta a standard event with the SDK's own anonymous id, your device model, operating system, and app version. We use it only to see which of our Meta ads led to installs and to stop paying for the ones that did not. Nothing you do inside the app, including creating an account or subscribing, is reported to Meta. On iPhone we never ask for tracking permission, so Apple's advertising identifier is never read and Meta attributes installs through Apple's privacy-preserving system. On Android the SDK also sends the Google advertising ID; turn that off in Settings > Legal > Ads measurement, or reset the ID in your phone's settings. No workout, food, body, or health values, and never your email.
- Crash reports (Sentry): the error, the code path, your account ID for grouping, device model, operating system, and app version. Email, name, username, and IP address are stripped before the report leaves your phone.
- Location, in two cases only. Fasting: when you turn on fasting and choose to use your location, the app reads your position once, on your device, to estimate Suhoor and Iftar times and name your city. Your phone's own geocoding service converts the coordinates to a city name; the coordinates are not sent to our servers. Outdoor cardio: while you record an outdoor session, the app reads GPS continuously, including in the background if you switch apps, to measure distance and pace. The route is saved with that workout so you can see it in your history and in City Glow. Location is never read at any other time.
- Push notification token: if you allow notifications, Expo's push service issues a token for your device, which we store so we can send reminders and community notifications. Turn them off in Settings > Notifications or in your phone's settings; the token is deleted with your account.
- Cookies on rizanah.com: see Section 5.
2.3 Information from Third-Party Services
If you sign up or sign in with Google or Apple, we receive your name and email address from that service. We never receive your password from them. If you connect Apple Health or Health Connect, we read only the categories you approve, as described in Section 2.1.
We do not purchase personal information from data brokers or any other third party.
03How We Use Your Information
We use your personal information for the following purposes:
- To provide the Service: build and adjust your workout plan, calculate nutrition targets, run the community, challenges, and Ummah Journeys, and track your progress.
- To process payments: keep your Premium status in sync with Apple, Google, and Stripe.
- To communicate with you: send account emails (welcome, password changes, deletion notices, trial and renewal notices, receipts), push notifications you have allowed, and replies to your support requests.
- To translate on request: send the text of a community post, comment, or intention to Microsoft Azure Translator only when you tap Translate.
- To log a meal with Shams (Premium): send the meal description you type, or the meal photo you take, to OpenAI only when you tap Find foods. OpenAI returns the dishes it recognises with an estimated amount, calories and macros for each; the app shows them as estimates, and a food you keep is saved as your own food in your account. We keep a count of your calls to enforce the daily limit, the food you pick when a guess was wrong, and, for each dish Shams named, the name, the estimate and what you did with it (kept, edited, removed or swapped), so Shams improves for everyone. Dishes many members save with similar numbers can become shared catalog entries without any account details. Before sending, Rizanah removes email addresses, phone numbers and links from the text and strips location and camera details from the photo. Rizanah does not keep the text or the photo after the result returns. OpenAI processes them under its API data terms: on every request we ask that the response is not kept as a retrievable record, OpenAI does not use API data to train its models, and it may retain the request for up to 30 days to monitor for abuse before deleting it.
- To improve the Service: analyze usage patterns and crash reports to fix bugs and decide what to build.
- To keep the Service safe: enforce our Terms of Service and Community Guidelines, act on reports, prevent abuse, and protect your account.
We do NOT use your data for:
- Selling or renting to anyone.
- Showing ads inside Rizanah.
- Sharing with data brokers.
- Training AI models.
04How We Share Your Information
We do not sell or rent your personal information. We share data only with the services below, only for the purpose stated:
| Recipient | What We Share | Why |
|---|---|---|
| Apple, Google, RevenueCat | Your account ID, device, and purchase or subscription events | Process in-app purchases and keep your Premium status in sync. |
| Stripe | Email, plan, and payment events for members who subscribed on the website | Process those payments. PCI-DSS compliant. Card numbers never reach us. |
| PostHog | Product analytics events and the profile facts listed in Section 2.2 | First-party product analytics. No health or nutrition values. |
| Meta | Install and app-open events only, with the Meta SDK's anonymous id, device model, operating system, and app version; on Android, the advertising ID unless you turn measurement off | Measure which of our Meta ads lead to installs. No tracking prompt on iPhone, so Apple's advertising identifier is never read. Meta processes these events under its own data terms. |
| Sentry | Crash reports: error, code path, account ID, device model, OS, app version | Find and fix crashes. Email, name, username, and IP address are removed first. |
| Expo push service | Your device push token and the text of each notification we send | Deliver push notifications through Apple and Google. |
| Microsoft Azure Translator | The text of a community post, comment, or intention, only when you tap Translate | Translate community text into your language. Nothing about your account is sent with it. The translation is stored with the post so the next member who taps Translate gets it instantly. |
| OpenAI | The meal description you type or the meal photo you take in Shams, only when you tap Find foods (Premium) | Name the dishes in a meal and estimate amounts, calories and macros, shown in the app as estimates. Rizanah does not keep the text or photo after the result returns. OpenAI processes it under its API data terms: it is asked not to keep the response as a retrievable record, does not use API data to train models, and may retain the request for up to 30 days to monitor for abuse. |
| USDA FoodData Central | The food search text you type | Look up nutrition for foods that are not already in our database. Public U.S. government API. |
| Resend | Email address, first name, app language | Send account and subscription emails. |
| Apple Maps, Google Maps | Map tile requests (your IP address and the map area on screen) when you open City Glow | Draw the map behind your routes. Your current position is not shown or sent. |
| DigitalOcean | Server logs (IP address, user agent) | Host and serve the application. |
| Supabase | All Service data, including uploaded photos (encrypted at rest) | Store account, workout, nutrition, community, and support data. |
| Other members | Username, display name, photo, bio, posts, comments, intentions, challenge and journey progress, team distance, and leaderboard positions | Visible within your gender community only. Teammates see each other's contributed distance. |
| Anyone with a link you share | The post, recipe, or challenge you chose to share, or your profile page (name, username, photo, public bio) | Share pages on rizanah.com open for anyone with the link, including people without the app. Sharing is always your choice. |
| Law enforcement | As required by law | Valid legal process only. We notify you unless prohibited. |
05Cookies and Tracking
rizanah.com sets only the cookie it needs to work. No advertising cookies, no tracking pixels. Visits are counted with PostHog in cookieless mode: nothing is stored in your browser, and unique visitors are counted from a daily-rotating hash that cannot be turned back into you.
| Cookie | Purpose | Duration |
|---|---|---|
| Sign-in session | Keeps you signed in on the rizanah.com pages that need an account, such as account deletion | Until you sign out or the session expires |
Because we set no advertising cookies and do no cross-site tracking, we do not show a cookie banner. The mobile app uses no cookies at all.
06Data Retention
We keep your personal information for as long as your account exists. Free accounts are not deleted for inactivity. Two things trigger deletion:
- You delete your account (see the box below).
- A cancelled Premium subscription. Eleven months after a Premium subscription is cancelled, we email you a 30-day notice. Opening the app or signing in at any point during those 30 days cancels it. If you do neither, the account and all of its data are deleted 30 days after the email, and we email you to confirm.
- Community content stays until you remove it. Posts and comments remain visible after you cancel Premium. Delete any post yourself from its menu, or delete your account.
If you delete your account (Settings > Account > Delete account):
- Your posts and comments are hidden from the community immediately.
- You have 30 days to change your mind: signing in again cancels the deletion.
- After 30 days we permanently delete your account and every record tied to it: profile, workouts and routes, nutrition, community content, journeys and teams, support requests, uploaded photos, notification tokens, and your Stripe customer record. We email you when it is done.
- What remains: an anonymised audit entry (a one-way hash of your account ID, the date, and the list of data categories removed), and the purchase records that Apple, Google, and RevenueCat keep under their own policies.
07Data Security
We protect your data with:
Encryption in transit
TLS 1.2 or newer (HTTPS) for every connection
Encryption at rest
AES-256 on the database and file storage (Supabase)
Password hashing
bcrypt through Supabase Auth; passwords are never stored in plain text
Row Level Security
Database rules that let each member read and write only their own rows
Payment security
Apple, Google, and Stripe handle all card data; Stripe is PCI-DSS Level 1
Admin access
Limited to named staff accounts, each with a role that opens only the screens it needs
No system is completely secure. If we discover a data breach that affects your personal information, we will email you within 72 hours with what was affected and what we are doing about it.
08Your Privacy Rights
8.1 All Users
Wherever you live, you can:
- See your data: everything we hold is visible in the app under Profile, Settings, History, and Nutrition.
- Correct your data: update anything from Profile or Settings.
- Delete your data: Settings > Account > Delete account removes everything after 30 days, as described in Section 6.
- Export your data: email [email protected] and we send you a copy.
- Cancel your subscription: in the App Store or Google Play, or through Stripe if you subscribed on the website. Settings > Subscription shows where yours is billed.
- Withdraw health information: remove injuries and health conditions in Settings > Health, and turn off Apple Health or Health Connect in Settings > Health sync.
8.2 California Residents (CCPA/CPRA)
If you are a California resident, you have additional rights:
- Right to Know: Request the specific data we collected, its sources, purpose, and who we share it with.
- Right to Delete: Request deletion of your personal information, subject to certain exceptions.
- Right to Opt-Out: Rizanah does NOT sell or share your data for advertising. There is nothing to opt out of.
- Right to Non-Discrimination: We will not discriminate against you for exercising your rights.
Do Not Sell or Share My Personal Information
Rizanah does not sell, share, or use personal information for cross-context behavioral advertising. We have never sold personal information and have no plans to do so. There is no need to submit an opt-out request because we do not engage in these practices.
To exercise your rights, email [email protected] with the subject “Privacy Request.” We will verify your identity and respond within 45 days.
8.3 European Residents (GDPR)
If you are in the EEA or UK, you have additional rights under GDPR:
- Legal basis: We process your data based on consent, contractual necessity, and legitimate interests.
- Right to Portability: Request your data in a structured, machine-readable format.
- Right to Restrict Processing: Limit how we use your data while a complaint is being resolved.
- Right to Lodge a Complaint: File a complaint with your local Data Protection Authority.
Rizanah stores data on servers in the United States (Supabase and DigitalOcean). Transfers from the EU/UK to the US are covered by Standard Contractual Clauses (SCCs) in our Data Processing Agreements with Supabase, DigitalOcean, and Stripe. You may request copies by emailing [email protected].
Lawful Basis for Processing
| Data | Legal Basis |
|---|---|
| Account, fitness profile, workout and nutrition logs | Contract (Art. 6(1)(b)): needed to deliver the service you signed up for. |
| Body metrics (height, weight, age) | Contract (Art. 6(1)(b)): needed to calculate your plan and targets. |
| Health data (injuries, conditions, pregnancy status, Apple Health and Health Connect data) | Explicit Consent (Art. 9(2)(a)): you provide it voluntarily and can withdraw it in Settings. |
| Community content | Legitimate Interest (Art. 6(1)(f)): operating the community. |
| Device, usage, and crash data | Legitimate Interest (Art. 6(1)(f)): security and product improvement. |
| Payment | Contract (Art. 6(1)(b)): processing your subscription. |
Withdrawing Consent
You can withdraw consent for health data at any time: remove injuries and conditions in Settings > Health, and turn off Apple Health or Health Connect in Settings > Health sync. Withdrawing consent does not affect processing that happened before. You can also delete your whole account in Settings > Account.
09Age Requirement
Rizanah is for adults. You must be 18 or older to create an account, and sign-up does not accept a date of birth under 18. We do not knowingly collect personal information from anyone under 18. If you believe someone under 18 has an account, email [email protected] and we will delete it.
10Health Data
Rizanah is a consumer wellness app, not a healthcare provider. The fitness and nutrition data you enter is not protected health information (PHI) under HIPAA, and Rizanah is not a HIPAA-covered entity.
We still treat it as sensitive. Data you allow us to read from Apple Health or Health Connect is used only to show your steps, weigh-ins and water inside Rizanah and to calculate your targets. We never use health or fitness data for advertising, never sell it, and never share it except as listed in Section 4. It is deleted with your account, and you can revoke Health access at any time in the Health app, in Health Connect, or in Settings > Health sync.
11Research Participation
If you take part in a Rizanah research study, through Prolific or through a personal invitation link, your study answers are kept separately from your Rizanah account. We do not attach them to your account, and nobody reading the answers can see who you are inside the app.
During a study we store the answers you give, which steps of the study you reached and when, and the study access code you were shown. Your browser holds a cookie containing only a random session number, so you can close the page and come back without losing your place.
If you arrive from Prolific, we store the participant, study and session identifiers that Prolific adds to the study link, so your submission can be matched to your payment. Prolific does not give us your name or your email address.
If you were invited directly and are offered a gift card, we ask for an email address for one purpose: sending the card. It is stored apart from your answers, is never used for marketing, is shared only with Giftogram, which delivers the card, and is deleted once the card has been sent.
Study answers are kept as research records with no name attached. To have your answers removed, email [email protected] with something that identifies your session, such as your Prolific ID or the email address you gave us for a reward.
12Changes to This Policy
We may update this Privacy Policy. If we make material changes, we will email you at least 30 days before they take effect and post the updated policy at rizanah.com/legal/privacy. The “Last Updated” date at the top shows the latest revision.
Your continued use of the Service after the effective date constitutes acceptance of the changes.
13Contact Us
If you have questions about this Privacy Policy or want to exercise your privacy rights:
[email protected]
In-App Support
Settings > Support
We respond to privacy requests within 30 days (45 days for CCPA requests).
Rizanah LLC, 1747 Olentangy River Rd #1067, Columbus, OH 43212