YOUR INFORMATION. YOUR CHOICE.
Privacy notice.
Prelaunch notice · 13 September 2026
About BITE
The BITE website is managed under the name Bite Creates Ltd., based in Riyadh, Saudi Arabia. This is the business name designated to operate BITE and manage the personal data described here; business registration is still in progress. Our contact for enquiries and data-protection requests is info@bitecreates.com. Registered details will be added once confirmed.
Website hosting
Google’s Firebase Hosting delivers this website. It receives technical connection data, including your IP address and browser requests, to deliver pages and help protect the service. We do not currently run optional analytics or advertising trackers.
Launch waitlist and enquiries
The waitlist collects your Saudi mobile number and, if you choose, your name. We use them to manage the list and send BITE launch updates by SMS with your consent. Our enquiry form collects your name, email address, topic and message to respond to you. Form records also include a security identifier, submission time, language, website source and privacy-notice version.
If you email us, your email provider delivers your message to our Google-hosted business mailbox. We use your message and contact details to respond. Please provide only information relevant to your enquiry, and do not include payment details or sensitive personal information.
Your choices and our legal bases
Joining the waitlist is voluntary and requires you to tick an initially empty consent box for BITE launch SMS updates only. Selecting “Send enquiry” is your affirmative consent to processing the details you provide to answer that enquiry. We record the submission time and notice version; waitlist records also record launch consent. An enquiry or direct email never subscribes you to marketing.
You can withdraw consent at any time by emailing info@bitecreates.com. This stops future consent-based use without affecting processing that was lawful before withdrawal. If you do not provide the required contact details, we cannot add you to the waitlist or reply through the form. You can still browse the website.
Essential technical processing supports our legitimate interest in operating a secure website and preventing spam, with access and collection limited to that purpose. We may also process information where necessary to meet a legal obligation. Launch messages are limited to the consent you give; no SMS delivery service is connected yet. This website is not intended for children.
Form protection and service providers
Firebase Authentication creates an anonymous security identifier; it does not ask you to create an account or verify your phone by SMS. Firebase App Check and reCAPTCHA Enterprise help assess whether a submission is genuine. These services process technical information such as IP addresses, browser or device signals and security tokens, and may use essential browser storage or cookies. A failed check can prevent submission; email is an alternative.
Form records are stored in Cloud Firestore in Dammam, Saudi Arabia (me-central2). This is the database location, not a promise that all processing stays in Saudi Arabia: Firebase Authentication operates in the United States, and Hosting, App Check, reCAPTCHA and email services can process data through Google’s international infrastructure. Google and its authorised service providers support these services under the applicable service and data-processing terms. See Firebase’s privacy and security information and Google’s Privacy Policy.
Access to form records is restricted to authorised administration; they are not publicly readable. We do not sell your information. We share it only as needed with the service providers above or where disclosure is required by law. We will update this notice before adding a launch-message provider.
How long we keep information
Our waitlist retention limit is 12 months from signup, or less if you withdraw consent or the launch-update purpose is complete. If the launch is delayed beyond that period, fresh consent is needed to remain on the list. Enquiries and related correspondence are kept for up to six months after the enquiry is resolved.
We review retained records monthly and remove expired records manually; there is no automatic deletion timer. Associated anonymous security accounts are removed when no longer needed for a retained submission, and unused accounts are reviewed against a 12-month limit. Browser preferences remain until changed or cleared. Google’s operational logs and backup deletion follow its service-specific retention terms. Information needed for a specific legal obligation or dispute may be retained for the necessary period, with access restricted.
Cookies, storage and analytics
This site stores your cookie preference and motion preference on this device, where browser storage is available. It does not currently load Google Analytics or Firebase Analytics.
When you submit a form, essential security storage supports anonymous authentication and spam checks; reCAPTCHA may set its _GRECAPTCHA cookie. These protections are separate from optional analytics. Clearing browser storage removes local preferences and identifiers, but does not delete a form record already submitted to us.
The planned analytics feature will remain off until it is introduced with an updated notice and you choose “Allow analytics.” Choosing “Essential only” will keep optional analytics off. You can change your choice using . Form names, phone numbers, email addresses and messages will never be included in our analytics events.
Your questions and requests
You may ask to be informed about our processing, access your personal data, obtain a copy, correct it, request its deletion or withdraw consent, subject to applicable Saudi law. Email info@bitecreates.com and tell us what you need. We will request only enough information to verify that the data is yours, and explain any lawful limit on your request. You may also complain to the Saudi Data & AI Authority (SDAIA) through its Data Governance Platform.
Updates
We will update this notice when our practices or registered details change, including before adding optional analytics or a launch-message provider. We will seek fresh consent where needed. The date above identifies this version.