Privacy Policy

OKEA Management (the “Platform”) is the internal operations platform of OKEA (“OKEA”, “we”, “us”), an e-commerce operator selling in cash-on-delivery markets in Africa and the Gulf. Our team uses the Platform to research and test products, manage creatives, sourcing and stock, record daily sales performance, follow finances, and read and manage OKEA’s own Facebook and Instagram advertising through the Meta Marketing API.

Accounts are created only by invitation from a OKEA administrator; there is no public sign-up. The people whose personal data the Platform processes are therefore mainly OKEA’s team members and invited collaborators (administrators, media buyers, video editors and sourcing specialists), people who apply to join us through the public application form, and the business contacts our team records (for example suppliers and transport companies).

The Platform’s Meta integration runs through OKEA’s Meta developer app (App ID 1218111533011708), connected to OKEA’s own Meta Business portfolio. This policy does not cover Meta’s own services, which are governed by Meta’s Privacy Policy, nor OKEA’s online stores.

Account and profile

• Name, e-mail address, role in the team, and — only if you or an administrator add them — job title, phone number, location and profile photo.
• Your password is never stored: we keep only a salted scrypt hash of it. Invitation links and password-reset links are stored as hashes too.
• The markets (countries) and media buyers an administrator assigns to you, and your account status (invited, active, suspended or archived).

Sign-in and security records

• For each signed-in session: a hash of the session token, when it was created, last used and expires, the IP address and the browser’s user-agent string.
• Your last sign-in time, and an audit log of important actions (who did what and when, with the values that changed) — for example campaign launches and edits, stock corrections and team changes.

Work content you create in the Platform

• Products and their markets, prices, costs, links and notes; creative files (videos and images) and their versions; briefs, revision requests, tasks and notes.
• Team chat messages, voice notes and attachments, and in-app notifications.
• Daily performance entries (aggregated counts of orders, confirmations and deliveries, revenue and ad spend), stock and sourcing records, including the business contact details of suppliers and transport companies (such as a name, phone number and location).
• For team members who are paid by commission or by output: the compensation agreements and earnings records an administrator keeps for them.
• OKEA’s internal finance records, which only the super administrator can open.

Job applications

If you apply through the public “Join” form: your name, e-mail address, the role you are interested in, your location, your message, and, if you attach them, your CV and a photo.

What we do not collect

• The Platform does not store the names, phone numbers or addresses of the customers of OKEA’s stores: sales are recorded as daily totals per product and market.
• We do not use Facebook Login, and we do not collect Facebook or Instagram users’ profiles, friend lists, messages or other personal information from Meta (see the next section).
• We do not collect payment card details. Advertising is paid directly to Meta (see our Terms of Service).

How the connection is made

A OKEA super administrator connects the Platform to Meta by entering an access token generated for a system user of OKEA’s Meta Business portfolio (Settings → Integrations). An individual ad account can optionally be given its own token, by the super administrator or by the media buyer assigned to that account. No one signs in with a personal Facebook account, and the Platform can only reach the ad accounts, Pages and pixels that OKEA’s business has assigned to that system user.

What the Platform reads from Meta

• Ad accounts: ID, name, currency, status, time zone and, where available, the name of the business that owns the account.
• Campaigns, ad sets and ads: IDs, names, statuses, objectives, optimisation goals and budgets, and a thumbnail link of each ad.
• Performance metrics per day: spend, impressions, reach, clicks, link clicks, landing-page views, results, video plays and watch milestones, add-to-carts, checkouts initiated and purchase value. These are aggregated statistics about ads, not information about identifiable people.
• For publishing: the Facebook Pages an ad account can advertise with (ID and name), their linked Instagram business accounts (ID and username), and the account’s Meta pixels (ID, name and the time they last received an event).

Figures are refreshed in the background (about every 10 minutes, and every few minutes for the current day), and up to two years of daily history are loaded so the team can compare periods.

What the Platform sends to Meta — only when a person asks

• When an authorised user presses Publish in “Create campaign”, the Platform creates the campaign(s), ad sets, ad creatives and ads described on the review screen in the chosen ad account, and uploads the selected creative videos or images. Placements are limited to Facebook and Instagram.
• When an authorised user edits a campaign, ad set or ad from the Platform, only the fields they changed (such as a name, budget or on/off status) are sent.
• If a launch fails midway, the Platform pauses the objects it had already created in that launch, so nothing half-built can spend money; the user can then retry.
• Nothing is created, changed or switched on in Meta without a person’s explicit action, and every launch and edit is written to the audit log.

Meta permissions and why we use them

Who can see it

Administrators can see every connected ad account. A media buyer only sees, and can only publish in, the ad accounts an administrator assigned to them. Video editors and sourcing specialists do not have access to Ads Manager.

We use data received from Meta only to run OKEA’s own advertising inside the Platform. We do not sell it, use it to profile individuals, or share it with anyone outside the providers listed below, and we handle it in line with Meta’s Platform Terms and Developer Policies.

• To create and secure your account, sign you in, and give you the access that matches your role and assigned markets.
• To run OKEA’s operations: product research and testing, creatives, sourcing and stock, daily performance, profit calculations in US dollars, team tasks and chat.
• To show advertising results and, when a user asks, to publish and edit OKEA’s campaigns in Meta.
• To write ad-copy suggestions with Claude, only when a user chooses that option (see “Service providers”).
• To calculate the earnings of team members paid by commission or by output, when an administrator has set this up.
• To send invitations and password-reset links, by e-mail when e-mail delivery is configured, or by a link an administrator shares with you.
• To review job applications.
• To keep the Platform secure, investigate misuse, keep an audit trail, and meet legal obligations.

• Meta access tokens, optional Meta app secrets and other integration keys (such as the Claude API key) are encrypted in our database with AES-256-GCM, using a key derived from a secret that exists only in the server’s configuration.
• They are decrypted only on the server, at the moment a request is made to the provider. They are never sent back to a browser: the Platform shows at most the first and last four characters.
• Only the super administrator can add, replace or disconnect the business-wide tokens; an ad account’s own token can also be managed by the media buyer assigned to that account. Disconnecting deletes the stored token immediately.
• Tokens are not written to the audit log, and we never ask anyone for their Facebook password.

We do not sell or rent personal data. We share data only with the providers needed to run the Platform:

• Meta Platforms — receives what is needed to create and manage OKEA’s ads when a user publishes or edits them: creative files, ad copy, budgets, schedules, target countries, and the chosen Page, Instagram account and pixel.
• Hetzner Online GmbH — hosts the server that runs the Platform, its database and its stored files.
• Anthropic (Claude API) — only when a user chooses “Claude writes it” while creating a campaign: the product name, market, language, price, product-page link, the user’s notes, and the public text of that product page are sent so Claude can suggest ad copy. If the user writes the copy themselves, nothing is sent to Anthropic.
• An e-mail delivery (SMTP) provider — only if e-mail sending is configured, to deliver invitation and password-reset e-mails (name, e-mail address and the link).

To prepare ad copy, the Platform’s server may also fetch the public product page a user entered; it only fetches public internet addresses.

We may also disclose information if required by law or by a valid request from a competent authority, or to protect the rights, property or safety of OKEA, our team or others.

• One strictly necessary cookie, okea_session, keeps you signed in. It is HttpOnly, sent only over HTTPS, limited to our own site, and expires after 30 days or when you sign out.
• Your browser’s local storage remembers your light/dark theme choice, and session storage remembers that the welcome animation was shown.
• If you install the Platform as an app, a service worker keeps a copy of the Platform’s own static files (scripts, styles and an offline page) so it opens quickly. It never stores pages, business data or uploaded files.

The Platform does not use analytics, advertising or social-media tracking cookies, and does not load third-party trackers. Its fonts are served from our own server.

• Business records (products, creatives, performance, stock, sourcing, finance, chat and the audit log) are kept for as long as OKEA uses the Platform for its operations. There is currently no fixed period after which they are automatically deleted.
• Team accounts: when an administrator removes someone from the team, an account with no work history is erased; an account with history is archived, so that the products, creatives and decisions it is linked to keep their author. Archived accounts can no longer sign in and all their sessions are ended.
• Sign-in records: sessions expire after 30 days; password-reset links after 20 minutes; invitation links after 7 days.
• Meta data: cached advertising data is kept as part of OKEA’s advertising history. Disconnecting Meta stops all further access immediately; data already copied stays until it is deleted on request.
• Job applications are kept until they are deleted on request.
• Backups: the database is backed up daily and these backups are kept for about 14 days; a backup is also taken before each update of the Platform, and the most recent ten are kept. Deleted data can remain in backups until they are replaced.

To ask us to delete your data, see User Data Deletion.

• All traffic is encrypted with HTTPS (TLS 1.2 or 1.3).
• Passwords are hashed with scrypt; session, invitation and reset tokens are stored only as hashes.
• Role-based access control is enforced on the server for every page and action; media buyers are limited to their own products, markets and ad accounts.
• Uploaded files are served only to signed-in users; applicants’ CVs and finance evidence only to the super administrator.
• Sign-in attempts are rate-limited, and suspending or removing a member ends their sessions immediately.
• Integration secrets are encrypted at rest (see above); important actions are recorded in an audit log; the database is backed up daily.
• Automated deployments run through a restricted account that cannot obtain administrator access to the server.

No system is perfectly secure. If we become aware of a breach affecting your personal data, we will inform you and the relevant authorities where the law requires it.

Depending on the law that applies to you, you may have the right to:

• access the personal data we hold about you and receive a copy of it;
• have inaccurate data corrected — you can edit your own name, job title, phone, location and photo at any time in your profile;
• have your data deleted, or its use restricted, or object to how it is used;
• withdraw a consent you gave, and complain to your data-protection authority.

To exercise these rights, e-mail ayoubbress12@gmail.com from the address registered on your account. We will verify your identity before acting and reply within the time the applicable law requires. Deletion requests follow the steps on our User Data Deletion page.

The Platform is hosted by Hetzner Online GmbH. Meta and Anthropic may process the data they receive in other countries, including the United States, under their own terms and safeguards. Our team members work from several countries and access the Platform from where they are.

The Platform is a professional tool for adults. It is not intended for anyone under 18, and we do not knowingly collect children’s personal data.

We may update this policy when the Platform or the law changes. We will change the “Last updated” date above and, for important changes, tell our team inside the Platform.

For any question about this policy or your personal data, write to OKEA at ayoubbress12@gmail.com.