Effective date: 17 October 2026
Last updated: 17 October 2026
If you had an account before 17 October 2026, this notice applies to you from 16 November 2026. Until then the previous version applies. We are emailing you about the change.
This notice explains what data we collect, why we collect it, how long we keep it, who we share it with, and the rights you hold under the Personal Data Protection Law of the Kingdom of Saudi Arabia (Royal Decree M/19 of 9/2/1443H, as amended by Royal Decree M/148 of 5/9/1444H) and its Implementing Regulation (the "PDPL"). It covers our websites, our shared sign-in service at authz.projexlabs.com, and our products: Cohort, Trellis, Skyline, OmniDeck and Projex Academy (together, the "Services").
We are the data controller for our websites and for your account. We collect what we need to run your account and the product you use, to respond to your inquiries, and to keep the Services secure. When a business uses our products with its own customers' data, we are its processor and it decides how that data is used. Some of the AI features you use send your content to AI model providers, some of which operate outside Saudi Arabia, and this notice tells you so. We do not sell personal data, we do not share it with advertisers, and we do not use your content to train AI models. You can access, correct or delete your data by emailing privacy@projexlabs.com. If you think we have got something wrong, you can complain to the Saudi Data and AI Authority (SDAIA).
The controller of your personal data is Makhabir Al-Muntajat Al-Raqamiya Company for Telecommunications and Information Technology (شركة مخابر المنتجات الرقمية للاتصالات وتقنية المعلومات), trading as Projex Labs, a one-person limited liability company registered in the Kingdom of Saudi Arabia under Unified National Number 7053866732.
We are the controller for personal data we process for our own purposes: your account, sign-in, billing, support, security, communications with you, and our websites.
We are a processor for personal data inside content our business customers put into the Services, for example the conversations between a business's customers and an AI agent it runs on Cohort, the records and files that agent collects, code and project data in Trellis, and data passing through accounts a business connects to Skyline. In those cases the business customer decides why and how the data is processed, and its own privacy notice applies. We process that data only on its instructions, under a data processing agreement. If you are the end user of one of our customers, please contact that customer first. We will help them respond to you.
When you email us or use an email-me link, we receive your name (if provided), your email address and your message. We set a single language-preference cookie (pxl_lang) on your device to remember whether you prefer the English or Arabic edition. Our hosting infrastructure generates standard server request logs (IP address, user agent, requested URL, timestamp), kept only for security and diagnostics. Some pages load web fonts from Google Fonts, which means Google receives your IP address and browser information. We do not use marketing cookies, advertising pixels, session replay, heatmaps or third-party analytics.
| Category | Examples | Services |
|---|---|---|
| Account and identity | name, email address, organisation, role | All |
| Content you submit | prompts, messages, instructions, agent charters, files, images, code, project data, notes, voice input (transcribed; audio not stored) | Cohort, Trellis, Skyline, OmniDeck, Projex Academy |
| Learning data | course enrolments, progress, submissions, grades | Projex Academy |
| Support and communications | messages you send us, feedback, survey answers | All |
| Payment information | billing name and address, payment method details | Paid plans |
Sign-in. You sign in with an account you already have at Google, Apple, Microsoft or GitHub. We do not ask for or store a password. The provider shares with us your name, your email address, a unique account identifier and, where available, your profile picture and whether your email address is verified. If you choose Apple's "Hide My Email", we receive a private relay address and use it like any other email address. We use sign-in data only to create and secure your account and to communicate with you. We do not use it for advertising and we do not sell it.
Payment cards. Card numbers are collected and stored by our payment provider, not by us. We receive and keep only limited details such as the card brand, the last four digits, the expiry date and the payment status.
| Category | Examples | Purpose |
|---|---|---|
| Usage and billing records | the models and features used, tokens, compute time, number of runs, timestamps | metering, billing, plan limits, capacity planning |
| Technical and security data | IP address, browser and device type, request logs, error logs, audit logs of account actions | security, fraud and abuse prevention, troubleshooting |
| Trial abuse checks | a one-way hashed form of your email address, network address and a device identifier, and your email domain | preventing repeated free trials |
| Local storage | sign-in session tokens, interface preferences, unsaved drafts | keeping you signed in, remembering settings |
This storage is strictly necessary or holds settings you chose, so it does not require your consent. If we ever introduce optional storage, such as analytics, we will ask for your consent first.
We do not ask you for sensitive personal data such as health information, and you should not give it to us unless the Service is configured for it. Some business customers use Cohort to collect health information from their own patients or clients. In that case we process it as their processor, access is limited to the minimum necessary staff, and we apply the additional safeguards Saudi law requires for sensitive data.
| Purpose | Lawful basis |
|---|---|
| Responding to an inquiry you send us | Taking steps at your request before a possible business relationship (PDPL Article 6), and your consent where applicable |
| Creating and running your account, providing the Services you ask for, processing your content | Performance of our agreement with you |
| Metering usage, billing, collecting payment, issuing invoices | Performance of our agreement; compliance with tax and commercial record-keeping laws |
| Security, preventing fraud and abuse (including trial abuse), and protecting our users and Services | Our legitimate interest in keeping the Services safe, assessed and documented as Saudi law requires; compliance with law |
| Operating a reliable, bilingual, secure website (language cookie, server logs) | Our legitimate interest, weighed against your privacy interests |
| Customer support and service messages (security alerts, billing notices, changes to our terms) | Performance of our agreement; legitimate interest |
| Improving the reliability and design of the Services using aggregated or de-identified usage statistics | Legitimate interest |
| Marketing emails about our products | Your consent, which you can withdraw at any time |
| Complying with legal obligations and requests from competent authorities | Compliance with law |
| Processing for a business customer as its processor | That customer's instructions; the customer is responsible for its own legal basis |
AI training. We do not use your content, your outputs, or the content our business customers process through the Services to train or improve AI models.
Automated decisions. We do not make decisions about you that produce legal or similarly significant effects based only on automated processing. Automated checks are used to prevent trial abuse and to enforce plan limits. If you think one of them has affected you wrongly, contact us and a person will review it.
Many Services work by sending your content to AI models to generate a response.
We keep personal data only as long as needed for the purpose it was collected for, then delete it or make it anonymous.
| Data | How long |
|---|---|
| Website inquiry emails | While the conversation is live, plus up to 24 months after the last interaction, then deleted or anonymised |
| Language cookie (pxl_lang) | 180 days on your device; you can clear it at any time |
| Account and profile data | For as long as your account is open, then deleted within 30 days of account closure, except where section 5.1 applies |
| Cohort session content: conversations, agent records and code changes | Kept until you delete it or close your account, then deleted within 30 days |
| Uploaded workspace bundles (Cohort) | Deleted 30 days after the last session that used them ends |
| Images and text attachments read by an AI reader (Cohort) | The original file is not kept after it is read. A description of it and a fingerprint (hash) of the file are kept with the session record |
| Voice audio (OmniDeck) | Not stored. It is transcribed as it is received |
| Voice transcripts (OmniDeck) | 24 hours, except transcripts you send to the assistant, which become part of your chat history |
| OmniDeck chats, files and memory | Until you delete them or close your account |
| Trellis, Skyline and Projex Academy content | For as long as your account or the relevant project is active, or until you delete it |
| Usage records (metering) | Kept for as long as needed for billing, and for the period Saudi tax and commercial record-keeping laws require |
| Financial records: invoices and payment records | For the period required by Saudi tax and commercial record-keeping laws |
| Security, audit and request logs | Kept only as long as needed for security and to investigate incidents |
| Trial abuse records (hashed identifiers) | Up to 3 years, to prevent repeated trials |
| Backups | Overwritten in normal rotation, usually within 30 days |
5.1 We may keep personal data longer where the law requires it, to establish or defend legal claims, or to prevent fraud and abuse. Where a business customer has set a different retention period for content it controls, that period applies.
5.2 Under Saudi law, records of processing activities are kept for the period of processing and five years after it ends.
We do not sell personal data and we do not share it for targeted advertising. We share it only as follows.
| Provider | Purpose | Location |
|---|---|---|
| Oracle Cloud Infrastructure | Cloud hosting: servers, databases, storage, key vault | Riyadh, Kingdom of Saudi Arabia |
| Cloudflare, Inc. | Website hosting, content delivery, DNS and network security | Global network |
| AI model inference providers | Generating AI responses, transcriptions and other model outputs | May be outside the Kingdom of Saudi Arabia |
| Resend, Inc. | Email delivery: account and service emails | United States |
| Moyasar | Payment processing | Kingdom of Saudi Arabia |
| Google LLC (Google Fonts) | Web font delivery | United States |
| Hugging Face, Inc. | Download of on-device voice models (OmniDeck) | United States |
We give business customers at least 30 days' notice of a new subprocessor, as set out in our data processing agreement.
Our primary infrastructure, including the databases that hold account data and content, is hosted with Oracle Cloud Infrastructure in its Riyadh region, inside the Kingdom of Saudi Arabia. We also keep backup copies on servers we operate ourselves in Riyadh.
Some providers process personal data outside the Kingdom: content delivery networks, AI model providers, email delivery, sign-in providers and web font providers. When we transfer personal data outside the Kingdom, we do so in accordance with the PDPL and its Regulation on Personal Data Transfer outside the Kingdom. That means we transfer only what the purpose needs, carry out the risk assessments the Regulation requires, and rely on a transfer mechanism it recognises, such as an adequacy decision or the Standard Contractual Clauses issued by SDAIA. For transfers of personal data of people in the European Economic Area or the United Kingdom, we use the European Commission's Standard Contractual Clauses or the UK equivalent where they are required. You can ask us for more information about the safeguards we use.
We never transfer personal data for advertising, profiling or secondary purposes.
Subject to the conditions and exceptions in the law, you have the right to:
How to exercise your rights. Use the controls in the product where they exist, or email privacy@projexlabs.com. We may ask you to verify your identity before we act on a request. We will respond within 30 days. If we need longer, we will tell you why, and the extension will not exceed a further 30 days. Exercising your rights is free, unless a request is manifestly unfounded or excessive.
Deleting your account. You can request deletion of your account and its data at any time at projexlabs.com/legal/delete-account or by emailing privacy@projexlabs.com. We will confirm when the deletion is complete.
If you believe we have violated your rights under the PDPL, you can file a complaint with the Saudi Data and AI Authority (SDAIA) through sdaia.gov.sa or the National Data Management Office (NDMO). If you live in the European Economic Area or the United Kingdom, you may complain to your local supervisory authority. You keep all rights under Saudi law to seek judicial redress. We also welcome complaints directly at privacy@projexlabs.com. We would rather hear about it and fix it than have it go to the authority first.
We use administrative, technical and physical safeguards designed to protect personal data, including encryption in transit, encryption of sensitive credentials at rest, access controls limited to staff who need them, one-way hashing of API keys, audit logs, and separation of each customer account's data. We align our broader security posture with the National Cybersecurity Authority (NCA) Essential Cybersecurity Controls (ECC) and Cloud Cybersecurity Controls (CCC) where applicable.
No method of transmission or storage is completely secure. If a personal data breach occurs, we will notify SDAIA within 72 hours of becoming aware of it, and business customers without undue delay, and affected individuals without undue delay where the breach may harm them, as the law requires.
The Services are not intended for anyone under 18, and we do not knowingly collect personal data from children. If you believe a child has given us personal data, contact privacy@projexlabs.com and we will delete it.
We send service messages that are necessary for your account, such as security alerts, receipts and important changes; you cannot opt out of these while your account is open. We send marketing messages only with your consent. Each one identifies us and contains a free way to unsubscribe, which we honour promptly.
We may update this notice to reflect changes to the law, our practices or the Services. If we make a material change (new data collection, new purposes, new recipients, new international transfers), we will notify you by email or in the Services at least 30 days before it takes effect. Where a change affects how we use data we received from a sign-in provider, or the law requires consent, we will ask for your consent before applying it. The date at the top shows when this notice was last updated.
Privacy requests and questions: privacy@projexlabs.com, with the subject "Privacy request" and your preferred language (EN/AR). We respond within 30 days.
Post: Makhabir Al-Muntajat Al-Raqamiya Company for Telecommunications and Information Technology (Projex Labs), Building 6268, Al Olaya Street, Al Olaya District, Secondary No. 3953, Riyadh 12211, Kingdom of Saudi Arabia.
PDPL Compliance Matrix
This is the same matrix we share with partners who ask for documented compliance.
| PDPL obligation | How we comply | Reference |
|---|---|---|
| Privacy notice | This page: plain-English summary plus formal sections 1 to 14 | Sections 1 to 14 |
| Identity of the data controller | Projex Labs, registered company and address | Section 1 |
| Lawful basis for processing | Table of purposes and bases | Section 3 |
| Purpose specification | Each category of data is tied to a stated purpose | Sections 2 and 3 |
| Data minimisation | We collect only what each purpose needs; no advertising trackers, no third-party analytics | Sections 2 and 3 |
| Consent management | Consent only where it is the basis (marketing); withdrawable at any time | Sections 3 and 8 |
| Retention | Retention table by category of data | Section 5 |
| Recipients and processors | Subprocessor table; no advertisers; no sale of data | Section 6 |
| Cross-border transfer rules | Transfers under the PDPL Transfer Regulation | Section 7 |
| AI processing disclosure | Recipients by category, notice in this document, no training on your content | Sections 3 and 4 |
| Data subject rights | Access, correction, deletion, consent withdrawal, objection and restriction, automated-decision review | Section 8 |
| Right to complain | SDAIA and NDMO route disclosed | Section 9 |
| Security measures | Safeguards listed; alignment with NCA ECC and CCC | Section 10 |
| Children's data | Not intended for under 18; deletion on notification | Section 11 |
| Breach notification | Notice to SDAIA within 72 hours; affected people without undue delay where the breach may harm them | Section 10 |
| Automated decision-making | None with legal or similarly significant effect | Section 3 |
All privacy-related requests (access, correction, deletion, withdrawal of consent, complaint) go through one address. Please include "Privacy request" in the subject line so we triage correctly.