This policy explains which personal data Grandify processes when you visit our website, use the Grandify app or order in a store built with Grandify, why we process it, who receives it and what your rights are.
It sets out your rights under Algerian Law No. 18-07 of 10 June 2018 on the protection of natural persons in the processing of personal data.
1Who we are
Grandify is an online platform that lets merchants create online stores, receive their customers’ orders, confirm them and ship them with Algerian delivery companies. In this policy, “Grandify”, “we” and “us” mean the operator of the Grandify platform.
For any question about your data, write to support@grandify-dz.com or use the contact form on our home page.
2Our two roles
Who decides what happens to the data depends on whose data it is:
- Merchants, their team members and the visitors of our website. Grandify decides why and how this data is processed: we are the controller (the person responsible for the processing in the sense of Law 18-07).
- Customers of the stores. When someone orders in a store built with Grandify, the merchant who owns that store decides how the customer’s data is used: the merchant is the controller. Grandify processes this data on the merchant’s behalf and on their instructions, as a processor, only to provide the service to the merchant, under the commitments set out in our terms of use.
If you are a customer of a store, contact the store first: its contact details appear on its pages. If you write to us, we forward your request to the merchant and help them answer it.
3The data we process
We only collect what the service needs. Depending on how you use Grandify:
Visitors of our website
- Browsing: your IP address and your browser’s identification, kept with your session while it lasts and in our server logs (see “How long we keep the data”).
- Contact form and demo requests: your name, e-mail address, phone number (optional for the contact form), message and, for a demo, the time that suits you.
- E-mail capture: the e-mail address you leave so that we contact you.
Merchants and their team members
- Account: name, e-mail address, phone number, language, profile photo (optional), notification and display preferences, the Telegram account you link (optional), and your password, which we store only as a one-way hash that nobody can read.
- Business and billing: business name, phone number, billing e-mail address, legal name, billing address and, when you give them, your tax identification number (NIF) and trade register number (RC), and your logo.
- Stores: store names, their addresses (a subdomain or your own domain), settings, products and images, and the services you connect (delivery company accounts, advertising pixels and their access tokens, Telegram bot and chats).
- Plans and payments: plan, periods, amounts, payment method and reference, the proof of payment you upload, and the references of online payments. We never receive your card number: you type it on Chargily’s payment page.
- Security and use: sessions (IP address, browser, last activity), date of the last sign-in, two-step verification (secret and recovery codes), a log of important actions (for example two-step verification turned on, a setting changed, a store created or archived, and who in our support team opened your account and why) with the IP address, support tickets and their attachments, in-app notifications, and the devices on which you use our mobile app (notification token, device name, system, app version).
- Team: the e-mail addresses of the people you invite and, for each member, their display name and phone number, roles, the stores they can access, working hours and order-taking settings, last activity, and the orders assigned to them and confirmed by them (to share the work and follow the team’s results).
- Free trial: to offer one trial per person, we keep a one-way fingerprint (a keyed hash) of the phone number and of the e-mail address used for the trial, and the IP address at that moment. The number and the address cannot be read back from the fingerprint.
Customers of the stores (processed for the merchants)
- Orders: first and last name, phone numbers, wilaya, commune, address, delivery type (home or office), note, products, quantities, prices, promo code, status and history, the follow-up by the merchant’s team (calls and their outcome, the member assigned, who confirmed it, comments) and the reason for a cancellation.
- Customer record: built from the orders, for each phone number within the merchant’s account: first and last name, other phone number, wilaya, commune and address, number of orders (confirmed, delivered, returned, cancelled) and total of the delivered ones, dates, the merchant’s notes and tags, and whether the merchant blocked the number, with the reason.
- Unfinished order forms: what was typed in an order form that was not sent (name, phone number, wilaya, commune, delivery type, product, quantity, estimated total), with the IP address, the browser identification and the campaign parameters, so that the merchant can call the customer back. When it holds a valid phone number, such a form becomes an order for the merchant to confirm after a time without activity that the merchant sets (20 minutes by default).
- Technical and anti-fraud signals: IP address, browser identification, a random identifier of the device (kept as a hash), the time taken to fill the order form, and where the visit came from (campaign parameters, advertising click identifier, referring page, type of device, the app in which the page was opened).
- Store visits: one record per visit with the hashed device identifier, the first page seen, the campaign parameters and advertising click identifier, the referring page, the type of device, the app in which the page was opened, the version of the page shown when the merchant tests two versions, and the order the visit led to.
4Why we use the data, and on what basis
Law 18-07 allows processing with your consent, or without it when the processing is necessary, among other cases, to perform a contract you are party to or steps you asked for before one, to comply with a legal obligation, or for a legitimate interest that does not override your rights and freedoms. We rely on these grounds as follows:
| Purpose | Basis |
|---|---|
| Creating and running your account and your stores, receiving and managing orders, the mobile app and its notifications | Contract (our terms of use) |
| Billing: plans, payments, receipts, reminders before a period ends | Contract; legal obligations (accounting and tax) |
| Security: sign-in and two-step verification, sessions, action log, limits against abuse, one free trial per person | Legitimate interest in protecting accounts and the service; our legal obligation to secure the data |
| Support: tickets and, when needed to help you or to investigate a problem, access to your account by our authorised support team (each access is limited in time and recorded with its reason and the actions taken; you can ask us for this record) | Contract; legitimate interest in running and securing the service |
| Service e-mails and messages: address verification, password reset, billing and order notifications | Contract |
| Answering the contact form and your e-mails | Your request; your consent |
| Overall statistics to improve the service | Legitimate interest |
We do not sell personal data, we do not build advertising profiles, and we never use the data of a store’s customers for our own purposes: we process it only to provide the service the merchant uses.
In their stores, merchants use their customers’ data to handle and deliver orders, to fight fake orders and, if they turn on advertising pixels, to measure their campaigns. Each merchant is responsible for the basis of the processing they decide and for informing their customers.
5Who receives the data
Within Grandify, team members see the data only as far as their role requires. Outside Grandify, data goes only to the providers below, for the purpose stated. Those marked “if the merchant enables it” receive data only when a merchant turns them on for their store.
| Recipient | Data | Purpose |
|---|---|---|
| DigitalOcean (hosting, servers in Frankfurt, Germany) | All the data the service stores | Hosting the platform, the app and the stores |
| ZeptoMail by Zoho (e-mail delivery) | Name and e-mail address of the recipient, content of the message | Sending the service’s e-mails |
| Chargily Pay (online payment, Algeria) | Amount, business name, plan and payment references; your card details go directly to Chargily | Paying for a plan online by EDAHABIA or CIB card |
| Telegram | Alerts to our team (for example a payment to review, a new support ticket or a plan change: the merchant’s name, the business or store name, the amount, the ticket’s subject); your own notifications if you link your Telegram account; if the merchant enables it, new-order messages to the store’s chats (customer’s name, wilaya and commune, phone number and note when they are visible, products, total) | Notifications |
| Google Firebase Cloud Messaging | If the merchant enables it (mobile app): new-order notifications to the merchant’s phones (customer’s name, wilaya, phone number when it is visible, products, total) | Push notifications |
| Google Fonts | Your IP address and browser identification when a page loads its fonts | Displaying our pages and the stores |
| Meta (Facebook, Instagram), TikTok, Snapchat, Google (Analytics, Ads, Tag Manager) | If the merchant enables it: their tag on the store’s pages collects browsing events; for Meta’s Conversions API our server also sends the order events, for every order including those whose contact details are hidden from the merchant, with the phone number, names, commune, wilaya and country in hashed form (SHA-256, so that Meta can match them with its users’ accounts: a hash is not anonymous), the IP address, the browser identification, Meta’s cookies, the products and the amount | Measuring the merchant’s advertising |
| Delivery companies (for example the carriers using the ECOTRACK platform) | If the merchant enables it: name, phone number, address, wilaya, commune, products and amount to collect of the orders the merchant ships | Delivering the orders |
| GrandiFlow agents (Grandify’s order confirmation service) | If the merchant enables it: the orders to confirm, with the customer’s name, phone numbers, address, wilaya, commune, products, total and note | Calling the customer to confirm the order |
WhatsApp receives nothing from us. Links that open WhatsApp (our support number, a store’s WhatsApp button, calling a customer from the app) only open the WhatsApp application, whose own terms then apply.
We also disclose data when Algerian law requires it, at the request of a judicial or other competent authority.
6Where the data is stored
Our servers are rented from DigitalOcean in its Frankfurt data centre, in Germany (European Union). Your data is therefore stored outside Algeria. We chose this host for the reliability and the security of its infrastructure (redundant power and network, controlled physical access) and so that the platform and the stores stay fast and available.
Some of the providers listed above (e-mail delivery, notifications, fonts, and the advertising tools a merchant enables) also process data outside Algeria. We send them only what their task needs.
7How long we keep the data
- Account, business and stores: as long as your account exists. When you ask us to close it, we take your stores offline and, within 30 days, delete the data or make it anonymous, except the billing records and the free-trial fingerprints below.
- Billing records (payments, receipts, proofs): as long as accounting and tax rules require.
- A store’s orders, customer records, unfinished forms and GrandiFlow orders: for the merchant, as long as their account exists, then like the account’s data.
- Archived store: taken offline, its data stays with the account so that the store can be restored, until the account is closed.
- Store visit records: 180 days.
- Sessions: our website and the app forget a session after 2 hours without activity; “Remember me” keeps you signed in to the app for 30 days; a store’s session ends after 12 hours without activity.
- Files uploaded but not used in a form: deleted within 3 hours.
- Action log and support tickets: as long as the account exists. When it is closed, the tickets are deleted and the log keeps its entries without the name, e-mail address or IP address.
- Free-trial fingerprints: kept so that the rule of one trial per person keeps applying, including after an account is closed; the IP address recorded with them is deleted when the account is closed.
- Contact form messages and e-mail addresses left on our website: kept until you ask us to delete them.
- Server logs: our web server’s access logs (IP address, page requested, date and time, browser identification) are kept 14 days; the application’s logs (errors and important events, which can contain an e-mail address or an IP address) at most 30 days.
- Backups: the database is copied every night (the 14 most recent copies are kept) and before each update of the service (the 5 most recent), and the uploaded files every week (the 4 most recent). Data deleted from the service disappears from the backups as they are replaced.
8How we protect the data
- Encrypted connections (HTTPS) on our website, the app and the stores.
- Passwords stored only as a one-way hash.
- Optional two-step verification with an authenticator app, and recovery codes.
- Secrets encrypted in our database: the two-step verification secret, the online payment keys, and the Conversions API access token of a pixel you connect.
- Proofs of payment for your account’s plan, uploaded in the app, kept in private storage: shown only to you, to the team members you give access to billing, and to the authorised members of our team.
- Each business’s data kept apart from the others; roles and permissions within your team; access by our team limited by role. When our support team opens your account, the access is limited in time and recorded with its reason and the actions taken.
- Limits on sign-in attempts and on forms against abuse.
No system is perfectly secure. If an incident affects your data, we take the necessary measures and inform you when it is likely to affect you; for the data of a store’s customers, we inform the merchant concerned.
9Your rights
Law 18-07 gives you the following rights:
- Information: to know who processes your data, why, and who receives it; this policy tells you.
- Access: to obtain confirmation that we process data about you, and a copy of it.
- Rectification: to have inaccurate or incomplete data corrected, updated, locked or erased.
- Objection: to object, for legitimate reasons, to the processing of your data, and to object without giving any reason to its use for marketing.
You can correct most of your account’s data yourself in the app’s settings. For anything else, write to support@grandify-dz.com from your account’s e-mail address, or tell us how to check that the request comes from you. We answer free of charge, within the time limits set by the law.
You can also ask us to close your account: its data is then deleted or made anonymous within 30 days, as described above and in our terms of use.
Customers of a store send their requests to that store; we help merchants answer them.
If you think your rights are not respected, you can lodge a complaint with the National Authority for the Protection of Personal Data (ANPDP).
11Children
Grandify is a service for merchants who have reached the age of majority. We do not knowingly collect data about children. If you think a child has given us personal data, contact us and we will delete it.
12Changes to this policy
We may update this policy when the service or the law changes. The date at the top shows the current version. If a change is important, we tell you in the app or by e-mail before it applies.
13Contact
Questions, requests about your rights or complaints: support@grandify-dz.com, or the contact form on our home page.