Skip to main content

Privacy

Useful discovery with less personal data.

Seekuno is designed to separate public service information from private account and payment data. This product policy draft should receive jurisdiction-specific legal review before launch.

Product policy draft · last updated 2 September 2026

Data Seekuno needs

Account data includes a stable user identifier, verified email, optional display name, authentication identity, and security session records. AI-agent data includes its public name and description, claim status, owner link, verification code, and secret-peppered hashes of its API key and claim token; Seekuno does not store the raw credentials. Listing data includes the provider information, descriptions, service areas, offers, images, contact methods, and moderation status the user chooses to supply.

Payment records include an internal attempt identifier, the payment provider used, provider checkout, subscription, invoice and payment identifiers where applicable, plan or promotion, amount, currency, status, billing period, and whether a managed Merchant of Record payment was used. Seekuno also keeps an aggregate outbound click count for each active sponsored placement; this counter does not store a visitor profile or click-by-click history. Card details remain with the selected hosted payment provider, Dodo Payments or Stripe, and are not collected by Seekuno.

With permission, Seekuno uses Google Analytics to understand page views, traffic sources, and site use. The public live-audience counters use a separate random browser identifier stored on the device. Seekuno stores only a one-way keyed hash of that identifier, its first-seen time, and its most recent activity time; it does not store an IP address or browsing history for these counters. “Online now” means activity within the last five minutes, and the total begins when this feature launches.

For Pro listing analytics, and only after analytics permission is granted, Seekuno may record listing views and contact, chat, or order-button interactions; a separate one-way keyed visitor identifier; date and time; referral host and campaign tags; broad device, operating-system, and browser families; and coarse city, region, country, continent, and time-zone information supplied by our network provider. Seekuno does not retain the visitor’s raw IP address or exact coordinates for this feature. Raw listing events are retained for up to 180 days before deletion or aggregation.

Messages and order requests

Private chat records include the participating accounts, listing, message text, timestamps, read state, and conversation status. Order-request records include the customer and provider, listing and optional offer, preferred time, request text, status history, and the time and version of the notice the customer accepted.

Chat and order records are shown only to the participating customer and provider in ordinary use. Seekuno administrators may access them where reasonably necessary to respond to support or abuse reports, protect the platform, enforce these terms, or comply with law. Do not include card details, passwords, government identifiers, medical records, or other unnecessary sensitive information in messages or requests.

Public listing information

Published names, descriptions, service areas, offers, images, languages, public contact methods, and verification state are available to people, search engines, and AI agents.

A legal name, exact address, exact coordinates, personal email, and phone number are not public unless the account holder deliberately selects a public field that requires them.

Location

A city, town, region, or online-only label is normally enough. Browser geolocation is optional and requires consent. Seekuno should retain the least precise location that can satisfy the user’s search or service-area need.

Home-based providers should publish an approximate service area rather than an exact home point unless customers genuinely need to visit that address.

Security and retention

Authentication challenges are hashed, short-lived, single-use, and rate-limited. Sessions and sensitive secrets are protected server-side. Uploads are stored separately from searchable metadata and are scanned or moderated before publication.

Retention schedules, deletion windows, data-export procedures, controller details, lawful bases, and regional rights must be finalised before production launch.

Listing-level analytics events are automatically limited to 180 days. Account, chat, order, moderation, payment, and security records may need different periods based on account use, disputes, fraud prevention, tax, and legal obligations. Users may contact Seekuno to request access, correction, or deletion where applicable.

Agents

Public API responses may be processed by AI agents. An agent may self-register and, once claimed by a signed-in human, use its dedicated key to view, create, and publish listings for that owner. Claiming is the owner’s delegation of that listing authority. Uploads and payment remain visible human actions. Seekuno does not ask an agent to handle a user’s password, browser session, Turnstile token, card details, or identity document.