Book a call

Kyzeflo / Legal

Privacy Policy

What we do and do not collect. The short version: this website doesn't track you, and we only hold what you send us directly.

Last updated — 19 October 2026

  1. 01

    Who is responsible

    Kyzeflo ("we", "us") is responsible for the personal information described here. We are a software, AI and digital systems studio working from Bangalore, India.

    Privacy questions and requests go to admin@kyzeflo.com.

  2. 02

    This website doesn't track you

    We want to be specific rather than reassuring. We set no cookies of our own. The site runs no analytics, no advertising or tracking scripts, and no session recording. It stores nothing in your browser — no local storage, no fingerprinting. It contains no forms, so there is nothing on it to submit.

    Typefaces are served from our own domain rather than a font service, so simply reading a page does not make a request to any third party.

    This site is hosted on Firebase Hosting, a Google service. Google processes standard server logs in order to deliver the site and keep it secure — typically an IP address, the page requested and a browser user-agent string — and retains them on its own schedule. Where its platform requires a cookie for delivery or security, that cookie is strictly necessary and is not used to profile you.

  3. 03

    What we collect when you contact us

    If you email us we receive your address, your message and anything you attach. If you book a call we receive the details you enter into the scheduling service — typically your name, email address and chosen time, plus anything you add in the notes.

    That is the whole of it. We do not buy contact data, and we do not build profiles on people who have not contacted us.

  4. 04

    Scheduling and other third parties

    Calls are booked through Calendly, an external scheduling service. When you follow that link you are on their platform, and their privacy policy governs what they collect there. They act as a processor for the booking details they pass to us.

    Google provides our hosting, as described above. The client websites and profiles we link to from case studies are outside our control, and their own policies apply once you follow the link.

  5. 05

    How we use it

    To reply to you, to arrange and hold a conversation, to prepare a proposal if there is something worth building, and to keep our own records of the engagement. We do not use it for advertising and we do not sell it.

    Where the law requires a lawful basis, ours is your consent when you choose to contact us, our legitimate interest in responding and running a studio, performance of a contract once we are working together, and compliance with legal obligations such as tax records.

  6. 06

    Client data during an engagement

    This is the part that matters most for the work we do, and our commitments are the same ones stated on our homepage.

    We don't train our own models on your data. Where a project uses third-party AI services, we choose settings that keep your data out of their model training wherever the provider offers that. We keep only what the project needs. When it ends, we return or delete your data as agreed in writing, apart from backups that expire on their normal cycle and records the law requires us to keep. Access is limited to what the work needs, given to named people, and removed when the engagement ends. Where it's practical, we build in logging so you can see what ran and when.

    Where an engagement requires us to handle personal data belonging to your customers or staff, we do so on your instructions as a processor, under the terms of that engagement's written agreement.

  7. 07

    How long we keep it

    We delete enquiries that don't lead to work after about three months, unless you ask us to stay in touch. Records relating to an engagement are kept for as long as the engagement runs, and afterwards only where a statutory obligation — tax and accounting, principally — requires it.

    Client data handled during a build is returned or deleted at the end of the engagement as agreed in writing, apart from backups that expire on their normal cycle.

  8. 08

    When we share it

    We do not sell personal information and we do not share it for anyone else's marketing.

    We share it only with the service providers who help us operate — Calendly for scheduling, Google for hosting, our email provider and, during an engagement, the hosting, software and AI providers that project uses, as agreed with you — and only to the extent they need it; where a law or a court requires disclosure; and with your agreement, for example when you ask to be introduced to someone.

  9. 09

    International transfers

    We are in India and work with clients in the United States, the UAE and India. The providers we rely on — Google for hosting, Calendly for scheduling, and our email provider — operate global infrastructure, so information may be processed outside your country. Where it moves across borders we rely on the transfer safeguards those providers have in place.

  10. 10

    Security

    Access to client systems and data is granted per engagement, credentialed individually and removed when the engagement ends. We keep the number of people with access to the minimum the work requires. No system is perfectly secure, and we will not claim otherwise, but we will tell you without undue delay if something happens that affects your data.

  11. 11

    Your rights

    You can ask us what we hold about you, ask us to correct or delete it, ask us to stop using it, or withdraw a consent you gave. Write to admin@kyzeflo.com and we will respond within a reasonable period.

    Depending on where you live, you may have specific rights under Indian data protection law, the UK and EU GDPR, or the privacy laws of a US state. We'll handle those requests wherever you are, subject to any legal exceptions, and we will not treat you differently for making one.

  12. 12

    Children

    This site and our services are for businesses and are not directed at children. We do not knowingly collect information from anyone under 18. If you believe we have, write to us and we will delete it.

  13. 13

    Changes to this policy

    We may update this policy. The version published here is the one that applies, and the date at the top shows when it last changed. If a change materially affects how we handle information about you, we will make that clear rather than quietly amending the page.