Privacy notice
Effective date: November 8, 2026.
Jay’s Platform is a private internal workspace operated by MASTROIANNI FAMILY ENTERPRISES LTD, operating as Jay’s Catering, for approved staff to manage company operations, scheduling, employee requests, accounting and payroll work.
Information used
Depending on the part of the app and the person’s assigned access, information may include business sign-in identity; customer, event and supplier details; sales and tax records; employee identity, employment status, hours and pay-related amounts; supporting benefit evidence where included in a review; company bank and card balances and transactions; and supporting documents, notes, calculations and review history.
Information comes from authorized company connections, source snapshots and records entered or supplied by approved users. The app uses a session cookie to keep an approved user signed in. It does not publish private workpapers on these public information pages.
Jay’s Team employee sign-in
Your cell number identifies your employee account. A security code is texted only to a number already approved for a Jay’s Team account, including the number the company already uses for your schedule texts, and verifies sign-in. The company and Twilio process those details and verification records to provide and protect access. The company keeps a record of the notice version, time of your code request and the approved mobile connected to it.
Payroll may release a saved supplemental-pay PDF to your Jay’s Team account. Only your own report is available through your employee sign-in; the link is not public. Released versions and Payroll’s release or withdrawal history are retained. Jay’s Team uses an employee sign-in cookie. Security-code consent is separate from schedule-text consent. For help, contact AJ at armand@jayscatering.com. Requests to correct or remove information remain subject to the company’s operational and recordkeeping needs.
Connected sign-in and phone unlock
When enabled for your app version, Apple, Google, Microsoft or Facebook can be connected as optional ways to sign in. You first verify an existing approved employee account with a text code. We use the provider’s account identifier, stored as a hash, to connect it to that employee account. Connecting or using a provider does not create an employee account or change your permissions. Your sign-in credentials are entered with the provider.
You can disconnect a connected account in Me and continue to use your cell number and text code. Disconnecting disables that connection and invalidates sessions signed in through it. Facebook deauthorization or a Facebook data-deletion request removes its active employee mapping and invalidates Facebook sign-in sessions. This does not erase company employment records, review or audit history, or existing backups; the recordkeeping and request provisions below continue to apply.
On compatible phones, you can choose optional Face ID, Touch ID or supported strong Android biometrics. Your phone’s operating system performs each biometric check. Jay’s does not receive or store face or fingerprint images or templates. The phone-unlock setting and its employee-account binding use secure storage on that device. Phone unlock protects an existing app session; it cannot create or renew an employee session or bypass sign-out or revoked access. If you cannot unlock, you can choose phone-code sign-in, which first signs out the previous session.
Jay’s Team mobile app and notifications
Jay’s Team connects approved staff to their own employee workspace. Published shifts and assignments, team messages, announcement read and acknowledgment state, requests and decisions, optional Feedback, and released Tip & Bonus reports are available according to the employee’s access and company settings. The company provisions employee accounts; requesting a sign-in code verifies an existing approved account rather than creating a public account.
The mobile app uses Expo and Apple Push Notification service on iPhone, and Expo and Firebase Cloud Messaging on Android. These services process app and installation identifiers and notification tokens to register the app and deliver enabled notifications. The company stores the Expo token, platform, registration time and its employee-account association. Delivery can include a title, message and navigation information.
On Android, Firebase Cloud Messaging can register the app installation before notification-display permission is granted. Notification software can retain registration information and update tokens. Signing out does not erase all provider or software records. Employees can manage notification-display permission in their device settings. Installing the app does not authorize unrelated marketing texts or change separate security-code and schedule-text consent.
Team chat, reports and calendar exports
Messages and replies are shared with the approved members of their chat group. The company retains authorship, message edits and removal history, audience and read or acknowledgment state for work communication and moderation. Abuse reports identify the reporting account and include the selected message or person, its group context, the report reason and any note the reporter chooses to add. They are reviewed through the private company Feedback inbox, not posted in the group. Blocking preferences and the version and time of a chat-conduct acknowledgment are retained with the account.
Opening a private PDF in the native app creates a temporary cached copy. The app attempts removal after preview or sharing activity, when the account changes, and using a 15-minute timer while the app can run. This does not erase copies saved or shared to another app. The operating system can delay cleanup while the app is suspended or closed.
Directions and calendar connections send selected work information to the service the employee chooses. Calendar disconnection stops access through the old feed; it does not erase previously imported events. A private calendar link lets its holder read the released schedule information, so it should not be shared with other people. Work destinations are company assignments; these features do not read the phone’s GPS, address book or personal calendar.
The optional reviewer demo uses invented records. Its device checks can open or share fixed sample files and show a device-local sample notification after a tap. Those checks do not connect a device to an employee account or send messages to staff. Choosing to save or share an exported file is a separate action controlled by the person using the phone and the chosen app or service.
Feedback
If you choose to send Feedback, we collect your message and its problem or suggestion category, your name and work-account identity, any email already held on the account, and the relevant app page or section. Feedback is optional and linked to you. Automatic page context excludes URL queries, fragments and individual record IDs.
We keep the submission time, review status, and the time and reviewer of status changes to review issues and improvements through the private owner inbox. Feedback is stored with the app’s private records and is not posted to other staff. The hosting and storage providers described below process these records.
Marking Feedback resolved changes its status; it does not delete the report. The recordkeeping and correction or removal request information below also applies to Feedback.
How information is used
The app organizes source information, prepares calculations and workpapers, helps reconcile records, and records review decisions and their supporting evidence. It keeps source dates and unresolved items so a saved snapshot can be distinguished from a current source-system record.
Authorized connections include Caterease, ADP, Toast, Intuit QuickBooks, and company bank and card activity supplied through Plaid. Other supporting business documents and imports may contain information from the company’s payment processors, suppliers or existing company files. Only the information needed for an enabled workflow is used in that workflow.
The dedicated QuickBooks integration uses Intuit authorization. Its application requests read company and selected supplier, bill, credit, payment, account and financial-report information for Serra and Hangar rent and prepaid workpapers, and company, account and journal information for payroll posting checks. AJ, Michele and Wayne may explicitly confirm creation of reviewed monthly payroll journal entries. Posting attempts and verified native journal receipts are retained to prevent repeat posting. The app does not edit or delete financial transactions, pay bills or move money. Approved payroll workflows may send reviewed earnings amounts to ADP Time cards; that is not payroll submission or a transfer of wages.
Service providers and access
Vercel hosts the app and its private backup files. Supabase stores private application records. Microsoft provides business sign-in. Authorized source services process the information needed to provide their connections. The app’s typeface is served with the app, without a separate Google Fonts request.
Access is limited to approved company sign-ins and the controls for each part of the app. Restricted café screens and finance connection controls have additional access limits. Connection credentials are used on the server. The dedicated QuickBooks access and refresh tokens are encrypted before storage and are not returned to the browser.
Approved dispatchers can share an expiring, revocable driver route link without requiring the driver to sign in. Anyone holding that link can view only its released route or assigned day: delivery windows, destinations, site contacts, operating instructions and packing notes. It does not provide access to the platform, payroll, financial totals, other drivers or employee schedules. Treat the link as private, send it only to the intended driver, and revoke it when it is no longer needed.
Keeping records and disconnecting
Saved workpapers, source records and review history are kept for company operational and recordkeeping needs. The current nightly backup schedule keeps daily copies for 35 days and the first available completed backup in each of the last 12 months. Separate source-capture backup files have no automatic expiry and are currently retained indefinitely. The nightly backup does not include sign-in sessions or the dedicated QuickBooks credentials.
Disconnecting or revoking a source authorization does not delete information already imported, retained source snapshots, review history or existing backups. Revocation of the dedicated QuickBooks authorization also does not disconnect separate bank feeds or other applications. Use the connection’s displayed result to check whether disconnection was confirmed.
The company handles access, correction and removal requests in light of its operational and legal recordkeeping needs. There is no single automatic deletion deadline for all records. Contact AJ at armand@jayscatering.com with a question, an access concern or a request to correct or remove information.