Privacy Notice

1. Who is responsible

Deluxe Technologies FZC, based in United Arab Emirates, operates Kemster and is the controller of personal information processed to run this marketplace. This notice covers our website, mobile applications, messaging, agents and APIs. For privacy questions, rights requests or the operator's current registered contact details, contact us.

Other members, dealers, payment services and AI providers may act as independent controllers for their own activities. Their privacy notices also apply when you interact with them. Features and providers described below are used only where enabled or needed for the service you use.

2. Information we collect

  • Account and profile: account identifiers, email, display name, avatar, sign-in and verification status, biography, country, chosen place, currency, language, timezone, notification preferences, business details and information you give support. Clerk handles sign-in and may receive information from the social sign-in provider you choose.

  • Verification: phone numbers, pending numbers, channel and verification results. Where available, Twilio Verify sends codes by SMS, WhatsApp or voice. Stripe Identity collects government-ID documents and a matching selfie for ID checks. Kemster stores the verification session identifier, status, time and error information rather than copies of those documents or selfies in its member record. Stripe's verification notices describe its processing, including facial comparison.

  • Location: the country and place you choose for your account, listings and wants, and location or distance information needed for matching and search. Addresses or meetup details you type into a post or message are also information you supply; avoid publishing your home address.

  • Marketplace activity: listings, wants, photos, audio or video you upload, prices, search and matching activity, contact requests, messages, offers, deal confirmations, meetup arrangements, reviews, reports and moderation records.

  • Agents and integrations: instructions, conversations, actions, approvals, usage, API-key metadata, connected-provider settings and credentials needed for authorized integrations. Connected AI-provider keys are encrypted in storage; Kemster access keys should still be treated as secrets.

  • Device and usage: IP address, browser or device information, request and error logs, app push tokens, activity events and approximate last-active information. These help operate, secure and understand the service.

  • Billing: Stripe customer, checkout, subscription and payment references, billing country, purchase amounts, currency, status and entitlement records. Stripe collects payment-card details through its payment interfaces; Kemster does not store full card numbers or card security codes.

We receive information from you, your authorized agents, authentication and verification providers, payment events, feed partners and other members, for example when someone reviews a deal or reports a message.

3. Purposes and legal bases

Where a law requires a legal basis, we use the basis appropriate to that activity and jurisdiction:

  • Contract or steps you request before a contract: creating accounts, publishing your posts, finding matches, delivering messages, operating authorized agents and integrations, fulfilling paid features and providing support.

  • Legitimate interests, where recognized and balanced against your rights: preventing fraud and abuse, enforcing rules, securing systems, measuring service performance, improving matching and investigating complaints.

  • Legal obligations: responding to valid legal requests, meeting applicable accounting and tax duties, and protecting rights as required by law.

  • Consent, where required: optional communications, device permissions and processing for which local law requires consent, including relevant verification steps. You can withdraw consent without affecting lawful processing before withdrawal. Declining information needed for a particular feature may prevent its use.

These principles apply as relevant under laws such as the EU GDPR, UK GDPR, applicable United States federal and state privacy laws (including the California Consumer Privacy Act where applicable) and the UAE Personal Data Protection Law. Not every legal basis or right applies identically everywhere. We will explain the basis for a particular use on request.

Matching, trust signals, fraud checks and moderation can involve automated processing. They can affect what appears in results or which features you can use. You can challenge a restriction and request human review through Contact, including where applicable law gives rights concerning automated decisions.

4. What other people can see

Public listings, public wants, reviews, stores and profiles can be viewed outside Kemster and indexed by search engines. A public profile can show your display name, avatar, biography, chosen place and country, currency, languages, membership date, badges, trust level, reputation, ratings, completed-deal and active-post counts, and response statistics. Distance is derived from chosen places, not a live location feed.

A profile may show a masked personal phone number exposing its last two digits; it does not publish your account email or full personal phone number by default. Business profiles can show a store handle, business name, website, hours, summary and the business phone or WhatsApp number you supply. Do not enter private contact details in public fields.

Last-active display is controlled by your opt-in setting. When enabled, other members see a broad period such as "today" or "this week", not your exact last-active timestamp.

Messages, contact requests, offers and meetup information are shared with the relevant participants and their authorized agents as needed for the interaction. Visibility settings limit discovery of private wants, but authorized contacts and agent actions may share relevant details. Recipients can keep or copy information you send; removing it from Kemster cannot recall their copies or immediately clear search-engine caches.

5. Providers and other disclosures

We use providers in these categories, giving them information needed for their role:

  • Hosting, databases, object storage and delivery infrastructure: to run the site and apps and store and serve content.

  • Authentication: Clerk, for accounts and sign-in.

  • Payments and ID verification: Stripe and Stripe Identity.

  • Phone verification and communications: Twilio, including enabled SMS, WhatsApp and voice channels.

  • Email: Resend or the configured mail-delivery service, for transactional and selected notifications.

  • AI: OpenAI and other configured model providers for enabled AI features; providers you connect yourself for your authorized agent or drafting requests. Relevant prompts, post details, messages or tool results can be sent to the selected provider. Do not submit sensitive information unnecessarily; your provider's account terms and privacy settings govern its own processing.

  • Diagnostics: optional error tracking, including Sentry when configured. Our error-reporting filters scrub sensitive fields, and default personal-information collection is disabled in the server integration; identifiers and technical diagnostics may still be included.

Providers may process some information for their own legally required or independently determined purposes, as their notices explain. We may also disclose relevant information to professional advisers, authorities in response to valid legal process, or parties investigating fraud or protecting legal rights. If our business is reorganized or transferred, information may be shared with appropriate confidentiality and legal safeguards.

We do not sell personal information or use advertising-tracking cookies. Clicking a partner or affiliate link takes you to a third party whose tracking and privacy practices we do not control.

6. How long we keep information

We keep information for the purposes described here, considering account activity, safety, dispute and legal requirements. Expiry, closure and deletion are different:

  • Listings and wants: the default active duration is 30 days, configurable by country and posting settings. Existing posts keep their recorded expiry until changed or renewed. Expired or closed posts stop normal public discovery, but their records and related history are not automatically erased after a fixed number of days.

  • Messages, threads and verification metadata: there is no fixed automatic age-based deletion period for these records. They remain available for ongoing account use, transaction history, support and safety needs, subject to deletion requests and applicable retention duties. Closing a conversation or post is not an erasure request. Stripe and Twilio retain verification information under their own applicable notices and legal duties; we do not promise that closing a Kemster account automatically erases provider-held documents.

  • Derived anti-abuse posting signals: scheduled cleanup removes signals older than 90 days.

  • Activity events: scheduled cleanup uses a configurable retention period, defaulting to 730 days (with supported settings from 30 to 3,650 days).

  • Billing, support, audit and security records: retained as needed for their purpose and any applicable accounting, legal, fraud-prevention or dispute requirements. There is no single automatic expiry for all these records.

Scheduled cleanup depends on successful processing and is not instantaneous. For an erasure request, we assess what can be deleted and what must be retained, restrict retained information to the necessary purpose and explain relevant exceptions. Backups, provider copies and information already received by others may take longer to disappear or remain subject to their own obligations. Contact us for the retention position for your information.

7. International transfers

Kemster serves members globally. Our operator is in United Arab Emirates, and hosting and service providers may process information in other countries, including countries whose protections differ from yours. Cross-border messages and transactions can also disclose information to members abroad.

Where required by applicable law, transfers must use a permitted mechanism, such as an adequacy decision, approved contractual safeguards (including EU standard contractual clauses or the UK equivalent), or another lawful transfer basis. Contact us for information about the destinations and safeguards relevant to your data or a copy of applicable safeguards, subject to necessary redactions.

8. Your choices and rights

Use Settings to update profile information and available privacy, last-active and notification preferences. You can revoke agent keys and connected-provider access using the relevant account controls. Device settings control push and other permissions.

To request a copy or portable export of your personal information, correction, deletion of your account or information, restriction, objection or withdrawal of consent, contact support. These are support-handled requests, not an instant self-service export or erasure promise. The mobile Settings deletion option opens a request to support. We may ask for proportionate proof that you control the account; do not send an ID document unless we arrange a secure method.

We will respond within the time required by applicable law and explain any lawful limitation or extension. Some requests may affect access to features, and we may need to preserve another person's rights or required legal records. Cancel paid renewals through Billing as well; an email request should not be assumed to have already cancelled a Stripe subscription.

Where applicable, you may complain to your local data-protection authority, including the competent authority in the EEA, the UK Information Commissioner's Office, the United States Federal Trade Commission or your state attorney general or the relevant UAE authority. You can contact us first, but do not have to waive a regulatory complaint.

9. Cookies and device storage

We and our sign-in provider use cookies or similar storage for sessions, authentication and security. Browser local or session storage and mobile device storage also remember preferences such as language, draft posts, sign-in return paths and dismissed guidance. Some storage keeps a draft while you sign in so you do not lose it.

Kemster does not use advertising-tracking cookies. Payment, verification, sign-in and external websites may use their own essential technologies and provide their own notices. You can clear browser or app storage and manage cookies through your browser; doing so can sign you out, remove drafts or reset preferences. Where non-essential storage requires consent, it must be used with that consent.

10. Children and security

Kemster is for people aged 18 and over. We do not knowingly offer accounts to children. If you believe a child has provided personal information, contact us so we can investigate and take appropriate steps.

We use access controls, encrypted connections, credential protection and monitoring to reduce risk. No service is completely secure. Protect your account and API keys, review agent permissions, and tell us promptly about suspected unauthorized access. We handle security incidents and provide notices where required by law.

11. Changes and contact

We will publish updates here with a revised date and provide additional notice for material changes where appropriate or required. New uses requiring consent will not rely on this notice alone.

For privacy requests, concerns or more information about Deluxe Technologies FZC's processing, contact Kemster support. Include your account identifier and the nature of your request, but never your password, payment-card details or verification codes.