Privacy Policy

Information Collection and Use

By default, the Service does not collect personal data beyond what is needed to keep it running securely and to enforce fair-use limits. Depending on how you use the Service, the following information may be collected:

• The pages and features of the Application you visit, and the time and date of your visit
• The operating system you use on your mobile device

The Application does not gather precise information about the location of your mobile device.

Account Information

If you choose to create an account, the Application collects:

• Email address and username (when registering with email and password)
• Profile information provided by Google or Apple when you sign in using those authentication services
• Profile avatar images you upload or generate within the Application

Account data is stored securely in the Service Provider's database, managed by Supabase (supabase.com). You may use the Application without creating an account; anonymous usage is tracked by a one-way hashed (HMAC-SHA256) representation of your IP address solely for the purpose of enforcing daily usage limits. Your raw IP address is never stored.

This same anonymous-tracking approach applies to the Chat page on this website: if you use it without signing in, your messages are processed by the same third-party AI infrastructure to generate a reply, and a one-way hashed representation of your IP address plus token usage counts are logged for analytics and to enforce a daily usage limit, exactly as described above.

Chat Messages and AI Processing

The Application is an AI assistant. Messages you send are processed by third-party large language model (LLM) infrastructure providers in order to generate responses. Specifically:

• Your chat messages may be transmitted to OpenRouter (openrouter.ai) and/or Hugging Face (huggingface.co), which route them to the appropriate AI model for a response. Please refer to those providers' privacy policies for details on how they handle data passing through their infrastructure.
• Chat history is stored on your device in encrypted form (AES-256-CTR). If you are signed in, it is also synced to your account so the same conversations are available in the Application and on this website's Chat page. Conversation titles and message contents are encrypted on your device before they are uploaded, so the database holds their titles and contents only as ciphertext.
• The key that encrypts your synced chats is held by the Service Provider on your behalf, wrapped by a master key that is not stored in the database. This means you never have to manage or remember a key, but it also means synced chat history is not end-to-end encrypted: the Service Provider is technically able to decrypt it. Message contents are not read or used for analytics.
• If you are not signed in, chats on this website's Chat page are not saved at all — they exist only in your browser tab until you close or reload it.
• Deleting a conversation while you're online removes it from your conversation list on each device signed into your account, but the synced copy isn't erased until you delete your account, and copies already stored on your other devices stay there (see "Data Retention Policy" below). Deleting your account deletes your synced conversations, including ones you had already deleted, from our servers.

Image Generation

If you use image or avatar generation features, the text prompts you provide are transmitted to Hugging Face (huggingface.co), which routes them to the image generation model to produce images. Please refer to Hugging Face's privacy policy for details on how they handle prompt data.

Memories

If you use the Memories feature, the memory entries you create are stored in the Service Provider's database (Supabase) and associated with your account. You may view, edit, or delete your memories at any time within the Application.

Optional Training Analytics

The Application may offer an optional, opt-in "Training Analytics" feature. If you choose to enable it, data you contribute through this feature is used to help improve KiwiMate's AI models. Because this data becomes part of an aggregate training/analytics dataset, once contributed it is not deleted — including if you later delete your account or turn the feature off. Opting out only stops future contributions; it does not retroactively remove data already contributed. This feature is off unless you actively opt in.

Usage Data and the Developer API Platform

The Application tracks the number of tokens (a measure of AI usage) consumed per request, per day. This data is stored in the Service Provider's database and is used to enforce daily usage limits (Kiwi Credits) and, for the website's Chat page, to understand overall usage as described above. It is not used for advertising or sold to third parties.

If you create a developer API key at kiwimate's Developers page, we also store the key (hashed, never in plain text after creation), the NZD credit balance associated with your account, and a record of API requests (timestamps, token counts, and rate-limit windows) needed to bill usage, enforce the 60 requests/minute rate limit, and detect abuse. We do not store the content of your API requests any longer than needed to generate and return a response.

Website Feedback and Issue Reports

If you submit feedback through this website, we collect the message, star rating, and an optional name you provide. If you report a bug through the "Report an Issue" page, we collect the title, description, an optional name and email address you provide, and your browser's user-agent string (to help diagnose the issue). This information is stored in the Service Provider's database/storage and used only to review feedback and fix reported problems.

Public Roadmap (Kanban Board)

The Application's public roadmap board is visible to anyone, including visitors who are not signed in. If you are signed in and submit a feature suggestion, your suggestion is displayed publicly on the board. We also record which account submitted it and that account's email address, for our internal reference only: neither is shown on the board or available to other users. Do not submit suggestions containing information you don't want displayed publicly.

Game Stats and the Streak Leaderboard

If you play games in the Application while signed in, we store what's needed for your game stats: your games won and played, your current and best daily win streak, the date of your last win, and your device's time-zone offset from UTC (not your location), so wins count towards the right calendar day.

Signed-in players are shown on a streak leaderboard that anyone can view, including people who aren't signed in or don't have a KiwiMate account. You're listed by default, but only after the Application has told you so with a one-time notice that lets you hide yourself straight away. Anyone viewing the leaderboard sees only:

• The username you chose. Never your real name or email address. If you haven't chosen a username, or it doesn't meet our naming rules, you appear as "Kiwi #" followed by four digits.
• Your rank, current and best win streak, games won, and games played.

The leaderboard never shows your email address, profile photo, credit balance, or location. You can hide yourself (you'll still see the leaderboard) or turn the leaderboard off entirely at any time in Settings → Game Settings, or with "Hide me" on the leaderboard itself.

People who aren't signed in see the top 50 players. That view is refreshed about every 15 minutes, so streaks, wins and games played there can be a little behind. Hiding yourself, turning the leaderboard off, removal by a moderator, or deleting your account takes you off it straight away (someone who already has the leaderboard open keeps seeing it until they refresh).

If you're signed in and report another player's name, we store the report (your account, the reported account, and the name as it was shown) so we can review it, and that name is hidden from your own leaderboard straight away while you're signed in. A name reported by several players may be hidden from everyone while we review it. Reports are used only for moderating the leaderboard. Reporting a name requires signing in.

Third Party Access

The Application uses the following third-party services, each of which may have access to certain data as described:

• Supabase — database, authentication, and file storage provider. Stores account details, memories, usage data, game stats and leaderboard settings, feedback, issue reports, and avatar images.
• GitHub — hosts our private issue tracker. Issue reports, including any name and email address they contain, are copied there so we can fix them.
• OpenRouter and Hugging Face — AI inference providers. Receive your chat messages to generate AI responses.
• Hugging Face — image generation provider. Receives text prompts when you use image or avatar generation features.
• Google / Apple — optional sign-in providers. Used only if you choose to sign in with Google or Apple.
• Vercel — hosts this website and provides cookieless, aggregate page-view analytics (Vercel Analytics) so we can see which pages are used. It does not set advertising or tracking cookies.
• Stripe — processes credit pack and subscription purchases made through this website's Store page. We do not receive or store your payment card details; see "Purchases" in our Terms & Conditions.
• Apple App Store / Google Play — if you make an in-app purchase in the mobile application, that purchase is processed entirely by Apple or Google. We do not receive or store your payment card details; see "Purchases" in our Terms & Conditions.

The Service Provider may also disclose information:

• As required by law, such as to comply with a subpoena or similar legal process
• When necessary in good faith to protect the rights, safety, or security of the Service Provider, users, or the public, or to investigate fraud
• With trusted service providers who work on the Service Provider's behalf, have no independent use of the disclosed information, and have agreed to adhere to this privacy policy

Cookies & Tracking Technologies

This website sets one cookie: geo-currency, a functional cookie that remembers the currency your prices should be shown in (detected from your country), so the Store page doesn't need to re-detect it on every visit. It expires after 30 days and is not used for tracking or advertising.

We do not run advertising or cross-site conversion tracking on this website, and we do not sell or share your data with advertisers.

Opt-Out Rights

You can stop all collection of information by the Application by uninstalling it. You may use the standard uninstall processes available as part of your mobile device or via the mobile application marketplace. If you have an account, you may also delete it at any time from within the Application, or contact the Service Provider to request deletion. You can also decline, or later turn off, the optional Training Analytics feature described above at any time (see that section for what happens to data you already contributed). To keep your username and game stats off the streak leaderboard, hide yourself or turn the leaderboard off in Settings → Game Settings; this takes effect immediately, for people viewing it signed in or not.

Data Retention Policy

We keep things simple: by default we don't collect data beyond what's needed to run your account. When you delete your account, your associated personal data on our servers (profile, memories, synced chat conversations including ones you had already deleted, game stats and leaderboard settings, leaderboard reports you made or that were made about you, and API/credit records) is deleted immediately, not just "in a reasonable time."

The Application also keeps a copy of your chat history on each device you use it on. Deleting a conversation, or using Clear Chat History, removes those chats from that device, although the home-screen widget can keep showing your latest message, and keeps a copy of your recent chat titles, until you next chat, or sign out or delete your account in the Application on that device. Signing out doesn't remove your chats from the device: they come back if you sign in to the same account there again, and you can delete them then. After you delete your account, whatever is left stays on each device until you uninstall the Application or clear its data there.

If you're signed in, the conversations you have are also synced to your account, with their titles and messages encrypted (details such as when each message was sent aren't; see "Chat Messages and AI Processing" above). Deleting a conversation doesn't erase the synced copy: it's marked as deleted, which takes it off your conversation list on your other signed-in devices (straight away, or when they next connect), and it stays on our servers until you delete your account. A copy already stored on another of your devices stays there until the Application is uninstalled or its data cleared on that device. If a deletion can't reach our servers, for example because you're offline, the conversation comes back the next time that device syncs.

Some data is kept after you delete your account. Data you've contributed through the optional Training Analytics feature (see above) is kept for model training; it isn't linked to your account, so it isn't deleted with it and we can't reliably tell which of it is yours to remove. Website feedback isn't linked to your account either. Issue reports are kept so we can fix the problems they describe: deleting your account removes a report's link to your account in our database, but the report, including any copy in our file storage or our private issue tracker on GitHub, still contains any name and email address it was sent with (reports sent from the Application while you're signed in include your account's email unless you replace it with a different address). Ideas you've suggested on the public roadmap also stay on the board, but deleting your account unlinks them from it and removes the email address recorded with them. If you'd like your account, feedback, issue reports or roadmap suggestions deleted, please contact the Service Provider at hello@kiwimate.net and they will respond in a reasonable time.

Children

The Application is not directed at, and is not knowingly used by, children under the age of 13. The Service Provider does not use the Application to knowingly solicit data from or market to children under 13, and does not knowingly collect personally identifiable information from them.

If you have reason to believe that a child under 13 has provided personally identifiable information to the Service Provider, please contact us at hello@kiwimate.net so we can delete it.

Security

The Service Provider is concerned about safeguarding the confidentiality of your information. Measures in place include: AES-256-CTR encryption for chat history, both on your device and for the synced copy (which is encrypted before it leaves your device, under a key wrapped by a master key that is never stored in the database), HMAC-SHA256 hashing of IP addresses (so the raw IP is never persisted), hashed storage of developer API keys (shown to you only once, at creation), HTTPS for all network communication, row-level security policies in the database ensuring users can only access their own data, and platform-native secure storage (iOS Keychain / Android EncryptedSharedPreferences) for encryption keys.

Changes

This Privacy Policy may be updated from time to time. The Service Provider will notify you of any changes by updating this page. You are advised to review this Privacy Policy regularly, as continued use of the Application constitutes acceptance of any changes.

Your Consent

By using the Application, you consent to the processing of your information as set forth in this Privacy Policy, now and as amended by the Service Provider. This Privacy Policy is governed by, and should be read in accordance with, the laws of New Zealand, including the Privacy Act 2020.