Kyro markKyroAutomate repetitive business tasks in Kenya and beyond.
Log inRequest a quote

Legal

Privacy Policy

This policy explains how Kyro collects, uses, stores, and protects personal data when users browse AI tools, create accounts, request services, or engage with subscriptions.

Platform useBilling termsUser responsibility
By creating an account, placing an order, subscribing, uploading files, or continuing to use the platform, a user acknowledges these terms and policies as part of the service relationship, subject to any non-waivable rights that apply under local law.
Use Project DeskReview pricing

Why this page matters

It explains the rules, limits, payment framing, and responsibilities behind the platform in a calmer structure.

What to look for

Start with account use, billing, and user-review responsibility before moving into liability and dispute handling.

Best next step

Use these terms as the trust framework, then move back into the service, tool, or request path that fits your task.

Information we collect

  • Account information such as email address, encrypted authentication tokens, profile preferences, and security-related account metadata.
  • Marketplace usage information such as viewed pages, referral context, approximate location signals, device characteristics, and engagement analytics including time spent on pages.
  • Transactional, security, and operational records needed for billing reconciliation, fraud prevention, access control, support, dispute handling, and platform protection.

Analytics, location signals, and browsing insight

  • Kyro may use first-party analytics and third-party analytics tools to understand website traffic, route performance, on-site engagement, and user journeys across the marketplace.
  • Approximate location data may be inferred from IP-derived infrastructure signals, deployment geo headers, browser locale information, time zone, and related technical indicators rather than precise GPS tracking.
  • Browsing analytics may be surfaced to administrators in dashboard reporting for operations, performance improvement, fraud prevention, order triage, marketing evaluation, and marketplace optimization.
  • Use of the website after notice through these policies may be treated as acknowledgement that such operational and security monitoring is part of the service, subject to consent requirements that cannot be waived under applicable law.

Lawful basis and global privacy alignment

  • Kyro may rely on consent, contractual necessity, legitimate interests, or legal obligations depending on the interaction.
  • Users in the European Economic Area, United Kingdom, and similar jurisdictions should receive transparency, access, correction, deletion, and portability support where required.
  • Users in California, selected United States states, Australia, and African jurisdictions may also have statutory privacy rights that should be operationalized before launch.

Uploads, prompts, and business information

  • Files, prompts, briefs, and business information submitted through the platform may be processed for delivery, moderation, abuse prevention, malware screening, operational review, and service improvement, subject to contractual confidentiality commitments where applicable.
  • Users should not submit material unless they have the right to do so and understand that no online platform can guarantee absolute confidentiality, uninterrupted availability, or immunity from unauthorized third-party activity.
  • Where sensitive, regulated, or third-party material is involved, users remain responsible for obtaining permissions, anonymizing data where required, and ensuring lawful cross-border transfer before submission.

Retention and security

  • Personal data and browsing analytics may be retained only for as long as reasonably necessary for business, security, tax, dispute, performance, and legal compliance purposes.
  • Supabase, hosting providers, and payment partners should be configured with least-privilege access, secure credential rotation, and audit logging where possible.
  • No internet-facing application can guarantee absolute security, so incident response and breach notification procedures should be prepared in advance.