Privacy policy

1Who we are and how to reach us

1.1 RetailPower ("we"), an Egyptian company.
1.2 Privacy contact: [email protected]. WhatsApp: the username @RetailPower.

2Two roles: controller and processor

2.1 We are the controller of the data about the Owner and the Shop's account: who signs up, how to reach them, what they pay, how they sign in, and what they send to support. We decide why and how that data is used.
2.2 We are the processor for the data a Shop enters about its own Staff Users, employees, customers and suppliers. The Shop is the controller of that data. We process it only on the Shop's instructions, which are the Terms of Service and the Shop's use of the settings, to provide the Service.
2.3 A Staff User, employee or customer of a Shop who wants to use their rights should first ask the Shop, which decides what happens to that data. We will help the Shop do so (clause 10.5).

3What we collect

3.1 About the Owner and the Shop (we are the controller)

• Name given at sign-up and mobile phone number. To identify the Owner, send sign-in codes and give support. The phone number is verified by a code.
• Google sign-in details: your name, email address and the identifier Google gives us. To let you sign in with Google. We ask only for basic profile and email. We do not ask for your Gmail, contacts or Drive.
• Shop name, store name, type of business, plan. To run the Shop's account and billing.
• Payment records: amounts, dates, invoice numbers, reference and status. To bill you and prove what was paid. The Gateway holds the card number. We do not see it.
• Records of acceptance: which version of each policy you accepted, the time, a hash of your network address. To prove what you agreed. A hash is a scrambled value, not your address.
• Sign-in and security records: time, network address, browser and device description, failed attempts. To protect accounts and investigate abuse.
• Messages you send to support, including through the contact form. To answer you.

3.2 About the Shop's staff, employees, customers and suppliers (the Shop is the controller)

The Shop chooses what to enter. The Service can hold:

• Staff Users and employees: name, username, a password stored only as a hash (we cannot read it), role, phone, email, hire date, salary and commission, sales target, national ID number, address, attendance, leave, payroll, and any papers the Shop uploads (such as scans of identity or contracts).
• Customers: name, phone, email, address, birth date, anniversary date, loyalty tier and points, purchases and returns, and records of whether the customer agreed to receive marketing.
• Suppliers: business name, contact name, phone, email, address, purchases.
• The Shop's business records: products, stock, sales, payments by method, shifts, day-end closes, alterations and the audit trail of who changed what.

3.3 We advise Shops to enter only what they need. For example, enter an employee's national ID number only where the law or the Shop's own duties require it.
3.4 We do not ask for card numbers from the Shop's customers. The till records the payment method used, not card details.
3.5 The Service is not meant for children. A Shop must not enter a child's data except where the law allows and a guardian has agreed.

3.6 Technical data

3.6.1 Our servers keep technical logs (request time, address, error references) to keep the Service secure and working.
3.6.2 Cookies and browser storage: see clause 12.

4What we do not do

4.1 We do not sell personal data. We do not share it for advertising. We do not build advertising profiles.
4.2 We do not send Shop Data to AI services.
4.3 We do not use cookies or tools that track you across other sites.

5Why we use the data, and on what basis

5.1 Egyptian law lets us process personal data with the person's consent, or on other grounds the law lists, such as: it is needed to carry out a contract with the person, to meet a legal duty, or to protect our legitimate rights where that does not override the person's fundamental rights and freedoms. We rely on:

• Create and run the Shop's account; sign-in; the Service itself: performing the contract.
• Take payments, issue invoices, keep tax records: performing the contract; our legal duties.
• Keep the Service and accounts secure; stop abuse: our legitimate rights, where they do not override yours.
• Send service messages: sign-in codes, billing reminders, notices of changes, incident notices: performing the contract.
• Support: performing the contract.
• Our own marketing to Owners (for example news and offers): your consent only. You can withdraw it at any time.

5.2 We do not use Shop Data for our own purposes, and we do not use it to train any model.

6Who receives the data

6.1 Our own staff, only as needed for their work.
6.2 Providers that help us run the Service (sub-processors), by category:

• Server hosting and database: Contabo, in Germany. It holds all data kept in the Service.
• Network protection and encrypted connections: Cloudflare. Web traffic passes through it, including network addresses. It works worldwide.
• Backup storage: Cloudflare R2. It holds encrypted copies of the databases, outside Egypt.
• Card payments: Paymob, once paid plans open. It receives the amount, the invoice reference, the Owner's name and contact details, and the card details you type on its page. It is a controller of card data in its own right.
• Sign-in codes by WhatsApp or text message: the messaging service we use to send the code. It receives the Owner's phone number and the message.
• Sign in with Google: Google. It receives the fact that you are signing in, and gives us the details in 3.1.
• Fonts and charts: Google Fonts and jsDelivr. They see your network address and browser description when a page loads a font or the chart library from them.

6.3 We bind each provider to protect the data, to use it only for the service it gives us, and not to sell it. We will update this list before adding a new category of provider, and will tell the Owner of a material change.
6.4 The authorities. We disclose data when a competent Egyptian authority or court lawfully orders it, and we tell the Shop where the law allows.
6.5 A sale of the business. If the business is sold or merged, the data moves to the successor under these same protections, and we will tell Owners.

7Where the data is kept, and transfer outside Egypt

7.1 The Service's servers are outside Egypt: in Germany, in the European Union. Some providers in clause 6.2 may handle data in other countries as well.
7.2 Egyptian law restricts sending personal data abroad. It allows it only where the receiving country protects the data at least as well as Egypt does, and generally requires a licence or permit from the Personal Data Protection Centre and, unless an exception applies, the consent of the person.
7.3 Our position today: our licence application to the Personal Data Protection Centre is being prepared.
7.4 A Shop that enters its Staff Users' and customers' data into the Service is the controller of that data. It should make sure it has any consent the law requires for that data to be held on servers abroad. We provide the Service on the basis that it has done so.
7.5 We protect the data as described in clause 9, wherever it is kept.

8How long we keep data

• Owner and Shop account details: while the Shop exists, and for 90 days after it closes.
• Shop Data (staff, customers, sales and the rest): while the Shop exists, including on Free. A downgrade to Free does not delete it.
• After a Shop is closed: 90 days, then deleted from live systems.
• Backups: backups are kept for 30 days and then expire.
• Invoices and payment records: the period the law requires.
• Records of acceptance of our policies: while the account exists, and afterwards for as long as we need them as proof.

8.1 A Shop that sends marketing messages must keep proof of its customers' consent for the period the law sets. Keep a copy of your consent records before closing the Shop.

9How we protect the data

9.1 What is in place now, on the software as built:

• Passwords are stored only as salted hashes (PBKDF2-HMAC-SHA256, 600,000 rounds). We cannot read them.
• Owner sign-in sessions use a random token stored on our side only as a hash. A session ends after 24 hours, and after 15 minutes without use. Owner sign-in cookies are marked secure, HttpOnly and SameSite.
• Roles and permissions are checked on the server, not only hidden in the page. A product's cost price is shown only to the Owner and Admin roles.
• Sensitive actions in the owner area ask the person to verify again.
• An audit trail records important changes: who, what and when.
• Browser protections: content-security policy, protection against framing, and protection against content-type guessing.
• Encrypted connections (HTTPS) on the website, with Cloudflare in front.
• Backups are encrypted.

9.2 What we do not claim. We have no security certification of our own. No system is perfectly secure, and we cannot guarantee that data will never be exposed.
9.3 You help by keeping passwords and phones safe, giving each Staff User only the role they need, and signing out of shared computers.

10Your rights

10.1 Under Egyptian law a person may ask to: know and obtain their personal data; withdraw consent; correct, edit, update or delete it; limit the use to a purpose; object to processing that contradicts their fundamental rights and freedoms; and be told of a breach affecting it.
10.2 Owners: write to [email protected] from your registered contact details. We answer within six working days. We do not charge for this.
10.3 Staff Users, employees and customers of a Shop: ask the Shop first; it is the controller. If you write to us, we will pass your request to the Shop and tell you we did so, unless the law stops us.
10.4 To protect people, we may ask you to prove who you are before we act.
10.5 When a Shop asks for our help with a request (for example to find or delete one person's data), we help promptly, so that the Shop can answer within the law's six working days.
10.6 You may complain to the Personal Data Protection Centre, and you may go to court.

11If something goes wrong (data breach)

11.1 For data we control (clause 3.1): we notify the Personal Data Protection Centre within 72 hours of the breach, and we notify the people affected within three days after that, saying what happened and what to do.
11.2 For data a Shop controls (clause 3.2): we tell the Shop without undue delay after becoming aware, with what we know: what happened, which data and how many records, the likely consequences and what we are doing. The Shop, as controller, tells the people affected and the Centre where the law requires, and we help.
11.3 We keep a record of every breach and what we did.

12Cookies and browser storage

12.1 We use only what is needed to run the Service and remember your choices. We use no analytics, advertising or tracking cookies.

• rp_owner cookie (owner area): keeps the Owner signed in, for up to 24 hours (it ends after 15 minutes idle).
• rp_owner_device cookie (owner area): recognises a device the Owner has verified, for 30 days.
• rp_owner_flow and rp_owner_google cookies (owner sign-in): carry the steps of sign-in and Google sign-in, for 10 minutes.
• rp_lang cookie (public pages): remembers the language you chose, for one year.
• Browser storage: the sign-in token for Staff Users, and your language, theme, font size, the store name you typed, last activity time and till screen state. It lasts until sign-out, expiry, or until you clear it.

12.2 Pages load fonts from Google Fonts and, on the reports pages, a chart library from jsDelivr. When they do, those companies see your network address and browser description.
12.3 You can block or delete cookies and storage in your browser. The Service will then not keep you signed in.

13Marketing by Shops

13.1 A Shop that sends offers to customers by WhatsApp, text or email must have each customer's consent, say who is sending, say it is marketing, and let the customer opt out easily. The Service includes a register where a Shop can record consent. The Shop is responsible for its messages. We do not send marketing to a Shop's customers on our own account.

14Changes to this policy

14.1 We give the Owner at least fourteen days' notice of a material change, with a short summary. The Owner is asked to accept the new version at the next sign-in. A published version is never edited. A correction is a new version.

15Contact and complaints

15.1 Write to [email protected] or on WhatsApp to the username @RetailPower. If we do not resolve a concern, you can complain to the Personal Data Protection Centre.