qeda-logo
Legal

Privacy Policy

This policy explains what personal data Qeda collects when you visit qeda.io, create an account, deploy on Qeda Cloud or top up your wallet with Mobile Money, why we use it, and the choices you have.

Last updated [DATE] · Applies to qeda.io, docs.qeda.io, dashboard.qeda.io · Version 1.0

terminal — qeda privacy
$ qeda privacy --summary
› Loading policy v1.0...
✓ We never sell your data
✓ We don't look inside your apps, databases or buckets
✓ Account data is hosted in France (EU): OVHcloud
✓ We never see your card number or Mobile Money PIN
✓ Export or delete your account at any time
⬡ GDPR & UAE PDPL apply

Privacy at a glance

We never sell your data

We use your data to run Qeda Cloud and bill you. We do not sell it or rent it to advertisers.

Who we share it with

Mobile Money without your PIN

Payments go through DPO Pay, a licensed provider. We receive a transaction reference, never your PIN or card number.

How payments work

Your apps stay yours

Code, databases and files you deploy belong to you. We process them only to host and run your services.

Data you deploy

Analytics only if you agree

Google Analytics runs on qeda.io only after you accept analytics cookies. You can change your mind at any time.

Cookies

You know where it lives

Your services run in the region you pick. Account data is stored in France, in Roubaix and Gravelines.

Storage and transfers

We answer within 30 days

Ask to see, correct, export or delete your data. We reply within 30 days, sooner where your local law requires it.

Your rights
01

Who we are

Qeda is a cloud platform that lets developers and companies across Africa deploy applications, databases and AI models, and pay for them in their local currency. The service is operated by [LEGAL ENTITY NAME], a [LEGAL FORM] registered under number [REGISTRATION NUMBER] with [REGISTERING AUTHORITY, e.g. Dubai DET or a free zone authority], whose postal address is P.O Box 44133, 44133 Dubai, United Arab Emirates. In this policy, "Qeda", "we" and "us" refer to that company.

For the personal data described here, Qeda is the controller: we decide why and how it is used. You can reach our privacy team at privacy@qeda.io for any question about your data.

02

What this policy covers

It covers the websites qeda.io and docs.qeda.io, the Qeda dashboard at dashboard.qeda.io, the Qeda command line and API, the beta programme, our community spaces and the emails we send. It applies to visitors, people who sign up, account owners and members of their workspaces.

It does not cover the applications our customers build and run on Qeda. If you use an app hosted on Qeda, that app's owner decides how your data is used, and their own privacy policy applies. Our role for that data is explained in Data you deploy on Qeda.

03

Information we collect

What you give us

When you create an account or join the beta we ask for your name, email address, country and a password, or we receive your name, email and public profile from GitHub or GitLab if you sign in with them. If you add a company we record its name, billing address and tax number. When you contact us, by email, through the dashboard or on WhatsApp, we keep your messages, any files you attach and, on WhatsApp, your phone number.

What we collect when you use Qeda

To run your services we record technical data such as the projects, services and regions you create, deployment and build logs, resource usage (CPU, memory, storage, bandwidth), IP addresses, browser and device type, and the date and time of each action in the dashboard or API. We keep security logs of sign-ins and changes to API keys.

What we receive from others

Payment providers tell us whether a top-up or payment succeeded, with its amount, currency, reference and the phone number or wallet used. Git providers send us repository metadata and commit events for the repositories you connect. If a teammate invites you to a workspace, we receive your email address from them.

Website visits

On qeda.io we measure visits with Google Analytics, only if you accept analytics cookies, to understand which pages are useful. The cookies involved are listed in our Cookie Policy.

04

How we use it and why

We only use personal data when we have a reason the law accepts. The table below lists each purpose with that reason. Where we rely on your consent, you can withdraw it at any time from your account settings or by writing to us, without affecting what was done before.

PurposeData usedLegal basis
Create and secure your accountIdentity, sign-in and security logsPerformance of our contract with you
Host, build and scale your servicesTechnical and usage data, deployed contentPerformance of our contract with you
Bill you, manage your wallet and Auto-StopBilling, payment and usage dataContract, and legal obligations for invoices and tax
Answer support requestsMessages, account and technical dataContract, and our legitimate interest in helping you
Prevent fraud and abuseIP addresses, logs, payment signalsOur legitimate interest in keeping the platform safe, and legal obligations
Product emails (incidents, billing, security)Email addressPerformance of our contract with you
Newsletter and beta announcementsEmail address, preferencesYour consent, which you can withdraw in one click
Improve the website and productAggregated usage and analytics dataYour consent for analytics cookies, legitimate interest for aggregated statistics

We do not make decisions about you based only on automated processing that have legal or similarly significant effects. Automatic suspension when your wallet reaches zero (Safety Auto-Stop) is a billing rule you agree to in our Terms, and you can restart your services as soon as you top up.

05

Data you deploy on Qeda

The code, databases, files, environment variables and logs of the applications you deploy may contain personal data about your own users. For that content you are the controller and Qeda acts as your processor. We process it only on your instructions, to host, back up and run your services, and we do not look at it except to provide support you ask for, to keep the platform secure, or when the law requires it.

Our Data Processing Agreement sets out these commitments, including security measures, sub-processors and assistance with your own users' requests. It is part of our Terms and available on request at privacy@qeda.io. If one of your users contacts us directly, we will pass the request on to you.

06

AI models and prompts

Qeda AI Hub is not available yet. When it launches, a dedicated page will explain how prompts, files and model outputs are handled, and we will update this policy before any of that data is processed.

07

Payments and your wallet

You can top up your Qeda wallet with Mobile Money (such as Orange Money, MTN MoMo, Moov Money or Wave) or with a bank card. Payments are handled by DPO Pay by Network, a licensed payment provider. You enter your PIN or card number on DPO Pay's secure pages, and we never see or store them.

From the provider we receive the amount, currency, date, transaction reference, status and the phone number or address used. We keep this with your invoices to meet accounting and tax rules.

08

Who we share it with

We do not sell your personal data. We share it only with the service providers that help us run Qeda, under contracts that limit their use to our instructions, and with others in the narrow cases described after the table.

ProviderPurposeLocation
OVHcloudCloud infrastructure hosting; local partners in Africa to be added here as they come onlineFrance (Roubaix and Gravelines datacenters)
DPO Pay by NetworkMobile Money and card paymentsEmirates NBD Building, Levels 101–201, First Al Khail Street, Al Barsha 2, Dubai, UAE (P.O. Box 4487)
WhatsApp (Meta), Qeda Ops (in-house)Customer supportWhatsApp: Meta servers · Qeda Ops: our own infrastructure
Google AnalyticsWebsite audience measurementUnited States and other Google locations
Google Workspace, OVHcloudEmailGoogle: United States and other Google locations · OVHcloud: France

We may also share data with our professional advisers, with authorities when a valid legal request obliges us to (we tell you first unless the law forbids it), to protect the rights and safety of our users or of Qeda, and with a buyer or successor if Qeda is involved in a merger or acquisition, in which case this policy continues to apply to your data.

09

Storage and transfers

Your applications run in the region you choose when you deploy. Account, billing and support data is stored in France, in OVHcloud datacenters in Roubaix and Gravelines, within the European Union. Some providers listed above, such as Google and Meta, may process data in the United States. Because Qeda is based in the United Arab Emirates and serves users across Africa and beyond, your data may be transferred to a country other than your own.

Transfers outside your country

When we transfer data, we use the safeguards your law requires: transfers to countries recognised as offering adequate protection, standard contractual clauses approved by the European Commission or by the relevant African authority, your consent where the law allows it, or the transfer being needed to provide the service you asked for. You can ask us for a copy of the safeguards that apply to you.

10

How long we keep it

We keep personal data only as long as we need it for the purpose it was collected for, and never more than 24 months after your last activity, then delete or anonymise it. The only exception is invoices and payment records, which tax and accounting law requires us to keep longer.

DataRetention
Account dataWhile your account is open, then 30 days after you close it. Accounts with no activity for 24 months are deleted after notice by email.
Deployed services after wallet reaches zeroKept stopped for 7 days, then deleted with their data after notice by email.
Invoices and payment recordsThe period required by tax and accounting law, currently 5 years in the United Arab Emirates.
Build, deployment and access logs90 days.
Security logs12 months.
Support conversations24 months after the last message.
Website analytics14 months.
Newsletter subscriptionUntil you unsubscribe.
BackupsDeleted on a rolling basis within 35 days.
11

How we protect it

Isolated workloadsEach customer's workloads run in isolated sandboxes with separate networks.
Encrypted in transitData is encrypted in transit with TLS. [Describe encryption at rest for databases, storage and backups.]
Controlled accessAccess to production systems is limited to staff who need it, protected by multi-factor authentication and logged.
72-hour breach noticeIf a breach affects your personal data, we tell you and the competent authorities within the time the law sets.

No system is perfectly secure. If a breach affects your personal data, we will tell you and the competent authorities within the time the law sets, which is 72 hours under the GDPR and under several African laws. You can help by using a strong password, turning on two-factor authentication and keeping your API keys secret.

12

Your rights

Wherever you live, you can ask us to show you the personal data we hold about you, correct it, delete it, export it in a common format, limit how we use it, or stop using it for marketing. You can also object to uses based on our legitimate interest and withdraw any consent you gave.

AccessCorrectionDeletionExport (portability)RestrictionObjectionWithdraw consent

Most of this is available in the dashboard under [Settings › Privacy]. Otherwise, write to privacy@qeda.io. We may ask you to prove your identity before acting. We answer within 30 days, sooner where your local law requires it, and we do not charge for reasonable requests.

Making a complaint

If you are not satisfied with our answer, you can complain to the data protection authority of your country. The main ones for our users are listed below. If you live in a country not listed here, you keep the rights your own law gives you, and we will handle your request in the same way.

United Arab EmiratesPDPL, Federal Decree-Law No. 45 of 2021 · UAE Data Office
European Union and EEAGDPR · Your national authority, such as the CNIL in France
NigeriaNigeria Data Protection Act 2023 · NDPC
KenyaData Protection Act 2019 · ODPC
SenegalLaw No. 2008-12 · CDP
Côte d'IvoireLaw No. 2013-450 · ARTCI
CameroonLaw No. 2024/017 of 23 December 2024 · The authority created by that law
BeninDigital Code, Law No. 2017-20 · APDP
GhanaData Protection Act 2012 (Act 843) · Data Protection Commission
South AfricaPOPIA · Information Regulator
13

Cookies

We use cookies that are needed to keep you signed in and to secure the dashboard. With your consent, we also use analytics cookies on qeda.io. You can change your choice at any time from the cookie banner link in the footer. Details are in our Cookie Policy.

14

Children

Qeda is a service for professionals and is not meant for anyone under 18. We do not knowingly collect data from children. If you think a child has given us personal data, contact us and we will delete it.

15

Changes to this policy

We update this policy when our services or the law change. The date at the top shows the latest version. If a change affects how we use your data in a significant way, we will tell you by email or in the dashboard at least 30 days before it takes effect.

v1.0[DATE]First published version
16

Contact us

For any question about this policy or your data, write to us. We read every message.

Questions about your data?

Write to privacy@qeda.io, or by post to [LEGAL ENTITY NAME], P.O Box 44133, 44133 Dubai, United Arab Emirates. A real person on our team will answer.

Contact our privacy team