BaytiChef

Privacy Policy

Last updated: October 27, 2026

This page explains how BaytiChef collects, uses, stores, and protects information when customers, chefs, administrators, and visitors use the app, website, and related platform services.

Information We Collect

• Account details such as name, email, phone number, account role, authentication provider, profile photo, address labels, language, country, and notification preferences.
• Chef application and compliance details such as kitchen profile information, menu content, service dates, fulfillment settings, Emirates ID or similar identity details when provided, date of birth when provided, payout onboarding status, IBAN or payout metadata, tax or business information, and records needed to review chef eligibility.
• Order, cart, payment, refund, delivery, pickup, review, message, support, complaint, cancellation, and dispute information needed to operate the service.
• Technical and security data used to keep the platform reliable and safe.
• Payment and payout metadata required to verify transactions, detect fraud, support refunds, and settle chef payouts. Full card details are handled by payment providers.

How We Use It

• To manage accounts, chef applications, listings, orders, payments, payouts, delivery, pickup, reviews, support, and account deletion requests.
• To send important updates such as order status and service notifications.
• To verify chef eligibility, review food-service compliance signals, investigate incidents, handle disputes, enforce platform rules, and protect BaytiChef legally and operationally.
• To improve product quality, detect abuse, prevent fraud, secure the platform, maintain business records, and comply with legal, tax, accounting, payment-provider, and regulatory obligations.

How Information May Be Shared

• With chefs when needed to prepare, package, communicate about, and fulfill customer orders.
• With customers when needed to show chef profiles, menus, order status, pickup details, support responses, and marketplace trust information.
• With payment processors, payout providers, identity or authentication providers, delivery partners, cloud hosting, analytics, messaging, support, fraud-prevention, and security vendors that help operate BaytiChef.
• With regulators, law enforcement, courts, payment networks, insurers, lawyers, accountants, or advisers where needed for legal compliance, safety, fraud prevention, claims, disputes, investigations, or enforcement.

Chef Videos and YouTube

BaytiChef uses YouTube API Services for its chef-video feature. When a chef submits a video, we receive the original file, title, description, chef account identifier, and publishing permission. We store submissions on our server for administrative review. Submitting a video does not immediately make it public. After approval, our backend sends the video and publication metadata to YouTube for public publication on the official BaytiChef channel. Published videos and their descriptions are accessible to the public.

Only the channel owner or an authorized administrator connects the channel through Google's authorization screen. Chefs do not need to connect their personal Google accounts. We request permission to upload approved videos and read the connected channel identity and uploaded-video processing and privacy status. We store the channel ID, video IDs, and publication status to operate this feature. OAuth credentials and resumable-upload session information are encrypted in server-side storage; chefs and customers do not receive them. Our implementation does not enumerate unrelated videos, subscriptions, playlists, or viewing history.

We use Google API data to publish and display chef videos, verify the channel, and check publication status. We do not sell that data, use it for advertising targeting, or use it to train generalized AI models. Human access is limited to operating, moderating, and supporting the feature, investigating security issues, or meeting legal obligations. Our handling of Google API data follows the Google API Services User Data Policy, including its Limited Use requirements.

Original submissions are retained for review, publication, support, and relevant dispute or legal needs. Approval, rejection, or publication does not automatically delete the original file. To request removal of a submission, a published video, or stored Google API data, contact info@zoser-soft.com with the chef account and video details. We verify the request and handle removal through our support process. YouTube publication and BaytiChef's stored copy are separate: a request should identify which copies you want removed. Relevant records may be retained where required for legal or dispute-resolution purposes.

The channel owner can also revoke BaytiChef's access using Google's third-party connections settings. Revocation stops future authorized API requests; it does not itself delete stored submissions or videos already published on YouTube. Contact support to request deletion of data held by BaytiChef. When you open a video on YouTube, Google may process device, playback, cookie, or account information under the Google Privacy Policy. The YouTube Terms of Service also apply to the YouTube feature.

Retention and Security

• BaytiChef keeps information for as long as needed to operate the platform, complete orders and payouts, resolve disputes, prevent fraud, enforce agreements, and meet legal, tax, accounting, regulatory, and payment-provider requirements.
• Some order, payment, payout, chef compliance, fraud-prevention, support, and legal records may be retained after account deletion when retention is required or reasonably necessary.
• BaytiChef uses reasonable administrative, technical, and operational safeguards, but no system can guarantee absolute security.

Your Choices and Contact

For privacy requests or account data questions, contact BaytiChef support at info@zoser-soft.com. Account deletion requests can also be submitted from Account Settings where available.