CloverBee Maker
Privacy Policy
Effective and last updated: October 1, 2026.
CloverBee Maker ("Maker") is a business-operations application provided by CloverBee Ventures ("CloverBee", "we", "us" or "our"). This policy explains what information Maker processes, why it is used, where it is processed, and the choices available to users.
1. Scope
This policy applies to the CloverBee Maker mobile application and the cloud services used to operate it, including authentication, synchronization, storage, receipts, support, export and account administration. It also applies to information you send to us for Maker support or privacy requests.
The general CloverBee Maker marketing website has a separate website-focused privacy notice at cloverbeemaker.ca/privacy.html.
2. Information Maker processes
Account and profile information
When you create or use a Maker account, Maker may process information such as:
- email address and account/authentication identifiers;
- your name and business role;
- business membership and permission information;
- account, session, verification and authentication status; and
- account-deletion, recovery or other account-administration records.
Authentication is provided through Supabase Auth. Authentication secrets are handled through that authentication system; CloverBee does not need or intend to store readable account passwords in Maker business records.
Business information you enter
Maker is designed to store records for the business using the app. Depending on the features you use, those records may include:
- business name, contact information, address, country/region, currency, time zone, fiscal settings and tax settings;
- customer and supplier names, email addresses, phone numbers, addresses, notes and related records when you choose to enter them;
- products, variants, materials, recipes, inventory, production and batch records;
- purchases, expenses, costs and inventory movements;
- sales, orders, fulfillment, prices, discounts, taxes, charges and payment records;
- receipt information and receipt-contact information;
- subscription plan, app-store transaction and entitlement information needed to verify Free/Paid access;
- business notes and other text you choose to enter; and
- files, images, receipts or attachments you choose to upload where an upload feature is available.
Payment records in Maker may include items such as payment method, amount, status and references needed for business records. When you use an integrated third-party payment service such as Square, Maker may send the payment amount and transaction reference to that provider and receive provider transaction identifiers and payment status needed to reconcile the Maker payment ledger. The payment provider processes card or wallet credentials under its own privacy practices. Maker is not intended to collect or store full card numbers, CVV codes or similar card credentials. Do not place sensitive payment credentials in free-text notes or attachments.
Device, synchronization and security information
Maker uses device authorization and offline synchronization. To provide those functions, Maker may process:
- app-generated device identifiers and device authorization status;
- business and user identifiers associated with an authorized device;
- record identifiers, synchronization sequence information, timestamps, retries and outbox state;
- security and audit information used to validate access and investigate abnormal activity; and
- ordinary network and service logs, which may include IP address, request timestamps and technical request information.
Support and feedback
If you contact CloverBee for support, feedback or a privacy request, we process the information you provide in that communication. We may also use relevant account, app-version, synchronization or error context when necessary to diagnose a problem. We do not need customer, sale or recipe contents for ordinary diagnostics unless you deliberately provide them or they are specifically required to investigate an issue.
3. How we use information
We process information to:
- create, authenticate and administer Maker accounts;
- create and operate business workspaces;
- authorize users and devices;
- store, synchronize and recover business records across authorized use;
- provide products, inventory, production, sales, orders, receipts, reports and export functions;
- provide customer support and troubleshoot technical problems;
- protect Maker, its users and business data from unauthorized access, abuse or security incidents;
- maintain service reliability and backups; and
- meet legal, accounting, security or regulatory obligations that apply to CloverBee.
Receipt contact information is used to provide the requested receipt-related function. Entering an email address or phone number for a receipt does not automatically subscribe that person to marketing.
4. Local storage and cloud processing
Maker is designed to work offline. Business data may be stored in a local SQLite database on an authorized device and synchronized when a network connection is available.
Maker also uses cloud infrastructure to operate the service:
- Supabase provides authentication, PostgreSQL database services and file storage used by Maker.
- Render hosts the FastAPI service that acts as Maker's trusted application, authorization and synchronization gateway.
- Apple App Store processes iOS subscription purchases and provides Maker with transaction and entitlement information. Google Play would perform the equivalent role if and when Maker is released on Android.
- Square processes customer payment credentials when a business deliberately uses the Maker 1.0 Square Point of Sale handoff.
These providers process information on CloverBee's behalf as necessary to provide their infrastructure services. Data may be processed or stored in jurisdictions outside your province, state or country depending on provider infrastructure and service configuration, and may therefore be subject to the laws of those jurisdictions.
5. Sharing and disclosure
We do not sell personal information or customer data. We do not disclose Maker business data to third parties for their own advertising purposes.
Information may be disclosed only as reasonably necessary:
- to infrastructure and service providers that operate Maker for us;
- at your direction, for example when you export, share or send a receipt or business record, use an app-store purchase, or initiate a supported third-party payment integration;
- to investigate security incidents, fraud, abuse or threats to the service; or
- when required by applicable law, legal process or a valid government request.
6. Advertising and tracking
Maker 1.0 does not contain advertising. CloverBee does not use Maker data for cross-app advertising tracking and does not sell personal or customer data.
If Maker later adds a feature that materially changes these practices, this policy and any required platform privacy disclosures will be updated before that feature is relied upon.
7. Security and business separation
Maker is designed with business-level authorization controls. Normal business operations pass through the FastAPI service, which validates the signed-in account, active business membership, role and authorized-device status. The Supabase database also uses row-level security as an additional tenant-separation control.
We use technical and administrative safeguards intended to protect Maker data, but no application, device, network or cloud service can guarantee absolute security. Maker is not designed as end-to-end encrypted storage from the service operator: the service infrastructure must be able to process business data to provide Maker's functions.
You are responsible for protecting access to your device, email account and Maker login and for limiting access to authorized people.
8. Retention, account deletion and recovery
While a Maker business is active, its normal operating data is retained so the service can provide synchronization, history, reporting, tax records and other business functions. Subscription cancellation or a future plan downgrade is not the same as deleting business data.
Maker provides an account/business deletion process with a recovery period:
- Day 0: an authorized owner requests deletion after the required confirmation and reauthentication. The business enters a deletion-pending state.
- Days 0-30: the business is recoverable and read-only. The owner can export data or cancel deletion. Staff/administrator access is disabled and new business writes/uploads are blocked.
- At approximately Day 30: active Maker business data is permanently removed from the active service and is no longer recoverable through Maker.
- Up to approximately Day 60: secure residual backup copies may remain until they expire through the normal backup-retention process.
Limited records may be retained longer where reasonably required for CloverBee's legal, accounting, fraud-prevention or security obligations. Such retention is not intended to preserve the normal deleted operating dataset.
If an account is associated with business ownership, deletion must respect the ownership and business-deletion safeguards built into Maker. This prevents an owner action from silently orphaning or bypassing the business's retained records.
9. Access, correction and export
Maker users can view and edit many account and business records directly in the app according to their permissions. Maker also provides data-export functions so a business can obtain its own records. Export may include structured and human-readable business records and, where applicable, uploaded attachments.
For help accessing, correcting, exporting or deleting information, contact us using the address below. We may need to verify your identity and authority over the relevant account or business before acting on a request.
10. Your customers' information
A business using Maker may enter information about its own customers, suppliers, employees or other contacts. In that situation, the Maker business user decides what information to enter and why it is needed for that business. Users are responsible for using Maker in a manner consistent with the privacy and record-keeping obligations that apply to their own business.
11. Maker Modules
Optional Maker Modules may use the same business data already stored in Maker when that is necessary to provide the module's function. If a future module requires materially different categories of personal information, third-party sharing or processing, we will update this policy and any required platform disclosures before relying on that change.
12. Changes to this policy
We may update this policy as Maker changes. Material changes will be reflected by updating the date at the top of this page and, when appropriate, by providing additional notice in Maker or through another reasonable channel.
13. Contact
Questions, access requests, deletion questions or other privacy concerns about Maker can be sent to: