Privacy Policy
This policy explains how Clawdya SARL (“Clawdya”, “we”) handles personal data when you visit clawdya.com, fill in one of our forms, or use Clawdya Flow: our web application, mobile app, point-of-sale (“Caisse”), Copilot assistant, API and MCP server, and the landing pages merchants publish with it.
It is written to comply with Algerian Law No. 18-07 of 10 June 2018 on the protection of natural persons in the processing of personal data and, where it applies, with the EU General Data Protection Regulation (GDPR). It also states how we handle data we receive from Meta, TikTok, Google and the other platforms you connect.
1. Who we are
Clawdya SARL, a limited liability company registered in Algeria under commercial register (RC) no. 16/00-1055215 B 26, with its registered office at Centre d’affaires d’Alger, zone d’activités, lots 43, 44 and 45, 4th floor, Bab Ezzouar, Algiers, Algeria.
Privacy contact: privacy@clawdya.com. General contact: contact@clawdya.com.
2. Our role
Clawdya as controller. We decide how and why we process the data of our own users (merchant accounts and their team members), of visitors and applicants on clawdya.com, and the billing, security and support data of the service.
Clawdya as processor. When a merchant uses Clawdya Flow to manage its business, the merchant is the controller of the data of its own customers (people who place orders), employees and suppliers. We process that data only on the merchant’s instructions, to provide the service. If you ordered from a shop that uses Clawdya Flow, contact that shop first; we will help it answer your request.
3. Data we collect
Account data. Name, email address, password (stored only as a hash), language, role and permissions in a workspace, sign-in sessions and the IP address used to sign in.
Business data entered or imported by merchants. Products, stock, suppliers, stores, orders, deliveries, returns, payments and costs.
Merchants’ customers. Name, phone number, email address if given, delivery address (wilaya, commune, address), order history, delivery outcomes, and notes or flags the merchant adds. Orders placed on a landing page also carry the campaign tags (UTM) of the link that brought the visitor.
Merchants’ staff. For order-confirmation agents: their pay rate and the confirmation cost of each order. With the optional HR module: name, role, hire and end dates, pay amounts, advances, bonuses and payment records. We do not collect national ID numbers, social security numbers, bank account numbers or family data.
Point of sale. Operator names and PIN codes (stored only as a salted, peppered hash), sales tickets and the fiscal journal.
Copilot. The messages you send (up to 4,000 characters each), images you attach for field extraction, and the files Copilot produces for you.
Files. Product images, logos, shipping labels, exports and other files you upload or generate.
Billing. Plan, invoices and payment status. Card or online payments are handled by our payment provider; we do not store card numbers.
Technical data. Security and error logs (with phone numbers, tokens and similar values removed before they are written), and a keyed hash of the IP address of landing-page visitors for rate limiting. We do not keep landing-page visitors’ IP addresses in clear.
Website forms. Pre-registration: first and last name, email, phone, number of shops, wilaya, carriers used, language. Job applications: name, email, phone, role, wilaya, experience, a link, a message and your CV. For both: country (derived from the IP address), a salted hash of the IP address, the browser user agent and anti-spam signals.
4. Data from platforms you connect
Connections are made by the merchant, from its workspace, and can be removed at any time. Access tokens are encrypted at rest (AES-256-GCM) and are never shown again after connection.
Meta (Facebook and Instagram ads). With the ads_read permission only, we read, for the ad accounts you choose: the account ID, name, currency and time zone; the IDs and names of campaigns, ad sets and ads; their objective; and their spend, impressions, clicks and conversion counts, by hour and by day. We also read your Meta user ID and the permissions you granted, to check the connection. We use this data only to show you the cost and profitability of your own campaigns and products inside your workspace. We never create, edit or pause ads, and we do not access Pages, posts, messages, audiences or your friends. Separately, if you connect Meta Lead Ads, the leads submitted on your forms are imported as orders.
TikTok for Business. With read-only reporting access, we read the same kind of data (advertiser account, campaign, ad group and ad IDs and names, spend, impressions, clicks, conversions) for the same single purpose.
Google. If you connect Google Sheets, we read the spreadsheet you choose to import orders and install the script needed to notify us of new rows. Clawdya’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
Online stores (Shopify, WooCommerce, YouCan, Lightfunnels, Dukaan): we read the orders of your store (customer name, phone, address, items, amounts) to import them. We honour Shopify’s customer data-request and redaction requests.
Carriers (for example ZR Express, Yalidine and the carriers reached through our delivery gateway): we send the recipient’s name, phone and address with each shipment and read back tracking statuses, fees and settlements.
What we never do with platform data. We do not sell it, rent it, share it with data brokers, use it for advertising, build profiles of people from it, combine it across merchants, or use it to train artificial-intelligence models. Each merchant’s data stays in that merchant’s workspace.
5. Why we use data, and on what basis
To provide Clawdya Flow (orders, confirmation, shipping, stock, point of sale, HR, profitability, Copilot, integrations): performance of our contract with the merchant.
To secure the service (sign-in protection, anti-spam, fraud and abuse prevention, rate limiting, error monitoring, audit logs): our legitimate interest in keeping the service safe.
To bill, keep accounting and fiscal records, including the point-of-sale fiscal journal: legal obligations.
To answer pre-registrations, job applications and support requests: your consent, given in the form, and steps taken at your request.
To send service emails and notifications (account verification, password reset, invitations, alerts you configure): performance of the contract. We do not send marketing to merchants’ customers.
We do not make decisions with legal or similarly significant effects about you based solely on automated processing.
6. Copilot and artificial intelligence
Copilot answers questions about your own workspace (for example orders, stock or ad spend) by reading that data through controlled tools, with your permissions. To generate answers, the request and the data needed to answer it are sent to Google’s Gemini API under Google’s paid-service terms, under which Google does not use the content to train or improve its models. HR and pay data are never sent to Copilot. Copilot never changes data on an ad platform. Files you attach to Copilot are deleted after 60 minutes, and files it generates after 24 hours.
8. International transfers
Clawdya is based in Algeria. Our servers are hosted in the European Union (Netherlands), and some providers (Cloudflare, Google, Sentry) may process data in other countries. We make these transfers within the framework of Law No. 18-07 and, for EU data, with appropriate safeguards such as the European Commission’s standard contractual clauses.
9. How long we keep data
- Workspace data (orders, customers, products, Copilot conversations…): for as long as the workspace exists. When a workspace is deleted, its data is erased within 30 days, connection tokens are destroyed, and audit records are anonymised and kept for at least one year.
- Ad platform data: hourly figures for 13 months, then kept as daily totals while the workspace exists; deleted when you remove the app on the platform’s side or ask us to (see section 11), and with the workspace.
- Copilot files: 60 minutes for attachments, 24 hours for generated files.
- Exports: 24 hours.
- Webhook and integration logs: 7 to 90 days.
- Carrier polling responses: 30 days.
- Trial-abuse fingerprints (hashes only): 6 months.
- Point-of-sale fiscal journal and invoices: at least the period required by tax law (6 years or more).
- Pre-registrations and job applications: until the launch campaign or recruitment ends, and at most 24 months, unless you ask us to delete them earlier.
10. Security
Data is encrypted in transit (TLS). Credentials and access tokens of connected platforms are encrypted at rest with AES-256-GCM. Every workspace is isolated from the others, access is limited by roles and permissions, sensitive actions are logged, and personal data is removed from error reports. No system is perfectly secure; if a breach affects your data, we will inform you and the competent authority as required by law.
11. Deleting your data and disconnecting platforms
Merchant account or workspace. The workspace owner can ask us to delete it by writing to privacy@clawdya.com. Data is erased within 30 days, except what the law requires us to keep.
Meta. To stop our access, open Settings › Profitability › Ads in Clawdya Flow and click Disconnect: we revoke the permission at Meta and destroy the access token. To also delete the ad data we already read, remove the app in Facebook: open Settings & privacy › Settings › Business integrations (or Apps and websites), select ClawdyaFlow Ads and remove it. Meta then notifies us and we delete the stored ad data of that connection and its access token. You can also email privacy@clawdya.com from the address of your Clawdya account; we confirm deletion within 30 days and give you a confirmation code you can check.
TikTok. Disconnect in Settings › Profitability › Ads, or revoke the app in TikTok for Business; then email us if you also want past ad data deleted.
Other connections (stores, carriers, Google Sheets): disconnect them in the workspace settings. For Google, you can also revoke access at myaccount.google.com/permissions.
12. Your rights
Under Law No. 18-07 you have the right to be informed, to access your data, to have it corrected or deleted, and to object to its processing for legitimate reasons. If the GDPR applies to you, you also have the rights to restriction, to data portability and to withdraw consent at any time.
Write to privacy@clawdya.com. We answer within one month and may ask you to prove your identity. If you are a customer of a shop that uses Clawdya Flow, we pass your request to that shop, which decides on it as controller.
You can also lodge a complaint with the Algerian data-protection authority, the Autorité nationale de protection des données à caractère personnel (ANPDP), or with the supervisory authority of your country.
14. Children
Clawdya Flow is a professional service for businesses. It is not intended for people under 18, and we do not knowingly collect their data as users.
15. Changes to this policy
We may update this policy. The date at the top shows the latest version. If a change significantly affects how we use your data, we will inform merchants in the application or by email before it takes effect.