The short version
Faida is local-first. We do not sell personal information, use it for third-party advertising, or include advertising trackers in the app. Cloud, licensing, payment, online-shop, and support features process only the information needed to provide those services.
1. Who this policy covers
This policy applies to the Faida applications, faida.app, the Faida customer portal, optional cloud services, and support provided by Algolab Limited (together, “Faida”). It covers account holders, workspace members, website visitors, and people whose information a business chooses to record in Faida.
A business using Faida decides what customer, supplier, employee, and transaction information to enter. That business is responsible for having an appropriate reason to collect and use those records. Algolab Limited processes cloud-hosted business records to provide Faida to that business.
2. Information we collect
Account and organisation information
We process names, email addresses, business names, workspace membership, roles, authentication records, and contact information supplied when an account, company, or support conversation is created.
Website visits and signup progress
We use a first-party browser cookie lasting 90 days to count visits to our public website and understand progress from signup to a purchased licence. We record daily page counts, page categories, approximate country, referrer host or campaign, browser and device categories, and recent visible-tab activity. IP addresses are used transiently for a local country lookup. We associate a signup with that browser and whether it came through the website or a Faida app handoff. This reporting does not store IP addresses, browser fingerprints, or app callback URLs. Browsers requesting Do Not Track or Global Privacy Control are excluded from visitor tracking and signup attribution. Account and payment records remain necessary to provide those services.
Business records
Depending on the features a business uses, Faida can store products, inventory, sales, invoices, payments, customers, suppliers, staff records, loyalty records, orders, attachments, reports, receipt delivery details, and business settings. Local workspaces store these records on the device. Cloud features send supported records to the business’s Faida Cloud workspace for sync, backup, restore, reporting, or online-shop functions.
Licensing, device, and security information
We process licence and seat status, device and installation identifiers, device public keys, app version, platform, sync status, IP address, request logs, and security or audit events needed to activate devices, protect accounts, troubleshoot failures, and keep services reliable.
Payments and support
For licence or service purchases, we keep the plan, amount, currency, tax, status, payer contact details, and provider references. Payment providers process card or mobile-money credentials; Faida does not store complete card numbers. If you contact support, we process your message, attachments, and the account or device details needed to answer it.
3. Why we use information
- create and secure accounts, organisations, roles, and sessions;
- activate licences and keep authorised devices connected;
- provide local POS, inventory, accounting, reporting, and export tools;
- provide optional sync, backup, restore, portal, and online-shop services;
- process purchases, taxes, receipts, refunds, and payment status;
- send service messages and respond to support or privacy requests;
- detect abuse, investigate errors, and maintain service security; and
- meet legal, tax, accounting, and dispute-resolution obligations.
We use information to perform our agreement with you, follow your business’s instructions, operate and secure Faida, comply with law, and—where required— act with your consent. We do not use business records to build advertising profiles.
4. What stays local and what reaches the cloud
Faida writes shop records to the local workspace first so sales can continue without a reliable internet connection. A local-only workspace does not sync those operational records to Faida Cloud. Data can still leave the device when someone intentionally exports a file, creates a backup, sends a receipt, opens an online service, or contacts support.
When a business enables Faida Cloud, supported operational records and changes are transmitted to its cloud workspace for the enabled features. Account, licensing, update, and security checks also use Faida services even when the operational workspace is primarily local.
Faida Cloud uses HTTPS. Updated hubs and tills use encrypted connections verified against the hub’s certificate when you scan or copy its secure pairing address. Both devices must support secure pairing. Older app versions use authenticated HTTP, and some network receipt printers use unencrypted connections. Use a trusted, private shop network; do not expose the hub or printers to the public internet.
5. Device permissions
- Camera: scan product and scale barcodes.
- Bluetooth and nearby devices: find and connect to compatible receipt or kitchen printers.
- Local network: connect tills, back-office devices, printers, and a paired LAN hub.
- Files: let you choose imports, exports, attachments, and backup locations.
- Internet: reach licensing, updates, portal, payment, support, and optional cloud services.
On Android 11 and earlier, the operating system can require location permission for Bluetooth discovery. Faida limits that legacy permission to those Android versions and does not use it to track or store your precise location. Permissions can be changed in device settings, although the related feature may stop working.
7. How long information is kept
Local business records remain in the workspace until an authorised user deletes them, resets the workspace, or removes the app and its data. Cloud records remain while the service is active and for the backup, recovery, and deletion cycle needed to operate it. Account, licensing, billing, support, fraud-prevention, and audit records are kept only as long as needed for the purposes above and any legal, tax, accounting, security, or dispute duties.
When deletion is completed, information is removed from active systems or de-identified. Residual copies can remain in protected backups until those backups rotate, and records that law requires us to keep remain restricted to that purpose.
8. Access, correction, export, and deletion
Depending on where you live, you may ask to access, correct, export, object to, restrict, or delete personal information, or withdraw consent. Workspace owners and administrators can manage many business records and members directly. You can also email hello@algolab.africa.
To delete a Faida account and its associated cloud data, use the direct account deletion page. Sign in and confirm the request directly; no email or telephone request is required. We aim to complete requests within 30 days and email confirmation with any legally required retention details. Uninstalling the app does not by itself delete a cloud account.
We may verify your identity and your authority over a business workspace before fulfilling a request. We will explain if a request cannot be completed or if specific records must be retained.
9. Security
Faida uses measures appropriate to the service, including protected credentials, signed releases, device authentication, encrypted network transport for cloud services, role-based access, audit records, and restricted administrative access. No method of storage or transmission is completely risk-free, so businesses should also protect their devices, passwords, exports, and local backups.
Security questions can be sent to hello@algolab.africa.
10. Children
Faida is a business operations product and is not directed to children. We do not knowingly invite children to create Faida business accounts. If you believe a child has provided personal information without appropriate permission, contact us so we can investigate and delete it where required.
11. Changes and contact
We may update this policy when Faida, our providers, or applicable law changes. The effective date at the top identifies the current version. Material changes will be communicated through an appropriate product, account, or website notice.
For privacy questions or requests, contact Algolab Limited at hello@algolab.africa. Include “Privacy” in the subject so the request can be routed correctly.