GRACE HOSPITALITY PRIVACY POLICY

1. Scope

This Privacy Policy explains how information is handled inside the GRACE HOSPITALITY mobile application. This version has no backend server, user account system, cloud database, analytics service, advertising SDK, or automatic transactional submission system.

2. Information entered by users

The app contains a local hospitality brief form. A completed local brief uses the following fields:

• Full name — required. Used to identify the person preparing the locally stored brief.
• Email address — required. Used as contact information inside the local record. It is not emailed or transmitted automatically.
• Phone number — optional. Used only as an additional contact reference inside the local record.
• Selected service area — required. Identifies the hospitality-planning area chosen by the user.
• Property or project name — optional. Used to label the local record.
• Property type — required. Provides context for the hospitality-planning request.
• Preferred timing — optional. Records the user’s expected planning period.
• Primary goals — required. Records the main hospitality needs described by the user.
• Additional notes — optional. Records extra context or special requirements.

Drafts may contain any subset of these fields because an incomplete brief can be saved as a draft.

3. Other locally stored app data

The app may also store:

• Saved service favourites.
• Recently viewed service identifiers.
• Local brief status.
• Local record creation and last-updated times.
• Local draft and brief history.

4. Storage and transmission

The information described above is stored in Android SharedPreferences on the user’s device. The app does not transmit this information to GRACE HOSPITALITY LLC, the privacy contact, a hotel, a restaurant, another service provider, or an external server.

Messages such as “Details received by the app,” “Saved locally,” or “In process on this device” mean only that the application validated or stored a record locally. They do not mean that the business received, accepted, confirmed, processed, or fulfilled the request.

The local SharedPreferences file is excluded from the app’s Android cloud-backup and device-transfer backup rules.

5. Retention and deletion

Local records, drafts, favourites, and recently viewed items remain on the device until the user deletes a record, uses the in-app delete-all control, clears the app’s storage through Android settings, or uninstalls the app. Deleting a local record removes it from the app’s local history.

6. Contact email action

The Contact Us screen can open an installed external email application using a mailto action. This action is separate from the local brief flow. The app does not automatically attach or send locally stored brief information. The user decides whether to compose and send an email in the external email application.

7. Information collected automatically

The app does not collect analytics identifiers, advertising identifiers, account credentials, precise location, device contacts, camera content, microphone recordings, or media-library content.

8. Services and capabilities not used

This version does not use:

• Backend servers or cloud databases.
• Firebase, analytics, tracking, or advertising SDKs.
• Authentication, passwords, user accounts, or access tokens.
• Payment processing or storage of card numbers, CVV/CVC codes, PINs, banking credentials, or raw payment credentials.
• Location, camera, microphone, contacts, notifications, or media/storage access.
• Internet access or third-party image-loading services for the core catalogue.
• Browser actions or website links.
• External communication applications for transactional submission.

9. Data sharing

The app does not sell or share locally stored brief data with advertisers, analytics providers, or external servers. A user may independently choose to send a separate email through an external email application.

10. Security limitations

The app uses Android private local storage for SharedPreferences. No storage method can be guaranteed to be completely secure. Users should avoid entering information that is not necessary for the local hospitality brief.

11. Children’s privacy

The app is intended for general business and hospitality-planning use and is not designed to knowingly collect information from children.

12. Changes to this policy

This policy may be updated when the app’s functionality, fields, storage, permissions, or external services change. The effective date should be reviewed when an updated version is released.

13. User choices and privacy contact

Users can choose which optional fields to provide and can delete local information using the methods described above. For a privacy enquiry, contact dev@gracehospitality.online.