CrewDue

Privacy policy

Last updated: 16 October 2026

CrewDue: Staff Expenses (“CrewDue”, “we”, “us”) is an app and website by MadOverTechnology that helps businesses keep track of money given to staff, staff expenses, receipts, approvals and settling each staff balance. This policy explains what we collect, why, who helps us run the service, how long we keep it and what you can do. Questions: hello@madovertech.io.

Who uses CrewDue

A business owner creates a business. Owners and managers join through email invitations and sign in with an email code, Google or Apple. Employees can use a sign-in code shared by their owner or manager; it works once, expires in 10 minutes and signs them into that business only. Each business decides who joins it. Owners and managers can see the records in their business as their role allows; employees see their own records.

What we collect

  • Your contact mobile number, if provided to your business. It is contact information, not a sign-in credential; we do not send SMS codes.
  • Your name, and the name a business uses for you. If you use Google or Apple sign-in, we also keep the provider’s account identifier, linked address and sign-in-method records; we verify identity tokens on our server. Apple authorization tokens needed to revoke access are encrypted.
  • Your email address, for email sign-in codes, security notices and weekly summaries for owners and managers. An address supplied by Google or Apple stays pending until you confirm it with our own email code. Staff who sign in with a code from their owner or manager do not need an email address.
  • Business records: business name, expenses (the purchases and payments people record for the business: amounts and their currency, dates, categories, notes, who was paid), decisions and reasons, money given to staff, returns, payments and settlements, and how the business says it paid (for example cash or bank transfer — we only record the label; we never handle the payment).
  • Receipts: photos or PDF files you attach. Before a photo is stored, we remove its hidden details such as location and camera information.
  • Export filters: when you request an expense export, we save the filters you choose, which may include search terms you typed, with your business and the membership that requested it. We use these filters to prepare the report you asked for.
  • Device information: an id the app creates for your device, the device name and type, and the app version. When phone notifications are set up for your app version and you allow them, we also store a notification token that identifies that app installation for sending alerts.
  • Technical information: IP address and browser or app details with each request, used to keep accounts safe and to limit abuse; a record of important actions (who did what and when), which also stores the IP address, browser or app details and device id of the request.
  • Firebase technical information: app versions configured with Firebase Core and Messaging may also send installation identifiers, notification tokens, IP addresses and technical or diagnostic details to Google. These can include device and operating-system details, app and SDK versions, language and time zone. Google uses service information to operate, maintain and improve Firebase. Some technical processing may occur when Firebase starts, separately from your choice to allow phone alerts.
  • Service diagnostics: Laravel Nightwatch receives technical records about server requests, response times, database-query performance, background tasks and errors so we can monitor availability and investigate problems. Our request-monitoring configuration removes account names, IP addresses, headers, request bodies and uploaded files, and replaces page addresses with route patterns. Internal account identifiers remain in the monitoring records and can link diagnostics to your account. Diagnostic error messages and application logs may still contain information relevant to an error.
  • Product suggestion cards: for owners and managers, when a card about NexaSync was last shown in each place in the app, how many times it has been shown, and whether you chose “Not now” or “Don’t show again” (see “Product suggestions” below).

What we do not collect

We do not ask for your location, contacts or microphone. We do not use third-party advertising tools: no ad networks, no advertising SDKs and no advertising identifiers. We do not add tools to analyse how you browse screens; Firebase and server-monitoring diagnostics are described above. We do not track you across other apps or websites. We do not require card or bank account details to use CrewDue; receipt files and notes can contain payment information you choose to include. This website sets no cookies on its public pages. Signing in on the website sets three cookies: a session cookie, a security cookie that protects forms, and a “remember me” cookie (see “How long we keep it”).

How we use it

To run CrewDue for you and your business; to sign you in and keep your account secure; to show activity updates and tasks in your Inbox; to send phone notifications when they are set up and allowed; to send sign-in codes, account-security notices and weekly summaries to eligible owners and managers who have chosen to receive them; to answer your questions; to decide when to show owners and managers our own NexaSync card (see “Product suggestions” below); and to prevent misuse.

We do not sell your data and we do not share it with advertisers. The only promotion in CrewDue is the NexaSync card described below.

Product suggestions

NexaSync is a separate app by MadOverTechnology for staff attendance, routes and site visits. Owners and managers may see a small card about it in a few places in CrewDue, for example next to an approved expense in a field-work category such as Travel, Fuel or Vehicle. Our servers decide whether to show the card from your role, from what is on the screen (for an expense, its category and its status) and from your earlier choices; employees never see it, and it never appears on a staff member’s balance. To show each card at most once a week, and to respect “Not now” and “Don’t show again”, we record when it was last shown in each place, how many times it has been shown and what you chose, for your account in that business. “Not now” hides the card in that place for 30 days. We use this record, with your role and what is on the screen, to decide when to show you our own promotion for NexaSync; it is not used to track you across other apps or websites. The card’s link opens the NexaSync website and carries no CrewDue data, and nothing about you is shared with NexaSync. Owners and managers can turn every card off in More → Product suggestions in the app, or under Product suggestions in Account & security on the web.

Who helps us run CrewDue

  • Laravel Cloud — hosting the app and its database. The database is Laravel Cloud’s Serverless Postgres, run by Neon. Hosting and file-storage providers may process information outside India.
  • Laravel Object Storage, on Cloudflare R2 — private file storage for receipts and reports, in storage set to private. File-storage location may differ from the app and database region.
  • Laravel Nightwatch — monitoring service availability, server performance and errors.
  • Resend — sending email.
  • Google and Apple — confirming identity when you choose their sign-in methods.
  • Google Firebase Cloud Messaging (and Apple’s push service on iPhones) — processing phone alerts when notifications are set up and allowed. The provider receives the notification token, a generic CrewDue alert and identifiers for the item to open. The notification contains no amounts, notes, decision reasons or receipt contents. The app checks your current access before showing the item you open.

These providers process information under their service and privacy terms. Firebase also processes technical service information as described above; see Google’s Firebase privacy information. Some providers may process data outside India. We may also disclose information when the law requires it.

Who else can see your information

The owners and managers of a business you belong to can see your name, the records you add in that business and your balance, as their role allows. Receipts and reports are only available to people who are allowed to see them at the time they open them, through signed-in pages — never through public links.

How long we keep it

Where a line below says “kept”, we keep those records ourselves and they do not expire automatically in the current version.

  • Your account details: until you delete your account.
  • Business records (expenses, receipts attached to expenses, balances, settlements, invitations and the history of changes): kept, including when a business closes. Money records are never silently edited: a correction is added as an adjustment or a reversal.
  • Records of important actions, including sign-ins and their IP address, browser or app details and device id: kept. Account deletion removes identifying details from the account and membership changes described below; earlier actions and request metadata remain.
  • Weekly summary emails: a copy of each summary sent to owners and managers (which contains business totals rather than individual staff records) is kept with the business’s email records. Turning summaries off stops future summaries; it does not remove earlier copies.
  • Receipts that were never attached to an expense: scheduled for cleanup after 7 days. Stalled uploads are scheduled for cleanup after 1 hour. Files may be removed later if a cleanup needs to be retried.
  • Reports you download: they can be downloaded for 24 hours after they are ready. After that they can’t be downloaded, and the file is removed from storage later, by our scheduled cleanup. The export record, including saved filters and any typed search terms, is kept beyond file expiry.
  • Sign-in code records: scheduled for cleanup 24 hours after the code expires. We never store codes in readable form.
  • Signed-in devices: until you sign out or remove the device. App sign-ins using personal credentials and unused for more than 90 days are removed by scheduled cleanup. Staff code sessions remain until the person logs out or an owner or manager signs the device out; staff website sessions expire after 30 idle days. Disabled phone-notification targets are scheduled for cleanup after 30 days. A website sign-in’s “remember me” cookie lasts up to about 400 days unless you sign out or remove the sign-in.
  • Logs kept by our hosting platform (separate from the records of important actions and the email records above): on our hosting plan, the platform keeps them for 7 days, or for less time if the plan’s log storage allowance runs out first. These logs may contain the IP address, the page address (path) and the host name of a request. These hosting logs are separate from the monitoring diagnostics described below.
  • Server-monitoring diagnostics: Nightwatch applies its monitoring-service retention separately from our business records and hosting logs. Deleting an account does not erase previously collected diagnostic records.
  • Product suggestion choices and the record of when cards were shown: until you delete your account.
  • Backups of the database: our hosting provider keeps the database recoverable to an earlier point in time for the recovery window set in our hosting configuration (the provider allows a window of up to 30 days). Deleting your account does not change backups that already exist; they follow that recovery window.
  • Firebase installation and technical records: Google applies its own service retention. Deleting a CrewDue account or its notification token does not automatically delete the separate Firebase installation identifier or all service diagnostics. See Google’s Firebase privacy information linked above.
  • Support emails: messages sent to our support address are handled through our email service and are not removed by the app’s account-deletion flow. CrewDue does not apply an automatic expiry to these emails.

Your choices

  • You can see and remove signed-in devices in More → Account & security → Signed-in devices in the app, or in Account & security on the web.
  • Owners and managers can manage weekly summaries in More → Notification settings in the app or Settings → Notification settings on the web. Eligible owners receive them by default; managers can opt in. Each owner or manager needs a confirmed email that can receive messages. Summaries cover the previous week, with aggregate activity, current pending work and balance totals. Routine updates use Inbox and push notifications.
  • On a product suggestion card you can choose “Not now” or “Don’t show again”, or turn all cards off in the Product suggestions setting described above.
  • Open More → Notification settings in the app to check phone notification setup and permission. Allow or turn off notifications in your phone’s settings. Your Inbox remains available when phone notifications are off or not set up.
  • You can delete your account at any time (see “Deleting your account”).
  • For questions about information that remains in business records, provider records or support correspondence, or to request access or deletion, email hello@madovertech.io. We may need to confirm who you are. We assess these requests separately from the self-service account-deletion flow.

Deleting your account

Open More → Account & security → Delete account in the app, or sign in on the web at https://crewdue.laravel.cloud/account/delete. We remove your name, contact number and email from your account in the live system at once, remove the name and contact phone each business used for you (including businesses you had already left), remove your name and email from the records of important actions about your account, delete your notification tokens and product suggestion choices, and sign you out everywhere. Reports you asked for can no longer be downloaded from that moment; their files are removed from storage later, by our scheduled cleanup. Copies already in database backups are not changed by the deletion; they follow the database’s configured recovery window. Business records you were part of stay with the business, shown as “Deleted account”; the business also keeps its record of the email invitation or staff sign-in code it issued. Records of important actions made before the deletion keep what happened and when, but no longer show your name, email or contact phone. Weekly summary emails already sent to owners and managers, and the business’s stored copies of them, retain their business totals; they do not contain individual staff records. If you are the only owner of a business that still has other members, make another member an owner first (or archive the other members). Details: https://crewdue.laravel.cloud/delete-account.

Security

The public service uses HTTPS to protect information in transit between your phone or browser and our servers. On your phone, the app keeps the records it saves in an encrypted database file; the key for that file is kept in your phone’s secure storage (the Keychain on iPhone, the Keystore on Android). Your sign-in on the phone is also kept in that secure storage. Receipts and reports use private storage and every view is checked against the viewer’s current access. No method of storing or sending data is completely secure, but we work to protect it.

Children

CrewDue is a tool for businesses and their staff. Accounts are for people aged 18 or older, and it is not meant for children.

Changes

If we change this policy, we will update this page and its last-updated date. Check this page for the current explanation of how CrewDue handles information.

Contact and complaints

Privacy questions and grievances: hello@madovertech.io