CLC App Privacy Notice
This Privacy Notice explains how Grassroots Economics Foundation (GEF, we, us, or our) handles personal data when you visit or use the Cosmo-Local Credit App at cosmolocal.credit and the related services that GEF operates (together, the App).
Read before publishing. Your private profile is not a public profile. Information you enter or copy into a Voucher, Pool, Offering, Want, Catalog, or Post can nevertheless be published through that resource. A resource's description, terms, images, tags, Wallet addresses, and exact map coordinates can be visible without signing in. Contact details on a Voucher, Pool, or Want are shown only through signed-in resource-information or contact features, but the recipient can still copy or share them.
This Notice supplements the Terms of Service and the Data Protection Policy.
1. Who is responsible for your data?
Grassroots Economics Foundation is the operator of the App and the data controller for the App data described in this Notice, except where another party independently determines how it uses data.
Contact GEF at:
- Email: [email protected]
- Postal address: P.O. Box 1659-80108, Kilifi, Kenya
Issuers, Pool Stewards, payment providers, Wallet providers, blockchain participants, and operators of external services may be independent controllers for information they receive or publish. Their own notices and terms may also apply.
2. Who and what does this Notice cover?
This Notice covers visitors, account holders, people using App features, and people whose information an authorized user submits through the App. It covers GEF-operated App interfaces, APIs, catalogs, storage, relaying, notifications, moderation, support, and related operational services.
It does not control how an independent Issuer, Pool Steward, third-party provider, public blockchain, external website, or another user processes information outside GEF's role. The App is for adults who meet the eligibility requirements in the Terms.
3. Data we collect
Account and profile data
Depending on the features you use, we may collect:
- your username and public blockchain Wallet address;
- your name, email address, phone number, country, and preferred currency;
- your biography, website, avatar, and saved location name and coordinates;
- account role, status, resource limits, and account creation or update times; and
- settings, language, notification preferences, and other choices you make.
Your username is different from your private profile name. It is used as a recipient identifier and can be returned with your Wallet address to a signed-in person who enters the exact username. Your profile can be used to prefill forms, but prefilling a form does not publish the field until you choose to publish the resource.
Authorized administrators can search the account directory by name, username, email, phone number, or Wallet address and can see account identity and contact fields, role, status, resource limits, and associated resources where needed to operate, support, moderate, and secure the App. This directory is not public.
Authentication, Wallet, and transaction data
We may process Wallet addresses, signed messages, transaction authorizations, signatures, passkey credential identifiers and public-key coordinates, credential state, session identifiers and roles, transaction requests, relayer records, replacement-transaction data, and transaction status. If a sign-in card is replaced, we can retain the old and new Wallet addresses, proofs of the requested change, linked passkey state, and the operational records needed to resume or verify the change.
The App stores the private material for its browser sign-in card in that browser's local storage so the browser can sign. GEF services receive signatures and signed transactions rather than that raw private key. A passkey provider protects the passkey's private key; the App and its services use the credential identifier, public-key material, challenge, and signed assertion needed to register or verify it. If you use a paper Wallet, sign-in card, passkey, or another credential, you are responsible for protecting the device and private material.
Where a Voucher or Pool is controlled by a compatible multisig, we may process the multisig address, signer Wallet addresses, approval threshold, proposed transactions, confirmations, execution state, and permissions needed to display and operate multisig controls. The owner address, signer set, and threshold can be returned through public ownership inspection and can also be visible on a public blockchain.
Device, security, and usage data
We may collect technical and operational information such as IP address, browser and device information, timestamps, requested pages or endpoints, session and security events, validation errors, rate-limit information, notification subscriptions and delivery acknowledgements, service activity, and diagnostic records.
Content and support data
We process information you submit in Vouchers, Pools, Offerings, Wants, Catalogs, Posts, Voucher and Pool Reviews, images, attachments, terms, descriptions, tags, locations, contact fields, private post-transaction messages or orders, complaints, support messages, and other communications.
If you use App messaging, we process:
- conversation requests and status;
- participant Wallet addresses, usernames, and avatars;
- message text, images, and timestamps;
- each user's read marker, block records, and request-quota records; and
- helpdesk threads and abuse reports.
Direct messages are private to the two conversation participants. GEF administrators can read helpdesk messages. They can read a direct message only when a participant attaches it to an abuse report.
Do not publish another person's personal data, image, contact information, or precise location unless you have a lawful reason and any permission that is required.
4. What becomes public?
The App has five important visibility levels.
| Visibility | What it means |
|---|---|
| Private profile and account data | Profile name, email, phone number, saved location, preferences, authentication records, and similar account information are used to operate the App and are not automatically placed in public resource responses. Authorized GEF personnel and service providers may access them when necessary for their work. Authorized administrators can also search and manage the non-public account directory. |
| Exact recipient lookup | A signed-in user who enters your exact username or full phone number may receive your public username and Wallet address. Partial usernames do not return a user. The phone number used for the query, your private profile name, email, phone number, and saved location are not returned in the recipient result. |
| Public catalog and resource data | Published descriptions, terms, images, tags, Wallet and contract addresses, locations, exact coordinates, Offers, Wants, Posts, Reviews, Pool rules, and technical settings can be visible without signing in. Public fields may be indexed, copied, shared, or associated with a Wallet or another resource. |
| Signed-in resource contact | Email, phone, website, or contact instructions deliberately added to a Voucher, Pool, or Want are removed from signed-out catalog and detail responses. A signed-in person can request the full contact-bearing Voucher or Pool record, or the contact methods selected for an active Want. The recipient can still copy, use, or share that information. Retired resources have narrower owner-or-administrator access. |
| Public blockchain records | Wallet addresses, contracts, balances, holdings, transfers, amounts, counterparties, timestamps, signatures, and contract actions can be visible permanently through public networks and independent block explorers. GEF cannot erase or rewrite a public blockchain. |
App messages are not public. The two participants can see each other's Wallet address, username, avatar, messages, images, conversation status, and timestamps. Read markers, block lists, and request quotas are operational records and are not public.
Removing a resource from the App's catalog does not remove copies already made by other people, search services, archives, independent indexers, or public blockchains.
5. Public resource fields
The fields available to a resource can change as the App develops. The form shown before publication is the most direct notice of what you are choosing to publish.
| Resource | Information that can become public |
|---|---|
| Voucher | Public: contract and chain identifiers; Voucher name, symbol, description, stated unit and value; Issuer or owner Wallet address; terms; location name and exact coordinates; images; tags; visual markers; and active catalog status. Signed in: deliberately entered email, phone, and website. Retired records are available only to an authorized owner or administrator through the complete-information endpoint, while chain history can remain public. |
| Pool | Public: contract and chain identifiers; Pool name and description; owner, fee-recipient, dependency, or other technical-controller Wallet addresses; supported Vouchers; inventory or availability information; valuation method; fees, limits, rules, other configuration; location name and exact coordinates; images; tags; timestamps; and, for compatible multisigs, owner, signer addresses, and approval threshold. Signed in: deliberately entered email, phone, and website. Retired records have the same narrower complete-information access as retired Vouchers. |
| Offering | Linked Voucher details; seller or provenance Wallet address; goods or services offered; description, quantity, unit, frequency, price, and availability; location name and exact or inherited coordinates; image; tags; and timestamps. |
| Want | Public: requested goods or services; description; tags; image; status and dates; location name and exact coordinates. Signed in: only the contact instructions, email, or phone deliberately selected for that active Want. Public Want responses omit those contact fields and do not identify the creator's private profile, although linked Vouchers or Pools can create an indirect association. |
| Catalog | Catalog name, description, image, tags, owner Wallet address, listed members or resources, counts, location name and exact coordinates, and timestamps. |
| Published Post | Title, summary, body, host name, participant information, dates, images, captions, attachments, embedded links, tags, linked Vouchers or Pools, and exact coordinates. The author's Wallet address and workflow status are retained for management and accountability but omitted from public Post responses. Linked resources or the content itself may still reveal an association. |
| Voucher or Pool Review | Rating, comment, and any public reply by the Voucher or Pool owner. The public Review response omits the reviewer's Wallet address and redemption or swap evidence. The service retains the reviewer address and evidence needed to verify eligibility, prevent duplicate reviews, support replies and flags, moderate content, and enforce the review period. Administrators can receive the report reason and the reported Review content when a Review is flagged. |
Contact details and exact coordinates can create personal safety risks. Use a suitable public contact method and a safe public meeting place rather than a private home whenever possible.
6. Public blockchain information
The App interacts with public blockchain networks. A transaction may disclose the Wallets involved, Token or Voucher contract, amount, time, status, signature, and related contract events. Pool contracts can also disclose supported assets, balances, deposits, payouts, swaps, liquidity withdrawals, fees, limits, valuations, owners, administrators, dependencies, and other configuration. Compatible multisigs can disclose signer sets, thresholds, proposals, confirmations, and executed actions.
Blockchain information may be processed by network validators, node operators, indexers, Wallet software, analytics services, and anyone who reads the network. Transactions can be irreversible. Closing an App account, changing a profile, replacing a sign-in card, removing or retiring a catalog resource, destroying Voucher units, or asking GEF to delete off-chain data does not delete earlier blockchain records or independently indexed copies.
7. Why we use data and our legal grounds
We use personal data only where we have an applicable legal ground. The ground can depend on the person, feature, and jurisdiction.
| Purpose | Typical legal ground |
|---|---|
| Create and operate accounts, authenticate users, provide requested features, submit authorized transactions, and provide support | Performance of our agreement with you and steps taken at your request |
| Publish a resource or contact method you deliberately submit for public display | Performance of our agreement, your deliberate public action, and consent where consent is required |
| Protect accounts and services, prevent fraud or misuse, enforce limits, investigate incidents, and maintain reliable records | Legitimate interests in operating a safe and accountable service, performance of our agreement, and legal obligations |
| Moderate Content, review complaints, enforce the Terms, and protect users or the public | Legitimate interests, performance of our agreement, and legal obligations |
| Keep financial, transaction, governance, compliance, tax, and dispute records | Legal obligations and legitimate interests in accountability and legal claims |
| Send optional communications or notifications | Consent where required, or our agreement and legitimate interests for service messages |
| Improve services and produce research or aggregate statistics | Legitimate interests, consent where required, and other lawful research grounds with appropriate safeguards |
We do not treat your decision to publish one field as consent to publish unrelated private profile fields.
8. Required and optional data
The App identifies required fields in the relevant form. Current guided account creation requires a Wallet address and authentication proof, a name, a profile image, a country and saved location, a preferred currency, and at least one email address or phone number. A username is optional. Other sign-in or account-recovery paths can create temporary system values until the user completes or corrects the profile. Particular features can require additional transaction, contact, location, eligibility, or resource information.
Other profile and resource fields are optional unless the form says otherwise. If you do not provide required information, we may be unable to create an account, authenticate you, submit a transaction, publish a resource, provide support, meet a legal requirement, or make the requested feature available.
Optional does not mean private after publication. An optional contact detail, image, description, or map pin becomes public if you add it to a resource and publish that resource.
9. How we receive data
We receive data:
- directly from you or a person authorized to act for you;
- from your browser, device, Wallet, passkey, or notification service;
- from public blockchain networks, contracts, nodes, and indexers;
- from Issuers, Pool Stewards, counterparties, payment or service providers, and other users involved in a feature or transaction;
- from public sources where collection is lawful; and
- from security, moderation, support, and compliance processes.
10. Who receives data?
We disclose only the information reasonably needed for the stated purpose, applicable law, or your requested public action. Recipients can include:
- App visitors and users when you publish a resource or use a public blockchain;
- signed-in App users when they request contact details you deliberately attached to an active Voucher, Pool, or Want;
- the other participant in a direct conversation;
- authorized GEF administrators handling a helpdesk thread or abuse report, subject to the limits described in Section 3;
- Issuers, Pool Stewards, counterparties, and other participants needed for a transaction, redemption, complaint, or requested service;
- infrastructure providers for hosting, databases, storage, content delivery, security, authentication, support, email, notifications, mapping, geocoding, blockchain access, indexing, transaction relaying, and monitoring;
- independent Wallet, blockchain, payment, stablecoin, cash-ramp, or other third-party service providers you choose to use;
- professional advisers, auditors, insurers, researchers, funders, and partners under appropriate duties and safeguards; and
- regulators, courts, law-enforcement bodies, or other persons where disclosure is required by law or reasonably necessary to protect rights, safety, and the integrity of the service.
The production web application is delivered through Cloudflare Pages. Its current browser configuration uses MapTiler for map styles and IP-based location suggestions, ArcGIS World Geocoding for place search and reverse geocoding, and configured Gnosis Chain RPC endpoints for chain reads. Those services receive the request data needed to answer, which can include IP address, browser information, map area, search text, coordinates, or Wallet and contract queries.
Other integrations are feature-dependent. When enabled and used, a notification service processes push-subscription endpoints, device state, linked Wallet addresses, delivery and click acknowledgements, and inbox state; a transaction relayer processes signed requests and transaction status; a Safe transaction service processes multisig addresses, proposals, signatures, confirmations, and execution state; and a payment or cash-ramp provider processes the phone number, Wallet address, asset, amount, provider identifier, rate, and transaction status needed for that feature. Image storage, the App API, databases, blockchain indexers, and monitoring infrastructure process the content and operational records needed for their functions. A third-party service can also collect data directly under its own privacy notice.
Current service register
This register records services evidenced by the production configuration reviewed on 17 November 2026. A deployment-dependent service appears only when the relevant feature is configured or used. Provider features, locations, and notices can change; the current notice presented by the provider also applies.
| Service or category | Purpose and data involved | Provider information | Status |
|---|---|---|---|
| Cloudflare Pages | Delivers the web application and processes network requests, including IP address, browser, security, and request information. | Cloudflare Privacy Policy | Current production web hosting |
| MapTiler | Supplies map styles and IP-based location suggestions; requests can include IP address, browser information, map area, and location context. | MapTiler Privacy Policy | Current browser configuration |
| Esri ArcGIS World Geocoding | Provides place search and reverse geocoding; requests can include search text, coordinates, IP address, and browser information. | Esri Privacy Statement | Current browser configuration |
| GEF-operated App services | Provide the App API, database, image storage, indexing, configured RPC access, transaction relaying, support, and related operations. The data depends on the requested App feature. | This Privacy Notice and the Data Protection Policy | Current, with individual components enabled by deployment |
| Safe transaction service | Supports compatible multisig discovery and transaction coordination, including Safe addresses, signers, thresholds, proposals, confirmations, and execution state. | Safe Privacy Policy | Deployment-dependent |
| Notification, payment, cash-ramp, and other optional providers | Process only the information needed for an enabled feature, as described above and in the provider terms shown with that feature. | The applicable provider's notice and transaction terms | Deployment-dependent |
11. International processing
The App, public blockchain networks, service providers, partners, and users can operate in more than one country. Personal data may therefore be accessed or processed outside Kenya or the country where it was collected.
Where a transfer requires safeguards, GEF uses measures appropriate to the transfer and applicable law, which can include contracts, access restrictions, encryption in transit, assessments of the recipient and destination, consent where appropriate, or another legally recognized transfer basis. Public information and blockchain transactions can be accessed globally and cannot be confined to one country.
12. How long we keep data
GEF keeps personal data only for as long as reasonably necessary for the purpose for which it was collected, including:
- while an account, resource, transaction, conversation, block, abuse report, complaint, or support matter remains active;
- for security, fraud prevention, reconciliation, audit, governance, research-integrity, and service-continuity needs;
- for tax, accounting, regulatory, contractual, dispute, limitation-period, or other legal requirements; and
- for a limited period in protected backups and logs before scheduled deletion or replacement.
Different records therefore have different retention periods. We delete, aggregate, de-identify, or restrict data when it is no longer needed, unless preservation is required or permitted by law. Public blockchain records and copies controlled by other people are outside GEF's deletion control.
13. Security
GEF uses proportionate technical and organizational measures designed to protect personal data. These can include access controls, authentication, role separation, secure transport, system updates, monitoring, backups, incident procedures, staff duties, and provider safeguards.
No online system, public blockchain, credential, or transmission is completely secure. You must protect your devices, sessions, passkeys, private keys, paper Wallets, and recovery information and review information before making it public.
14. Your rights and choices
Subject to applicable law, you may have the right to:
- be informed about how your personal data is used;
- request access to personal data GEF holds about you;
- request correction of inaccurate or misleading data;
- object to or request restriction of particular processing;
- withdraw consent where processing depends on consent;
- request deletion of data that GEF is not required or entitled to retain;
- receive portable data where the right applies; and
- complain to the Office of the Data Protection Commissioner (ODPC) or another competent authority.
Send a request to [email protected]. We may need to verify your identity and authority before acting. Rights can be limited by other people's rights, public records, legal duties, technical necessity, or the permanent nature of a public blockchain.
You can also choose not to enter optional profile fields, remove optional information before publication, use a suitable public contact method, select a safe public map point, manage notification permission, and avoid a feature that requires data you do not wish to provide.
Information about Kenyan data-subject rights is available from the ODPC. A data subject can also use the ODPC's official complaint page.
15. Children
The CLC App is restricted to people who are at least 18 years old and have reached the age of legal majority that applies to them. Do not create an App account for a child or submit a child's personal data through the App unless GEF has expressly provided a separate lawful process with the required safeguards and authorization.
GEF activities outside the App that involve children are governed by the Child Safeguarding Policy and applicable data-protection requirements.
16. Complaints and incidents
Contact [email protected] if you have a privacy complaint, believe personal data has been published without authority, or suspect a data-security incident. Include enough information for us to locate and assess the issue, but do not send private keys, passwords, or unnecessary sensitive data.
You may also complain to the Office of the Data Protection Commissioner or another authority with jurisdiction over the processing.
17. Changes to this Notice
GEF reviews this Notice when App behavior, providers, legal requirements, or data practices materially change. We will publish the current version and effective date on this page and provide any additional notice or consent required by applicable law.
A later Notice does not make previously private data public. The visibility of a resource is determined by the fields, controls, and notices that apply when it is published or later edited.
18. Contact
For privacy questions or requests:
Grassroots Economics Foundation
P.O. Box 1659-80108
Kilifi, Kenya
[email protected]