1.Who we are
The controller of the personal data in this policy is Transformational Retail Holding Company (شركة التجزئة التحولية القابضة), commercial registration 7054544486, VAT number 314841629700003, address Khobar, Saudi Arabia, operating as BAYRQ («بيرق») at bayrq.com ("we").
Contact about your data: support@bayrq.com.
This policy is issued under Article 12 of the Personal Data Protection Law, Royal Decree M/19 dated 9/2/1443H, amended by Royal Decree M/148 dated 5/9/1444H (the "PDPL"), its Implementing Regulation, the Regulation on Personal Data Transfer outside the Kingdom, Article 5 of the E-commerce Law, and Articles 5 and 6 of its Implementing Regulations.
2.Who it covers
This policy covers Buyers who buy Products, Supporters who send Supports, Creators who hold accounts, and visitors to BAYRQ pages, links and stores, including stores on Creators' own domains.
It does not cover outside platforms you go to from a Creator's link (such as their social accounts), which have their own policies.
3.Definitions
Personal data, processing, controller, processor and sensitive data have the meanings in Article 1 of the PDPL.
4.The data we collect
4.1Buyers
- Name, phone number (for the code and delivery), and email (for confirmation and invoice).
- National address (short code), city and the full address the lookup returns.
- Order details: Products, sizes, amounts, payment method, shipping status and tracking number.
- Limited payment data returned by the payment provider (such as card type, last four digits and the result). We do not keep the full card number.
- If you report a defect: the photos you send and the description.
4.2Supporters
- The amount, the name you write (if any), and your message (if any).
- Email if you enter it for the receipt (optional).
- Limited payment data as in 4.1.
- We do not ask for a phone number for Supports.
4.3Creators
- Name, phone number, email, link name and social account links.
- The Content you upload (designs, logos, images, text).
- Payout and verification data: IBAN and bank name, ID photo, bank account proof photo, and your confirmation that you own the account. For Creators abroad: bank or PayPal account details, and the identity-check result from the identity-check provider (which may include an ID or passport photo and a selfie).
- Earnings, movements, payouts and invoices.
- If you buy a domain: the owner details the registrar and ICANN require (name in English letters, email, address, city, postal code).
- If you connect streaming integrations (such as Twitch, Kick, Streamlabs or StreamElements): account identifiers and the tokens needed for the connection.
4.4All visitors
- Technical data: IP address, the country derived from it, device and browser type, pages visited and visit times.
- Cookies, as in section 14.
4.5Help requests by WhatsApp
See section 7.
5.Purposes and legal bases
- Purpose
- Fulfilling the order: code verification, payment, delivery, invoice, defects and returns
- Data
- Buyer data (4.1)
- Legal basis
- Performing an agreement the data subject is party to (PDPL Article 6(2))
- Purpose
- Receiving a Support, passing it to the Creator and sending the receipt
- Data
- Supporter data (4.2)
- Legal basis
- Performing an agreement (Article 6(2))
- Purpose
- Providing the Services to the Creator and paying out Earnings
- Data
- Creator data (4.3)
- Legal basis
- Performing an agreement (Article 6(2))
- Purpose
- Verifying identity and bank account ownership, and preventing fraud
- Data
- ID, IBAN, account proof
- Legal basis
- Performing an agreement, legal obligations, and legitimate interest (Article 6(2) and (4))
- Purpose
- Issuing e-invoices and keeping accounting and tax records
- Data
- Order and invoice data
- Legal basis
- Processing required by another law (Article 6(2)), the VAT Law and e-invoicing rules
- Purpose
- Answering help requests and complaints
- Data
- Section 7
- Legal basis
- Performing an agreement, and legitimate interest
- Purpose
- Platform security, abuse prevention and rate limits
- Data
- Technical data
- Legal basis
- Legitimate interest (Article 6(4))
- Purpose
- Improving the Services with aggregate statistics (such as link visitor counts)
- Data
- Technical data
- Legal basis
- Legitimate interest, or consent where required
- Purpose
- Marketing messages
- Data
- Email or phone
- Legal basis
- Consent only (PDPL Articles 25 and 26), see section 15
- Purpose
- Complying with authorities' requests and defending our rights
- Data
- As needed
- Legal basis
- Processing required by another law, and legitimate interest
| Purpose | Data | Legal basis |
|---|---|---|
| Fulfilling the order: code verification, payment, delivery, invoice, defects and returns | Buyer data (4.1) | Performing an agreement the data subject is party to (PDPL Article 6(2)) |
| Receiving a Support, passing it to the Creator and sending the receipt | Supporter data (4.2) | Performing an agreement (Article 6(2)) |
| Providing the Services to the Creator and paying out Earnings | Creator data (4.3) | Performing an agreement (Article 6(2)) |
| Verifying identity and bank account ownership, and preventing fraud | ID, IBAN, account proof | Performing an agreement, legal obligations, and legitimate interest (Article 6(2) and (4)) |
| Issuing e-invoices and keeping accounting and tax records | Order and invoice data | Processing required by another law (Article 6(2)), the VAT Law and e-invoicing rules |
| Answering help requests and complaints | Section 7 | Performing an agreement, and legitimate interest |
| Platform security, abuse prevention and rate limits | Technical data | Legitimate interest (Article 6(4)) |
| Improving the Services with aggregate statistics (such as link visitor counts) | Technical data | Legitimate interest, or consent where required |
| Marketing messages | Email or phone | Consent only (PDPL Articles 25 and 26), see section 15 |
| Complying with authorities' requests and defending our rights | As needed | Processing required by another law, and legitimate interest |
6.What the Creator sees
The Creator sees only the Buyer's name and city on the order. They do not see your phone, email or address, and cannot search for you by your number.
The Creator sees the Supporter's name, message and amount if you write them, and may show them on their link or on their live stream through alert tools.
The Creator does not see the help requests you send us (section 7).
7.Help requests by WhatsApp
What we collect. When you write to us from the "Contact us" page on any link or store, we collect: your WhatsApp number, your message, your name if you write it (optional), the order number if you pick or type one (optional), the topic (an order you placed, a question before buying, or something else), the store you wrote from, and the page language. We record internally whether your number is verified and whether it matches the Buyer's number on the order, so we only share an order's details with its owner. We use your IP address for message limits and abuse prevention.
How we use it. Our support team replies to you on WhatsApp from the team's phone, only to help with what you wrote. We use your number for nothing else, and we send you no automatic or marketing message because of it.
Who sees it. Only BAYRQ's support team. The Creator does not see it, and we do not share it with them.
Legal basis. If your message is about an order you placed: performing an agreement you are party to (PDPL Article 6(2)). Otherwise: our legitimate interest in answering people who ask for our help (Article 6(4)), without prejudice to your rights or interests.
Retention. We keep the message and its replies for 12 months after it is closed; then our systems delete it automatically.
WhatsApp. Replies go through WhatsApp, a service run by Meta. Your messages there are also subject to WhatsApp's policy and may be processed outside the Kingdom (section 10).
8.Sharing data
We do not sell your data.
We share data only as far as needed with the parties below. Most act as processors on our behalf under Article 8 of the PDPL:
- Party
- Moyasar
- Purpose
- Processing mada, Visa, Mastercard and Apple Pay payments
- Data
- Payment data and amount
- Party
- Tamara and Tabby
- Purpose
- Pay-later and instalments for Products
- Data
- Name, phone, email, address and order details; they run their own assessment as independent controllers
- Party
- PayPal (later, for Supports and some Creator payouts)
- Purpose
- Payment and payout
- Data
- Payment and payout data
- Party
- The carrier (currently SMSA)
- Purpose
- Delivering orders
- Data
- Name, phone and address
- Party
- National address service
- Purpose
- Checking the address
- Data
- Short code
- Party
- Msegat
- Purpose
- Sending codes by SMS
- Data
- Phone number and code text
- Party
- WhatsApp (Meta)
- Purpose
- Sending codes, and the support team's replies
- Data
- Phone number and messages
- Party
- Identity-check provider
- Purpose
- Verifying Creators abroad
- Data
- ID data and photo
- Party
- The bank (Alinma Bank)
- Purpose
- Paying out Earnings
- Data
- Name, IBAN and amount
- Party
- Hosting and email provider (Amazon Web Services)
- Purpose
- Running the platform, storing data and sending email
- Data
- All stored data
- Party
- Security and network provider (Cloudflare)
- Purpose
- Protecting the site and routing traffic
- Data
- Technical data
- Party
- Google (Google Analytics)
- Purpose
- Measuring visits to public pages
- Data
- Device and browsing data, a cookie identifier and approximate location; no name, phone number or email
- Party
- The registrar (Tucows through OpenSRS)
- Purpose
- Registering Creators' domains
- Data
- Owner details
- Party
- Streaming platforms and alert tools a Creator connects
- Purpose
- Showing support alerts
- Data
- Supporter's name, message and amount
- Party
- Zakat, Tax and Customs Authority
- Purpose
- E-invoicing and returns
- Data
- Invoice data
- Party
- Competent government and judicial authorities
- Purpose
- When lawfully required
- Data
- What is requested
- Party
- Professional advisers (lawyers, accountants, auditors)
- Purpose
- Advice and audit
- Data
- What is needed, under confidentiality
- Party
- A successor to the business
- Purpose
- On a merger, sale or restructuring
- Data
- Data relating to the business transferred
| Party | Purpose | Data |
|---|---|---|
| Moyasar | Processing mada, Visa, Mastercard and Apple Pay payments | Payment data and amount |
| Tamara and Tabby | Pay-later and instalments for Products | Name, phone, email, address and order details; they run their own assessment as independent controllers |
| PayPal (later, for Supports and some Creator payouts) | Payment and payout | Payment and payout data |
| The carrier (currently SMSA) | Delivering orders | Name, phone and address |
| National address service | Checking the address | Short code |
| Msegat | Sending codes by SMS | Phone number and code text |
| WhatsApp (Meta) | Sending codes, and the support team's replies | Phone number and messages |
| Identity-check provider | Verifying Creators abroad | ID data and photo |
| The bank (Alinma Bank) | Paying out Earnings | Name, IBAN and amount |
| Hosting and email provider (Amazon Web Services) | Running the platform, storing data and sending email | All stored data |
| Security and network provider (Cloudflare) | Protecting the site and routing traffic | Technical data |
| Google (Google Analytics) | Measuring visits to public pages | Device and browsing data, a cookie identifier and approximate location; no name, phone number or email |
| The registrar (Tucows through OpenSRS) | Registering Creators' domains | Owner details |
| Streaming platforms and alert tools a Creator connects | Showing support alerts | Supporter's name, message and amount |
| Zakat, Tax and Customs Authority | E-invoicing and returns | Invoice data |
| Competent government and judicial authorities | When lawfully required | What is requested |
| Professional advisers (lawyers, accountants, auditors) | Advice and audit | What is needed, under confidentiality |
| A successor to the business | On a merger, sale or restructuring | Data relating to the business transferred |
Making, preparing and shipping Products is done by the company itself, so it is not a disclosure to another party.
Otherwise we disclose only in the cases Article 15 of the PDPL allows.
9.Where data is stored
Platform data is stored with Amazon Web Services in Ireland (the eu-west-1 region).
10.Transfers outside the Kingdom
Some data may be processed outside the Kingdom by: the hosting provider, WhatsApp (Meta), PayPal, the registrar (Tucows), the identity-check provider, the security provider, Google (Google Analytics), and streaming platforms.
We transfer only the minimum needed, after checking the conditions in Article 29(2) of the PDPL and the Regulation on Personal Data Transfer outside the Kingdom, or under its exceptions, and we use appropriate safeguards (such as the standard contractual clauses issued by the Saudi Data and AI Authority) where needed.
11.Retention
We keep data as long as the purpose needs it, then destroy it without delay under Article 18 of the PDPL, unless another law requires keeping it longer.
- Data
- Order and invoice data
- Period
- At least 6 years from the end of the tax year, under VAT requirements
- Data
- Buyer account data (phone, name, addresses)
- Period
- While the account is active, then 24 months from the last order, unless you ask for deletion sooner
- Data
- Support data
- Period
- 6 years for financial records; name and message deleted after 24 months
- Data
- Creator account
- Period
- While the account is open, then as needed for financial records and disputes
- Data
- ID photo and bank account proof
- Period
- Until the account is approved, then deleted, keeping only the verification record
- Data
- Defect photos
- Period
- 24 months from closing the report
- Data
- Help requests by WhatsApp
- Period
- 12 months from closing the request (section 7)
- Data
- Verification codes
- Period
- Minutes, until they expire
- Data
- Technical logs
- Period
- 90 days
| Data | Period |
|---|---|
| Order and invoice data | At least 6 years from the end of the tax year, under VAT requirements |
| Buyer account data (phone, name, addresses) | While the account is active, then 24 months from the last order, unless you ask for deletion sooner |
| Support data | 6 years for financial records; name and message deleted after 24 months |
| Creator account | While the account is open, then as needed for financial records and disputes |
| ID photo and bank account proof | Until the account is approved, then deleted, keeping only the verification record |
| Defect photos | 24 months from closing the report |
| Help requests by WhatsApp | 12 months from closing the request (section 7) |
| Verification codes | Minutes, until they expire |
| Technical logs | 90 days |
12.Security
We apply organisational, administrative and technical measures to protect data under Article 19 of the PDPL, including encryption in transit, need-to-know access, keeping defect evidence and ID photos in private (non-public) storage, and limits on code attempts.
If data leaks, is damaged or is accessed unlawfully, we notify the competent authority under Article 20 of the PDPL and its Regulation, and we notify you if it is likely to harm you. We notify the Ministry of Commerce and affected consumers within three days of learning of it under Articles 5(2)(c) and 18(2)(g) of the E-commerce Implementing Regulations.
13.Your rights
Under Article 4 of the PDPL you have:
- the right to be informed of the legal basis and purpose of collecting your data, which this policy sets out;
- the right of access to your data;
- the right to obtain it in a readable, clear format;
- the right to ask for correction, completion or updating;
- the right to ask for destruction of data no longer needed, unless a law requires keeping it.
You may withdraw consent at any time where consent is the basis, under Article 5(2) of the PDPL, without affecting the lawfulness of earlier processing.
How to use them: write to support@bayrq.com or use "Contact us". We may need to verify your identity (such as a code to your phone). We reply within 30 days under Article 21 of the PDPL and its Regulation.
You may complain to the Saudi Data and AI Authority under Article 34 of the PDPL.
14.Cookies
Essential (no consent needed): the Creator's sign-in session, the Buyer's session after code verification, the cart, language, appearance, and abuse protection.
Statistics: we use an internal counter for link visitors, and Google Analytics to measure visits to the site's public pages: the page with any code in its address removed, device and browser, country and approximate city, where the visit came from, and a completed support or order with its amount and no identifier. We send it no name, phone number or email, and it does not run on a Creator's dashboard, the stream alerts page or any link that carries a code. We have turned off its advertising signals, ad personalisation and data sharing with Google; it sets cookies (_ga) to tell visits apart, which you can block in your browser settings.
Creators' code: custom sections a Creator adds run in an isolated frame that cannot send data out.
We use no advertising cookies.
15.Marketing messages
Codes, order confirmations, invoices, shipping updates and receipts are service messages, not marketing.
We send marketing only with your consent, and give a clear way to stop it, under PDPL Articles 25 and 26 and Article 10(2) of the E-commerce Regulations.
16.Children
The Services are not aimed at anyone under 18, and we do not knowingly collect their data. If you learn a child gave us data, write to us and we will delete it.
17.A Creator's public data
What a Creator puts on their link or store (name, image, bio, accounts, Products) is public by nature and visible to anyone who visits.
YouTube API Services. BAYRQ uses YouTube API Services to read public YouTube channel data (such as a channel's name, description, subscriber count and latest videos) with an API key. We never access a Google account and never any private data. When a link page shows YouTube videos, the visitor's browser loads their thumbnails from YouTube's image server (i.ytimg.com) as the page opens, so the browser contacts YouTube; a video plays only when the visitor taps it. This is subject to the Google Privacy Policy. If we ever hold data from your Google account with your permission, you can revoke that permission at any time from your Google account's permissions page.
OpenStreetMap maps. When a store shows a map of places, the visitor's browser loads the map's pictures from OpenStreetMap's servers (tile.openstreetmap.org) as the map shows, so the browser contacts OpenStreetMap. This is subject to the OpenStreetMap Foundation Privacy Policy.
18.Changes to this policy
We update this policy when needed, publish the new version with its date, and notify Creators of material changes.
19.Contact
For questions and requests about your data: support@bayrq.com, or the address Khobar, Saudi Arabia.
20.Language
This policy is written in Arabic, and the English text is a convenience translation. If the two differ, the Arabic text prevails.