Privacy Notice
A bilingual draft explaining how NeighbourCuisine handles customer account, order, delivery, and food-preference information.
Who is responsible
This draft notice applies to the NeighbourCuisine website, customer accounts, ordering, delivery, and related support. The organization responsible is NEIGHBOURCUISINE INC., 36 Zorra Street, Apartment 1004, Etobicoke, Ontario, M8Z 0G5, Canada. For privacy questions, access or correction requests, or a concern about our handling of information, contact the Privacy Officer at privacy@neighbourcuisine.com.
Information we handle
Depending on how you use the service, this may include your name, email address, optional phone number, account credentials and language choice; delivery address, unit, buzzer and instructions; meals, orders, delivery status and subscription selections; payment amounts, status and payment-provider references; messages and details you submit in support or catering requests; and food preferences, ingredient exclusions, allergies or other dietary information you choose to provide. If you choose Google sign-in, we receive your Google account's verified email address and stable Google account identifier. An optional phone number is saved to your account profile only; it is not verified or currently used for sign-in or automatic messages. The website stores password hashes and payment references; the application code does not store full card numbers or your Google password. The payment provider may collect card details directly when you pay.
Why we use it
We use information to create and secure accounts; take, prepare, charge for and deliver orders; check whether a delivery address is serviceable; remember your selected meals and preferences; communicate about orders, account security and support; review refunds, food-safety questions and service issues; prevent fraud and protect the service; and meet legal, tax, accounting and record-keeping duties. An optional phone number is currently kept as account-profile information and is not used to contact you. We do not use allergy or dietary information to diagnose a condition. Please share only the details needed to help us prepare and deliver your order safely.
Food preferences and information about others
Allergy and dietary details can be sensitive. Saving an allergy or dietary profile requires a separate affirmative opt-in. You can withdraw that consent and remove the saved profile by clearing it and saving; information already attached to an order may still be used to handle that order and retained with its records. Relevant information may be made available to the kitchen or support staff who need it to review or fulfil your order. Food preference notes are not a guarantee that a meal is free from an allergen. If you provide information about a guest or delivery recipient, make sure you are authorized to share it and that the person understands how it will be used for the requested service. Our target is to delete or irreversibly de-identify guest or recipient contact and dietary information within 90 days after the related delivery or event is completed or the request is closed. This is a policy target, not a current production guarantee; the production cleanup must be implemented and verified first.
When information is shared
We make relevant information available to authorized NeighbourCuisine staff and assigned delivery personnel only as needed to take, prepare, support and deliver an order. We also use service providers for functions such as payment processing, address validation when enabled, transactional email, hosting, database operation and private file storage. If you choose Google sign-in, Google processes the authentication request and returns your verified email address and stable account identifier to us; we do not receive your Google password. Google handles the sign-in under its own privacy terms. The code also integrates Stripe for test-mode payment workflows and Google Address Validation when configured; the hosting, email and storage providers and their processing locations depend on the environment and have not yet been confirmed for production. Before launch, we must review provider contracts and confirm that each provider is limited to the service it performs and is required to protect the information. We may also disclose information where required by law, to respond to a valid legal process, protect safety or rights, or handle a business transfer under appropriate safeguards.
Address verification and payment
When Google Address Validation is enabled, the street address, city, province and postal code you submit may be sent to Google to validate the address and determine whether delivery is available. For online payment, Stripe or another provider shown at checkout processes the payment. NeighbourCuisine receives payment status and reference identifiers needed to reconcile the order; the provider's own privacy terms apply to information it collects directly. The current application is configured for test-mode payments, and production payment processing has not been confirmed.
Cookies and browser storage
The application uses an essential, HTTP-only sign-in session cookie. It also uses browser local or session storage for functions such as your cart, selected delivery address, language preference and checkout recovery. You can clear browser storage in your browser settings, but doing so may remove saved selections or require you to sign in again. This draft describes the storage observed in the application code; any analytics, advertising or other tracking tools used by the live hosting environment must be confirmed before publication.
Storage, access and security
Personal information is stored in the systems used to operate the service. The production hosting, database, file-storage providers and data locations have not yet been confirmed, so we cannot presently promise that all information is stored in Canada. The application uses controls such as hashed passwords, restricted staff permissions, staff multi-factor authentication for sensitive operations, session protections and private, time-limited access to delivery photos. No method of transmission or storage is completely secure, and safeguards must be reviewed as the service and providers change.
Retention and account closure
We keep information only as long as needed for the purposes described here and as required to meet legal obligations, resolve disputes and maintain appropriate business records. The application is configured to remove in-app notifications after one year and delivery-proof photos after 90 days. Closing an account immediately deactivates it and starts a 30-day verified recovery period. After the recovery period, the account-erasure job removes login credentials, saved addresses, optional phone number, food preferences, saved allergy profiles, notification preferences and payment-method references; it also removes resolved support conversations and anonymizes closed catering requests. Erasure is deferred while an order, weekly-plan charge run, refund or change request, support case or catering request remains open or an active legal-retention hold applies. The current application schedule also removes order contact and address snapshots, order-linked allergy-review snapshots, and stored kitchen-label PDFs after six years from the end of the related tax year, unless a legal exception or retention hold applies; financial and other required order evidence is retained. This six-year schedule is an application setting, not a blanket legal period for all personal information, and still needs accountant/legal approval. The target schedule is to retain operational and security audit events for one year from creation, minimizing personal fields, and to keep encrypted rolling backups for no more than 35 days. Restored backups must reapply deletion requests and legal holds before customer access is restored. These are approved policy targets, not current production guarantees: audit cleanup, guest-data cleanup and backup rotation must be configured and verified before the targets take effect. Tax-record periods depend on the record and applicable law; we do not apply a blanket seven-year period to all information.
Your choices and privacy requests
You may update information available in your account and change optional email-notification preferences. You may ask us to confirm whether we hold your personal information, provide access, correct inaccurate information, or explain how it has been used or disclosed. Send requests to privacy@neighbourcuisine.com; we may ask you to verify your identity. We handle requests under applicable law, including its permitted limits and response extensions. Withdrawing consent may prevent us from providing a service that needs the information, such as delivering to an address. You may also raise a concern with the Office of the Privacy Commissioner of Canada if you are not satisfied with our response.
Contact and changes
Contact NEIGHBOURCUISINE INC. about this notice or a privacy request at privacy@neighbourcuisine.com or 36 Zorra Street, Apartment 1004, Etobicoke, Ontario, M8Z 0G5, Canada. We may update this notice as our practices change. We will post the revised notice with a new effective date and provide any additional notice or consent required by law. This is a working draft; the owner has approved the public Privacy Officer title and privacy@neighbourcuisine.com address. Before this notice is final, the business must confirm internal responsibility for the role, mailbox monitoring and request handling, provider list and locations, full retention schedule, and production deletion process.
Privacy references
This draft was informed by a preliminary review of the Personal Information Protection and Electronic Documents Act (PIPEDA) and official privacy guidance. Counsel should confirm how the law applies to the business and its data flows. See the PIPEDA text, the Office of the Privacy Commissioner of Canada's fair information principles, and its access-request guidance.