VenuewardBack to the app

Venueward privacy notice.

How we handle your information in the Venueward service and staff web pilot.

Updated 29 September 2026

Who we are

Venueward is operated by Mohammed Islam. For privacy questions, information requests or privacy complaints, email mohammed.j.islam95@gmail.com.

This notice covers the Venueward app, website and support service. Venueward helps hospitality businesses manage their teams, reservations, daily checks and venue records.

Your business and Venueward

Your employer or restaurant decides why it uses staff, applicant, guest and operational records. It is the data controller for that use. Venueward processes those records to provide the service on the business’s instructions. The business should give you its own privacy information, including its retention rules.

Mohammed Islam is separately responsible for Venueward’s account administration, customer relationships, support correspondence and service-security activities. Contact us if you are unsure where to direct a request or no longer have app access.

Information we handle

Depending on the features your business uses, information includes:

Information comes from you, authorised business users, their uploads and the service’s activity and security functions. A restaurant may enter information received in person or by telephone. Please avoid unnecessary medical information, identity documents, passwords or payment-card details in general notes and support emails.

Search terms sent to retrieve records may appear in our service provider’s technical request logs.

Purposes and lawful bases

For processing where Venueward is the controller:

The business determines its lawful bases for employment and guest records. Health information also needs an applicable special-category condition. Accepting an invitation or allowing notifications is not blanket consent to employment or health-data processing.

Sign-in and access information is necessary to use an account. Your business should explain other information it requires. Venueward does not use customer business records for marketing, sell those records, make hiring decisions or score employee performance.

Recorded stock demand helps suggest minimum stock and order quantities.

Access and providers

Business access depends on membership, role, work area and the feature. Some actions require shift approval or manager confirmation. Staff can see their own absence details; authorised managers can access the relevant staff records. Absence reasons are not copied into cover offers. Businesses are responsible for copies they print, export or share.

The service uses:

Relevant information may also be disclosed where legally required or needed for a specific professional-advice or legal matter.

The app database is configured in London. Suppliers may handle information elsewhere, including the United States. Supabase’s and OpenAI Sites’ published processing terms describe UK transfer clauses; Expo and Google describe the UK extension to the Data Privacy Framework; Apple describes contractual safeguards. These are supplier arrangements, whose application depends on the service and information involved. Contact us for details relevant to your data.

The website and staff app

The public product walkthrough uses fictional venue, staff and guest records; its examples do not connect to a live business. Browser interactions with sample data can be held for that browser session. Do not enter real personal or business information into the public demonstration.

The staff website loads a sign-in page that anyone with the link can open. Operational records require an authorised Venueward account and the appropriate business membership and permissions. Website hosting involves network/request information needed to deliver and protect the pages.

Retention and deletion

Retention depends on the information and its purpose. Account details are needed to maintain authorised access. Support correspondence is kept while needed to resolve the enquiry and understand related follow-up. Privacy-case records document the request, action and outcome. Security information supports investigating misuse; relevant contract or financial information may be needed for legal duties or claims.

Business records follow the business’s instructions and applicable requirements: recruitment needs, employment/payroll responsibilities, a reservation or unresolved complaint, food-safety records, inspections or a specific legal claim. Named attribution is retained only where separately necessary. Keeping records indefinitely merely because storage is available is not the purpose. Ask the business for its particular periods.

Mohammed Islam is responsible for the retention review process, with customer-controller instructions for business records. The adopted policy requires a monthly review of records due for review, a policy review every 90 days, and earlier review when the relevant purpose ends. When information is no longer needed, the policy requires deletion or genuine anonymisation across records, files, history and request copies. Illness reasons and health notes are reviewed separately: a need to keep attendance hours does not justify keeping health details.

Any point-in-time recovery copies held by Venueward also need a documented retention decision. Deleting a live record does not necessarily remove an existing copy immediately. Supabase Pro daily database backups were observed on 28 October 2026; this is a dated observation, not a claim about their current health. The separate encrypted Storage copy described below is still being set up and has no verified first cloud copy or active nightly schedule.

Venueward Backups: Google Drive connection

Additional disclosure prepared 29 October 2026

Current status: this additional uploaded-file backup is being set up. Its first cloud copy, recovery check and nightly operation have not been verified. The following describes its intended operation after authorised setup, rather than an already running service. See the Venueward Backups information page.

Purpose, permission and information

The connection requests Google Drive’s drive.file permission. This permits access to files created through the app or specifically shared with it; it is not a request to manage every file in the account. The planned job is configured to use a private folder created through the dedicated app.

The job will use the Google Drive API to create, list and read back its encrypted backup objects and their metadata, including identifiers, sizes and timestamps. The encrypted inventory includes the names and other details needed to recover the source uploads. Google Drive will hold encrypted file contents and inventory, together with Drive’s ordinary file metadata.

These data will be used to make, check and recover the authorised uploaded-file copies. The connection is not intended to analyse the account’s unrelated Drive content. It does not add a new marketing, advertising or sale use of business records.

Providers and access

The intended GitHub Actions job will read original private files from Supabase, process their unencrypted bytes while capturing and verifying them, and encrypt the backup contents before uploading them to Google Drive. Connection credentials and the encryption key will be supplied through private repository Actions secrets. Authorised repository workflows and people with sufficient repository permissions can have access to those secrets; the operator remains responsible for that access.

Google Drive access is authorised by the operator through Google’s consent flow. Recovery depends on retaining the separate encryption key. Authorised recovery can make the original contents readable again. This connection does not provide public access to the uploaded business files.

Retention, stopping access and requests

The prepared job marks the latest 30 Storage points active but does not automatically delete older encrypted objects. This is not a promise of deletion after 30 days. Removing a live record or disconnecting Google access does not itself remove an existing backup. Retention decisions and privacy requests continue to follow the main notice and the responsible business’s instructions.

The Google account owner can revoke the app’s access through Google’s account permission controls. Revoking access affects future API access; stored encrypted files, retained keys and copies already held by the operator need a separate review. Contact mohammed.j.islam95@gmail.com to ask about stopping the connection, recovery, retained copies or a privacy request. No automated account-wide erasure tool or new deletion timetable is promised here.

This mode copies accessible Storage files only. It does not export native database records, embedded database file bytes, application source or configuration, and it does not prove an atomic database-and-files snapshot or complete standalone recovery. Provider database backups are separate.

Account deletion during the web pilot

Email mohammed.j.islam95@gmail.com to request account deletion or help with your information. You can contact us even when signed out or without a business membership. We verify your identity and explain the effect on your account and business access.

If you own a business, its ongoing ownership or closure needs to be resolved. Necessary business records are considered with the responsible business under the retention criteria above. An account-deletion request does not automatically erase every record you helped create or information about other people.

We confirm what has been deleted and explain any justified retention or unresolved action. A request being received or under review is not confirmation that deletion has finished. Automated in-app account deletion is not available in this browser pilot.

Your rights and complaints

Depending on the circumstances, you can request access, correction, deletion, restriction or a portable copy of your information. You can object to processing based on legitimate interests. Where consent is the basis, you can withdraw it.

Email us using the address above; no special wording is needed. We may need proportionate identity checks. Rights requests normally receive a response within one month, with any lawful extension explained.

We acknowledge data protection complaints within 30 days, investigate and explain the outcome. You can also complain to the Information Commissioner’s Office.

Device choices

Camera and file selection support attachments you choose to add. The web pilot does not send phone push notifications and does not offer an offline copy of business records. Downloads, screenshots and printed files may remain on the device. Lock or sign out after using a shared device.