Privacy Policy
Last updated: 17 Nov 2026 • Published: 22 Aug 2026 • Effective: 22 Aug 2026
MessMax (“we”, “us”, “our”) is a mess management platform that operates at messmax.net and related services (web app, Android/iOS app). This Privacy Policy describes how we collect, use, share, transfer, retain, and safeguard your personal data when you use our services. By creating an account or using any part of MessMax, you consent to the practices described here.
Scope
Covers all data collected via messmax.net, our backend API (messmax.net/api/*), and the MessMax mobile app (Android/iOS, package com.messmax.net.app). It does not cover pages or ads hosted on third-party sites you reach by following links inside our app/site.
Data controller & contact
Controller: MessMax (Bangladesh). Data queries and requests: Contact page or email [email protected]. We aim to respond within 7 business days.
1. Information we collect
a) Account & profile
Name, email address, password (bcrypt hashed — never stored in plain text), optional avatar image, and chosen account type (hostel owner / individual). When you sign in with Google, we store the verified email and display name returned by Google and the hashed internal ID — never your Google password.
b) Mess content you create or join
Mess names/slugs, member lists (display name, email, role), monthly sheets (meals per day per member, bazar expenses per day, guest meals, deposits, extras), bazar duty schedules, and seat ads (location string, phone/WhatsApp contacts you publish, amenity list, pricing). This is the core dataset you own; we host it for you.
c) Automatically collected
Device/app version, X-API-Key header value, sanitized FCM tokens, app activity logs, IP-derived approximate geo (city/district), and aggregate metrics (page views, API calls). Firebase Cloud Messaging (FCM) is used to deliver push notifications; Google may process token/device data on our behalf per Google’s Privacy Policy.
d) Cookies & local storage
Session cookie: one first-party httpOnly cookie for login (laravel_session). CSRF token cookie. Language preference (lang). LocalStorage (mobile): auth tokens and push tokens via flutter_secure_storage — no third-party tracking cookies are set by MessMax.
e) Data you choose to make public
When you publish a seat ad, fields such as seats_available, rent_per_seat, area/city, amenities, description, and contact phone/WhatsApp become visible to anyone browsing /ads or calling /api/home. Use “Hide exact address” in the ad form to suppress street-level location from visitors.
2. How we use your data
- Operate, personalize, and troubleshoot the mess management service.
- Authenticate you, enforce roles (owner/manager/member), calculate meal rates
Rate = SUM(Bazar)/SUM(Meals)and per-member bills. - Send transactional email (invite, OTP, bazar/announcement, request decisions) via the SMTP host an admin configures — or
logdriver in development. - Deliver push notifications via FCM for meal/bazar/invite/manager events and marketing broadcasts opted into.
- Provide public translation and ad listings to unauthenticated clients (home/seat feed).
- Enforce rate limits and the X-API-Key client gate to block scraping/abuse, detect fraud, and secure the platform.
3. Legal basis (GDPR)
Where GDPR applies: Contract performance (providing your chosen mess service), legitimate interest (security, analytics, product improvement), consent (marketing push/showcasing an ad publicly), and legal obligation (compliance, fraud prevention). You may withdraw consent at any time (e.g., delete an ad, uninstall/disable push) without affecting prior lawful processing.
4. With whom and where we share data
- Within your mess only: meals, deposits, and bazar details are visible to members of that mess. Nothing outside the mess sees that private sheet.
- Public feed: published seat ads and their subset of metadata (above) are globally readable.
- Subprocessors: our hosting provider (Heroku, eu region) stores and serves the database/filesystem; Google (Firebase FCM & Google Sign-In — 1069180546995-u7cik408g6uj08rctf798be1133n5fib.apps.googleusercontent.com); the SMTP provider selected in
/hq-secure-k7p/smtpsends emails; Cloudflare passes encrypted traffic. Each provider processes data per its own published policy. - Transfers: data may transit outside your locality (e.g., EU host). We rely on the provider’s Standard Contractual Clauses and compatible safeguards for such transfers.
- Never: we do not sell your data, run data-broker syncs, or serve third-party ad trackers inside our product.
5. Retention
We keep your data while your account/mess exists and for 90 days after deletion to handle disputes/restores, then purge or anonymize. Logs are rotated within 90 days. Marketing push records are retained per broadcast until deleted in /hq-secure-k7p/notifications. OTP codes (password_reset_otps) expire 10 minutes after generation and are deleted on reuse/reset.
6. Children
MessMax is not directed to children under 13. We knowingly collect no data from them. If you believe a minor provided data, contact us and we will remove it promptly.
7. Security
Deployed over HTTPS (forceScheme). Passwords are bcrypt-hashed; audit tokens are hashed. Public APIs require X-API-Key (key mm_sec_live_···) plus scoped rate limits (api-public / api-auth / api-bulk and web 60s OTP cooldown). File uploads are bound by mime/size checks; database activity is revokable per-role.
8. Your rights & controls
- Access / export: request a copy of your account & member data via Contact.
- Correction / deletion: edit your profile or delete your account in
Dashboard → My Accountor ask an admin in/hq-secure-k7p/users— deletions cascade to linked member entries per our sync. - Objection / restriction: disable push, archive a seat ad, or set a mess to inactive.
- Withdraw consent: clear consent-gated data (e.g., a public ad).
9. International users
Our infrastructure and our notarized data transfers may locate your data outside your country (e.g., Dhaka user data may be stored on an EU host or delivered via a global CDN). By using MessMax, you consent to such transfer subject to this policy and applicable law.
10. Changes to this policy
We may update this page when features or laws change. Continued use after a posted update means you accept the revised policy. Material changes will be noted here with a new “Last updated” date.
11. Grievance / questions
Questions about data handling? Visit Contact — we write back.