ImportExport KSA — Privacy Policy
Last updated: 10 October 2026
1. Who is responsible for your data
1.1 ImportExport KSA ("the Service") is the business-to-business trade portal offered through this website and through the ImportExport KSA mobile app once released.
1.2 The Service is operated by InfoTech Global Ltd, 128 City Road, London EC1V 2NX, United Kingdom ("we", "us"). We decide why and how the personal data described in this policy is used.
1.3 Contact for privacy questions and requests: legal@infotech-global.co.uk.
2. Who this policy is about
2.1 The Service is for business users. The personal data we handle is mainly about the individuals who register and use accounts on behalf of businesses.
2.2 The company database (section 5.9) and members' own content may also contain information about other individuals, for example a sole trader's business phone number or a contact person named in a message.
3. The data we collect, and where it comes from
3.1 Data you give us
| Category | What it includes | When |
|---|---|---|
| Account | Email address; password (stored only as a one-way hash); first name; last name; company name (optional); language preference; whether you work as buyer, seller or both; whether your email is verified; that you ticked the box accepting the terms | Registration and account settings |
| Company profile | Company name (English / Arabic); description (English / Arabic); sector; country; address; contact details; agency or distribution terms; commercial registration (CR) number; products and services with descriptions, images and prices | When you create or edit your profile |
| Trade activity | Requests for quotation (title, description, category, quantity, target market, deadline); quotes (price, currency, lead time, terms, notes); business propositions (title, summary, instrument type, percentage offered, amount sought, currency) | When you post them |
| Communications with members | Messages; introduction requests and notes; meeting requests (proposed time, time zone, topic, mode — online, in person or phone — location, notes, your response); reviews (rating and text) and replies | When you send them |
| Documents | Files you upload, with the file name, type, size, checksum, upload time and who uploaded them. This includes documents you offer as evidence for a verification badge (for example commercial registration, VAT, ISO, chamber or credit documents) and financial or corporate documents you attach to a business proposition | When you upload |
| Search and matching | Search words and filters; saved searches (label, query, filters); saved companies; your "what I am looking for" text for matching | When you use search |
| Assistant, translation, catalogue suggestions | The question you ask the assistant; the message you ask to have translated; catalogue text you paste or a catalogue file you upload for suggestions | When you use those tools. These inputs are processed to produce the answer and are not stored by us afterwards (see section 5.4) |
| Support | What you send us when you contact us | When you contact us |
3.2 Data created when you use the Service
| Category | What it includes |
|---|---|
| Membership | Plan, currency, subscription status, start and end of the billing period, and the identifiers the payment provider gives us for your customer record and subscription |
| Reveals and limits | Which company records you revealed, in which billing period and when; how many matching searches you ran each day; any individual daily limit set for you |
| Sign-in security (where available for your account) | For each signed-in session: when it started, when it was last active, the IP address and the browser or device description ("user agent"). If you switch on two-factor authentication: the secret that links your authenticator app, the date you enrolled, and short-lived sign-in challenge records |
| Password reset and email verification | Short-lived tokens (password-reset tokens are stored only as a hash) |
| Notifications | The in-app notifications created for you (for example "quote received", "RFQ awarded", "new message", "profile decision") and whether you have read them |
| Moderation and verification | The status of your profile; the decision and which staff member made it; an automated advisory assessment of your submitted profile (recommendation, flags, confidence, short rationale, model used); badges issued, by whom, with any expiry; the status, reviewer and reviewer's note of a KYC/KYB review you requested |
| Read state | When you last read each conversation |
| Technical | IP address and request details handled by our web server for security and rate limiting |
3.3 Data from the mobile app (once released)
| Category | What it includes |
|---|---|
| Push notifications | If you allow notifications: a push token for your device, the platform (iOS or Android), the app language, and when the device was registered and last seen |
| Device storage | The app keeps your sign-in tokens and push token in the device's secure storage. It keeps a small amount of non-secret data on the device (company records you revealed, and a few flags such as whether you have answered the notification prompt). This stays on your device |
| Camera, photos and files | Only when you choose to upload: the app opens the file picker, photo library or camera at your request, and uploads the file you pick. The camera permission is requested only when you press "Take a photo". The app does not use the microphone |
| Biometric lock | If you switch on the app lock, your device checks your face or fingerprint. The app is told only whether the check passed; we never receive biometric data |
3.4 Data from other sources
- Payment provider. Stripe tells us whether a payment succeeded, and your subscription's status and billing period. We do not receive your full card number.
- Other members. Other members may mention you or your company in messages, quotes, reviews and requests they send through the Service.
3.5 Data we do not ask for
We do not ask for special-category or sensitive personal data (such as health, religion or biometric data). Please do not put such data into profiles, messages or uploads.
4. Why we use your data
| Purpose | Data used | Basis |
|---|---|---|
| Create and run your account; sign you in; verify your email; reset your password | Account; sign-in security | Performance of contract |
| Take payment, manage your subscription, apply your plan's allowances | Membership; reveals and limits | Performance of contract |
| Keep accounts secure: session list, two-factor authentication, rate limits, abuse prevention | Sign-in security; technical | Legitimate interests (security); performance of contract |
| Review and publish your company profile; show it to other members; show limited profile information publicly | Company profile; moderation | Performance of contract |
| Operate RFQs, quotes, messages, introductions, meetings, reviews and propositions | Trade activity; communications | Performance of contract |
| Screen text for contact details and prohibited content | Text you enter | Legitimate interests (protecting members and the Service) |
| Issue verification badges and carry out KYC/KYB reviews you request | Documents; moderation and verification | Performance of contract |
| Provide AI-assisted features (matching, assistant, translation, catalogue suggestions, RFQ summaries, advisory profile pre-screening) | See section 6.3 | Performance of contract; legitimate interests |
| Send service messages: verification and password emails; in-app notifications; where switched on, notification emails and push notifications | Account; notifications; push token | Performance of contract |
| Find and fix errors (error tracking — not active at the date of this policy) | See section 8 | Legitimate interests |
| Understand how the Service is used, including session recording (analytics — not active at the date of this policy) | See section 8 | Your consent, which we will ask for before this is switched on (section 8.4) |
| Comply with legal obligations (for example tax and accounting records) and handle legal claims | As required | Legal obligation; legitimate interests |
We do not use your data to make decisions about you by automated means alone that have legal or similarly significant effects. Profile publication, badges and KYC/KYB outcomes are decided by a human member of staff; the AI assessment of a profile is advisory only.
We do not sell personal data. We do not currently send marketing or newsletter emails from the Service.
5. Who can see your data
5.1 The public (no account needed)
For each published company profile, the public part of the website can show: company name (English / Arabic), sector, country and badges.
5.2 Other members with an active membership
- Your published profile: names, descriptions, sector, country, address, agency or distribution terms, products and services with images and prices, badges, and reviews of your company.
- Not shown: the contact details in your profile are not published to other members.
- Your RFQs: the content of an open RFQ is shown on the RFQ board to members. The board does not show who posted it.
- Your quotes: the owner of the RFQ sees your quote with your company's display name.
- Your messages: only the other participant in the conversation.
- Your introductions and meeting requests: the member you address sees your company's display name and what you wrote.
- Your reviews and replies: members who view the reviewed company see the review with your company's display name.
- Your open propositions: members see the proposition with your company's display name. Documents attached to a proposition are not shown to other members.
Other members are not shown your email address, your personal name or your account identifier by these features. They see a company display name.
5.3 Screening of contact details
Text you enter in RFQs, quotes, propositions, messages, notes and reviews is screened automatically. Phone numbers, email addresses and bank account numbers (IBANs) that are detected may be replaced with a mask before the text is stored, or the text may be refused.
5.4 What is not stored
The question you put to the assistant, the text sent for translation and the catalogue text or file sent for suggestions are processed to produce the result and are not kept by us afterwards; the catalogue file is read in memory and discarded. RFQ summaries are held briefly in the server's memory so that repeat views do not call the AI provider again.
5.5 Our staff
Authorised staff (moderators and administrators) can see submitted profiles and the advisory AI assessment, documents offered as badge evidence, propositions and attached documents in a KYC/KYB review, and members' search limits. Access to uploaded evidence and proposition documents is through an authenticated staff-only download. The moderator account is a separate, administration-only account that cannot hold a membership.
5.6 After your account is deleted
See section 10.
5.7 Service providers
See section 6.
5.8 Legal disclosures
We may disclose data where the law requires it, or to establish, exercise or defend legal claims.
5.9 Company records shown to members
The Service lets members search company records and reveal further details of a record (which may include commercial registration number, PO box, phone number, legal form and status). Where a record relates to a sole trader or names an individual, it may be personal data. Each reveal is recorded against the member who made it. If a record contains information about you and you want to ask for it to be corrected, or to object to it being shown, email legal@infotech-global.co.uk.
6. Service providers that receive data
We use the providers below.
6.1 Core providers
| Provider | Purpose | What it receives | Status |
|---|---|---|---|
| Stripe | Card payments, subscriptions, billing portal | Your email address (prefilled at checkout for some accounts), our member reference, the plan and currency you chose; and whatever you enter on Stripe's own pages (card details, billing address). Stripe acts under its own privacy policy for payment data | In use. The Service shares a Stripe account with another service we operate |
| An object-storage provider | Stores uploaded files | The files you upload, under a path that includes your member number. Files go directly from your browser or app to the storage provider through a short-lived upload link | In use where storage is configured |
| An email delivery provider | Sends verification, password-reset and password-changed emails; where switched on, notification emails | Your email address and the content of the email | Account emails in use. Notification emails ("quote received", "RFQ awarded", "new message") are built but switched off by default |
| A hosting provider | Runs the website, the application and the database | All data in the Service | In use |
| Google Fonts (Google) | Supplies the typefaces the website displays | Your browser requests the fonts from Google's servers, which shows Google your IP address and browser details. No account data is sent | In use |
| World Bank public data service | Source of the economic indicators shown | Nothing about you. Our server fetches public figures | In use |
6.2 Mobile push (mobile app only)
| Provider | Purpose | What it receives | Status |
|---|---|---|---|
| Expo push service (which passes messages to Apple's and Google's push services) | Delivers push notifications to your phone | Your device's push token; the notification's title in your app language; a reference to the notification and the item it concerns. The body of the notification is not sent | Built; switched off by default. Devices can register before sending is switched on |
6.3 AI providers
The Service is built to use several AI providers. Which of them are active at any time depends on how the Service is configured. The providers that may receive data are:
| Provider | Used for | What it receives |
|---|---|---|
| Anthropic (Claude models) | Assistant (first choice); advisory pre-screening of submitted profiles; fallback for translation, catalogue suggestions and RFQ summaries | See the list below |
| DeepSeek | Translation, catalogue suggestions and RFQ summaries (first choice); fallback for the assistant and for profile pre-screening | See the list below |
| A self-hosted model server operated by us | A further fallback for the assistant, translation, catalogue suggestions and RFQ summaries | See the list below |
| OpenAI (embeddings model) | Meaning-based search and matching | See the list below |
What is sent, by feature:
- Assistant: your question, plus a short summary of your own account — whether your membership is active and its plan, your profile's status and a completeness estimate, and the numbers of your RFQs, quotes and saved companies. No other member's data is sent, and not the names or text behind those numbers.
- Message translation: the text of the one message you ask to translate.
- Catalogue suggestions: the catalogue text you pasted or the text extracted from the file you uploaded (up to a size cap).
- RFQ summary: the RFQ's title, description, category, quantity and target market, and the number of quotes. No names or contact details are added by us.
- Profile pre-screening: the profile you submit for review — company names, descriptions, sector, address, the contact details you entered in the profile, agency or distribution terms, and product names and descriptions. A second automated check of the profile's free text masks detected phone numbers, email addresses and IBANs before sending it, but the first check sends the profile, including its contact details, as entered.
- Meaning-based search and matching: for each published profile — company names, sector, descriptions, and product names and descriptions — to create a numerical representation that is stored in our database. And each time you search or run a match: the text of your search or of your "what I am looking for" preference.
Apart from the profile contact details mentioned above, we do not add your name, email address or account identifier to these requests. If you include personal data in the text itself, it is sent as part of that text.
6.4 Error tracking and analytics
See section 8. These are built into the Service but are not active.
7. Where your data is processed, and international transfers
7.1 The operator, InfoTech Global Ltd, is based in the United Kingdom. The website, the application and the database run with a hosting provider, and uploaded files are stored with an object-storage provider (section 6.1).
7.2 The Service is offered to businesses in Saudi Arabia and elsewhere. Data is therefore processed outside Saudi Arabia, and may be processed outside the country you are in. The Service is not hosted in Saudi Arabia.
7.3 The providers in section 6 may process data in other countries, which may be outside Saudi Arabia, the United Kingdom and the country you are in.
8. Cookies, browser storage, error tracking and analytics
8.1 Cookies we set today
| Name | Purpose | Type | Details |
|---|---|---|---|
| ksa_refresh_token | Keeps you signed in and lets the site obtain a fresh short-lived access token | Strictly necessary | HttpOnly (not readable by scripts), Secure, SameSite=Lax. Set for the parent domain of this website's address |
| ksa_auth_token | Access token issued at sign-in | Strictly necessary | HttpOnly, Secure, SameSite=Lax. Same domain. Short-lived |
The website keeps the access token it actually uses in the page's memory only; it is not written to browser storage and is lost when the page is reloaded (it is then re-issued using the refresh cookie).
The mobile app does not use cookies. It keeps its tokens in the device's secure storage.
8.2 Browser storage we use today
| Key | Where | Purpose |
|---|---|---|
| iex-lang | localStorage | Remembers whether you chose English or Arabic |
Company records you reveal are held in the page's memory only and are cleared when you sign out, when the page is reloaded or when another account signs in.
8.3 Third parties
- Stripe. When you go to Stripe's checkout or billing portal you are on Stripe's website, and Stripe sets its own cookies under its own policy.
- Google Fonts. See section 6.1.
We do not use advertising cookies or advertising trackers.
8.4 Error tracking and analytics — not active
The Service contains code for two further tools. Neither is active at the date of this policy: no error tracking, analytics or session recording is running on the Service.
Sentry (error tracking). If switched on, it would receive: details of software errors (error message and stack trace), the page address without its query string, browser and device information, timing information for a sample of page loads (about one in ten), and an opaque numeric account reference (for example ksa-member:123). The code removes sign-in tokens, cookies, request and response bodies and query strings before anything is sent, and does not send your name, email or company. Sentry's own session replay is switched off.
PostHog (product analytics and session recording). If switched on, it would receive: page views (address without query string), clicks and other interactions captured automatically (including repeated "rage" clicks and clicks that do nothing), the opaque numeric account reference above, and a session recording — a recording of how the page looked and how you moved through it. In the recording, all text on the page is masked by default (replaced with asterisks) except navigation and fixed labels that have been explicitly marked as safe; everything typed into a form field is masked; request and response contents and headers are not recorded; and console output is not recorded. PostHog would also use its own cookie and browser storage to recognise a returning browser.
Before anything is switched on. Analytics and session recording are not active at the date of this policy. Before they are switched on we will update this policy and ask for your consent. We will also update this policy before error tracking is switched on.
The mobile app has the same two tools built in and not active. If switched on in the app, analytics would send event names only (and the search mode) — not search words, message text, company names, file names or profile text.
9. How long we keep data
We keep your data for as long as your account exists. After an account is closed we keep it in archived form for as long as it is needed for legal, accounting and security reasons. The table shows what happens to each kind of data.
| Data | What happens |
|---|---|
| Sign-in session records (including IP address and user agent) | Deleted automatically about 30 days after the session was revoked or last active (never sooner than the life of the refresh token plus one day) |
| Two-factor sign-in challenges | Deleted automatically once used or expired |
| Push tokens | Deleted when you sign out of the app or unregister, when your account is deleted or is no longer active, or when the push service reports the device as no longer registered |
| Assistant questions, translation inputs, catalogue text and files sent for suggestions | Not stored by us (see section 5.4) |
| A document you delete | The record of the document is removed from your account at once. The stored file itself is not erased at that moment; it is kept in archived form |
| Account, profile, membership, reveals, searches, RFQs, quotes, messages, introductions, meetings, reviews, propositions, documents, notifications, moderation and verification records | Kept for as long as your account exists, and afterwards in archived form while needed for legal, accounting and security reasons |
| Records of deleted accounts (section 10) | Kept in archived form while needed for legal, accounting and security reasons |
| Reports and blocks (section 10.5) | A report is deleted 2 years after it is resolved; an unresolved report is kept until it is resolved. Blocks are kept until you remove them or delete your account |
| Payment and subscription records | Kept for as long as your account exists, and afterwards while needed for legal, accounting and security reasons. Stripe keeps its own records under its own policy |
| Web-server and application logs | Kept while needed for security and troubleshooting |
| Error-tracking and analytics data | None is collected: these tools are not active (section 8.4). This policy will state how long such data is kept before they are switched on |
| Support correspondence | Kept while needed to deal with your request, and afterwards while needed for legal, accounting and security reasons |
10. Deleting your account
10.1 Where self-service deletion is available for your account, you can delete your account from the account page by entering your current password. Where it is not, contact us at support@infotech-global.co.uk.
10.2 Deleting your account closes and anonymises it. It does not erase all of your data: section 10.4 lists what we keep in archived form. When an account is deleted, the following happens immediately:
- your subscription is cancelled with the payment provider;
- your account is closed and anonymised: your email address, password hash, first name, last name and company name are removed from your account record; password-reset tokens are cleared; the link to any older shared login is removed; and the account is marked as deleted, so it can no longer be signed in to. The email address becomes free to register again;
- your two-factor secret and sign-in challenges are deleted, all your sessions are revoked, and your push tokens are deleted;
- your company profile is withdrawn from the marketplace and from the moderation queue;
- your open RFQs are closed, your open propositions are withdrawn, your open quotes are withdrawn, and your pending introductions and meeting requests (sent and received) are declined.
10.3 What other members still see. So that the members you dealt with keep an intact record, the text of your messages, your quotes, your reviews and replies, and your past introductions, meeting requests and propositions remain. In each of those places your company name is replaced by the label "Deleted member".
10.4 What we still hold after deletion. The following is archived, not erased, when an account is deleted: the (now anonymised) account record and its number; your company profile record, which still contains the company name, descriptions, address and contact details you entered, although it is no longer shown to members; your RFQs, quotes, messages, reviews, propositions, introductions and meeting requests; your uploaded documents; your reveal history; saved companies and searches; notifications; and your subscription record with the payment provider's identifiers. We keep these in archived form while they are needed for legal, accounting and security reasons.
10.5 Reports and blocks. Reports you make about other members or their content, and reports made about you or your content, are kept together with a copy of the reported content as it was when the report was made. We keep each report for 2 years after it is resolved and then delete it; this applies even after you delete your account. Blocks are removed when your account is deleted.
10.6 Deleting your account with us does not delete the records Stripe holds about your payments. If you registered through an older shared login, deleting your account here does not delete that separate login.
11. How we protect data
The following measures are present in the product:
- All traffic is encrypted in transit (HTTPS with TLS 1.2 or 1.3, with HSTS).
- Passwords are stored only as salted one-way hashes (bcrypt).
- Sign-in uses a short-lived access token held in the page's memory and a refresh cookie that scripts cannot read; refresh tokens are rotated.
- The email address must be verified before the member area can be used.
- Optional two-factor authentication with an authenticator app (where available for your account); it is mandatory for moderators once the moderator controls are switched on.
- You can view and revoke your signed-in sessions (where available for your account); changing your password signs out existing sessions.
- Rate limits on sign-in, account deletion attempts, billing actions, search, reveals and AI features.
- A content-security policy and related browser security headers restrict what the website can load and where it can send data.
- Uploaded files are private. Uploads use short-lived signed links; staff read evidence and proposition documents only through an authenticated staff-only download; file types are restricted and size is capped.
- Each member's reads and changes are limited to that member's own records on the server; other members are identified by company display name rather than by account identifier or contact details.
- Error-tracking and analytics code (not active — section 8.4) strips tokens, cookies, request contents and query strings, and masks page text and typed input, before anything is sent.
- The mobile app keeps tokens in the device's secure storage and offers an optional biometric app lock and a privacy cover when the app is in the background.
No system is completely secure.
12. Your rights
12.1 Depending on the law that applies to you, you may have the right to: be informed about how your data is used; ask for a copy of your data; ask for inaccurate data to be corrected; ask for your data to be deleted or destroyed; ask us to restrict or stop certain uses; object to uses based on our legitimate interests; receive your data in a portable format; and withdraw consent where a use is based on consent.
12.2 What you can do yourself in the Service:
- see and edit your company profile, products, match preferences, saved searches and saved companies;
- delete documents you uploaded (see section 9 on what is removed);
- cancel your membership;
- delete your account (where available for your account);
- see and revoke your sessions, and switch two-factor authentication on or off (where available);
- switch push notifications on or off in the mobile app or your phone's settings.
12.3 What needs a request to us: a copy or export of your data (there is no self-service export), correction of data you cannot edit yourself (such as your name or email address), deletion where self-service deletion is not available for your account, removal of a message or review you posted (these cannot be edited or deleted in the Service), and any objection or restriction request.
12.4 How to ask. Email legal@infotech-global.co.uk. We may need to confirm your identity before we act on a request. We will reply by email.
12.5 Complaints. You may complain to a data-protection authority.
13. Children
The Service is for business users and is not directed at children. We do not knowingly collect personal data from anyone under 18. If you believe a child has registered, contact us and we will close the account.
14. Other members' use of your data, and your use of theirs
Members receive information about each other through the Service (profiles, quotes, messages, reviews) and receive company records through reveals. Each member is responsible for its own use of that information under the laws that apply to it. See the Terms of Service for the rules on permitted use.
15. Changes to this policy
We may update this policy. We will post the new version on this website with a new "last updated" date and, where a change is material, tell you by email or by a notice in the Service.
16. Contact
InfoTech Global Ltd
128 City Road, London EC1V 2NX, United Kingdom
- Privacy requests: legal@infotech-global.co.uk
- General and support: support@infotech-global.co.uk