Kinstap Privacy Policy
Version 1.1 · Updated 26 October 2026 · Proposed effective date: 26 October 2026
1. Who we are
Kinstap is owned and operated by Meclon Tax and Consultancy Limited (“Meclon”, “we”, “us”). Meclon determines how and why the personal data described in this policy is processed and acts as the data controller where applicable.
Our business address is Emmanuel House, Suite 14C, Ongata Rongai, Kenya. Our postal address is MPOST 254708552857-00511, Ongata Rongai. You can contact us at privacy@kinstap.com or through Kinstap Support in the app.
Our public website is kinstap.com. Public legal and privacy information is available through web.kinstap.com.
We are responsible for complying with the Kenya Data Protection Act, 2019 and other data-protection laws that apply to our processing. Collecting limited information does not automatically exempt us from applicable legal obligations.
2. The short version
- No account phone number or email required. You can create and use a Kinstap account without providing a phone number, email address or legal name. Some optional payment processes may involve additional information.
- Pseudonymous identity. Your handle and display name may be a nickname or pseudonym. Kinstap does not verify your real-world identity as a general account-registration requirement.
- Encryption. Supported private communications are designed to use end-to-end encryption so that only authorised member devices can decrypt their content when the relevant protections operate as intended.
- Your keys and recovery phrase. Kinstap is designed so that identity private keys, device keys and your recovery phrase remain under device-side control rather than being provided to Kinstap's servers. Protect your phone and recovery phrase carefully.
- Metadata still exists. To operate and protect the service, we process information such as handles, device identifiers, connection requests, routing information, network addresses and service activity. Section 5 explains this in detail.
- Kinstap Official and Kinstap Support. These are communications with Kinstap, not private end-to-end encrypted conversations with other users. Their contents may be accessible to authorised personnel.
- Payments. Payment providers process the information necessary for the payment method you select. We retain transaction information required to manage subscriptions, support contributions and legal records.
- No data sales or advertising. We do not sell personal data or use it for advertising. The app is designed without advertising or third-party advertising trackers.
- Security is not absolute. Encryption and other safeguards reduce risks but cannot guarantee that every device, feature, communication or account will remain secure under every circumstance.
3. How Kinstap is designed
Kinstap follows a device-first approach intended to minimise the information available to our servers.
Your phone stores supported conversations, media and cryptographic material locally. Supported private communications use end-to-end encryption. Our servers coordinate connections, route encrypted information and provide other services necessary to operate Kinstap.
The application uses the Messaging Layer Security protocol (MLS, IETF RFC 9420) through the OpenMLS library for supported conversations and Circles. The protection available depends on the feature, the participating devices, the current software and the correct operation of the applicable cryptographic and authorisation controls.
Encryption does not mean that every category of information is hidden from Kinstap. Our servers must process certain account, routing, delivery, payment and operational information to provide the service.
4. What is encrypted and what is not
The following describes the intended protection of supported features. It is not a claim that every possible device, implementation path or software version has been independently audited.
| Information or feature | Intended protection | Information Kinstap may process |
|---|---|---|
| Direct Chats and Circle messages | End-to-end encryption for supported conversations | Encrypted content, size, delivery timing, sender-device and routing information |
| Chat attachments | Encryption for supported attachments | Encrypted data, size, delivery and storage information |
| Moments and comments | Encryption for supported shared content | Encrypted objects, sizes and associated service metadata |
| Status and presence | Encryption for supported sharing with connections | Routing, delivery and other necessary operational metadata |
| Profile photo, bio and country | Designed to be shared through protected communications with accepted connections | Related encrypted traffic and operational metadata; confirm the current implementation and storage behaviour |
| Voice and video calls | Encrypted call media and protected call signalling, according to the supported call path | Connection information, network addresses, participants, timing and traffic metadata |
| Circle group calls and Live | Designed to protect media content while allowing the relevant servers to coordinate and relay sessions | Session participation, routing information, timing, packet characteristics and other information needed to operate the feature |
| Kinstap Vault backups | Designed to store encrypted backup material that Kinstap cannot decrypt through ordinary service operations | Encrypted objects, sizes, dates and storage metadata |
| Handles and display names | Not end-to-end encrypted | Account and public-profile information required to operate the service |
| Connection requests | Not end-to-end encrypted | Requesting identities, outcomes and relevant timestamps |
| Circle names in invitations | May be visible to the service while invitations are delivered | Circle name and delivery information |
| Kinstap Official and Kinstap Support | Not end-to-end encrypted in the same way as private user communications | Message content accessible to authorised personnel |
| Reports | Not end-to-end encrypted | Report content and associated information |
| Payments and subscriptions | Processed through the applicable payment and service controls | Transaction references, amounts, statuses, provider references and subscription records |
End-to-end encryption is designed to prevent the service from reading supported protected content in ordinary operation. It cannot protect content displayed on a compromised or accessible device, information a recipient has copied, or information that a particular feature must process outside the protected communication.
For details about security controls and their limitations, read Security at Kinstap.
5. Information we process
5.1 Account and identity
We process information needed to create and operate your Kinstap identity, including:
- Handle and display name: the identifiers you choose to use in Kinstap. Your display name need not be your legal name and does not have to be unique.
- Public keys and identifiers: public cryptographic keys, internal identity identifiers and device identifiers needed to identify and authorise accounts and devices.
- Device information: device registration, authorisation status and relevant activity timestamps.
- Profile information: optional information such as a profile photo, bio or country, subject to the current feature's implementation and sharing settings.
- Registration and activity timestamps: information needed to operate the service and display applicable account information.
Kinstap does not generally require your phone number, email address, contacts or legal name to create an account. Payment-related exceptions are described in Section 5.8.
Search and discovery controls, including any limits on search results or request rates, are used to help operate the service and reduce abuse. The exact behaviour is governed by the current app and server implementation.
5.2 Connections and Circles
We process connection requests and their outcomes so that the service can manage relationships and apply the access rules for Direct Chats.
This can include:
- The identities involved in connection requests;
- Whether requests were accepted, declined or withdrawn, and relevant timestamps;
- Conversation and Circle routing identifiers;
- Device and membership information needed to route communications; and
- Circle names where required to deliver invitations.
This information helps operate the service but may reveal aspects of your relationships and activity. End-to-end encryption does not necessarily hide these operational records.
5.3 Encrypted messages and files in transit
Kinstap processes encrypted information to deliver communications between authorised devices. Encrypted content may remain temporarily on servers or in storage while delivery is pending.
Retention periods depend on the type of information, delivery status and applicable service configuration. The intended retention periods for message and file delivery are described in Section 9. They should be interpreted subject to actual system behaviour and any applicable legal retention requirement.
Once information has been delivered or expires, deletion from the service does not erase copies that recipients have already saved or that may remain in device backups or other systems outside Kinstap's control.
5.4 Kinstap Vault
If you use Kinstap Vault, a Kinstap Plus feature, encrypted backup objects are stored through our storage provider.
Vault is designed so that the stored backup content is encrypted and unavailable to Kinstap in readable form through ordinary service operations. We may process object sizes, dates, account associations, storage usage and other information necessary to operate Vault.
Backup availability, included content and successful restoration depend on the applicable version, the data types supported, storage availability, the integrity of the backup and the recovery material available to you.
Do not assume that every message, media item, setting or other item is backed up. Review the functionality available in your version and keep your recovery phrase safe.
5.5 Voice, video calls and Live
Kinstap processes information required to establish, coordinate and deliver supported calls and Live sessions.
Depending on the connection path, this can include:
- Network addresses and connection information;
- Session participants and room membership;
- Session start and end times;
- Traffic volume, packet sizes and timing; and
- Operational information required for routing, admission, moderation and session management.
Supported call media is designed to be encrypted so that relay infrastructure cannot decrypt the content when the relevant protections operate correctly. This does not mean that the service receives no call metadata.
We do not intend to record calls as a routine service feature. Any claim about the absence of all call recordings or the exact retention of call metadata remains subject to the current implementation and operational configuration.
5.6 Notifications
If you enable push notifications, your device may register a push token with Google Firebase Cloud Messaging.
Push services are used to wake or notify the app. The information sent through them depends on the notification implementation. We aim to minimise the content included in push messages and avoid exposing private conversation content through notification payloads.
When the app receives a notification, it may contact Kinstap to fetch the relevant information. Firebase and other notification infrastructure may process device and delivery metadata under their applicable terms.
5.7 Kinstap Official, Kinstap Support and reports
Kinstap Official is the service identity used for official announcements. Kinstap Support is used for support conversations with Kinstap.
These communications and reports are not treated as private end-to-end encrypted conversations between users. Their contents may be stored in readable form so that authorised personnel can provide support, investigate reports and operate the service.
We may record the staff identity, role, reason and time associated with administrative actions. The app may display the service identity rather than the individual staff member.
Official announcements may be targeted using limited account and service information, such as plan status or account activity, where the relevant feature is enabled. We do not use end-to-end encrypted message content to target advertising. We do not use personal data for advertising.
5.8 Kinstap Plus, payments and Support Kinstap
Payment methods available to you depend on your location and the payment options configured for Kinstap.
- Paystack: where available, card payments are processed through Paystack. You enter payment details in the provider's payment interface rather than providing your full card number or card security code to Kinstap.
- M-Pesa: for eligible customers in Kenya, the app may ask for a Safaricom phone number to initiate a payment prompt. That number is provided to Safaricom for the payment process. Kinstap is designed not to retain the number after it has been used for that purpose.
- Payment credentials: Kinstap will not ask you to disclose your M-Pesa PIN or card security code to staff. Enter sensitive payment credentials only in the official interface of the relevant provider.
- Payment records: we process transaction references, amounts, currencies, exchange-rate information where applicable, payment status, provider references, plan information, refund or chargeback status and the Kinstap identity associated with the purchase.
- Email for card payments: if the payment provider requires an email address, the payment process may use an address you supply or a pseudonymous address, depending on the supported flow and configuration. The provider may process that address under its own privacy terms.
- Support Kinstap: voluntary contributions may be associated with the contribution amount, transaction status, receipt reference, attribution preference and any supporter badge you choose to display.
Kinstap is designed to verify payment outcomes with the relevant provider before granting the corresponding subscription or support entitlement. A return from a payment page or an unverified notification is not, by itself, proof of successful payment.
Prices, currencies and payment options are shown in the app before you confirm a transaction. Provider fees, payment handling and refunds are subject to the applicable provider terms and Kinstap's policies.
5.9 Security and operational records
We process certain information to secure, maintain and troubleshoot the service. This may include:
- Device registration and revocation events;
- Account deletion and security-related events;
- Payment verification and administrative audit events;
- Short-lived values used to prevent replay of requests;
- IP addresses and other network information;
- Request method, path, status, timing and service diagnostic information; and
- Information required to investigate abuse, impersonation or suspected security incidents.
We aim to avoid including message content, secrets or sensitive payment callback credentials in routine request logs. The information actually recorded and retained depends on the relevant service configuration.
5.10 Information designed to remain under your control
Kinstap is designed so that private cryptographic keys and the recovery phrase remain under device-side control. Message history, media libraries and other local information may also be stored on your phone.
The precise information held locally or remotely depends on the feature. Some encrypted material must be transmitted or stored temporarily to deliver communications or operate Vault.
If you want to understand the protection for a particular feature, consult the current Security page and the feature information in the app.
6. Why we use information and our legal bases
We use information for purposes such as:
| Purpose | Potential legal basis, depending on the processing |
|---|---|
| Create and operate accounts and devices, route communications, provide calls and deliver notifications | Performance of our contract with you |
| Manage connections, Circles, search and service functionality | Performance of our contract with you and, where applicable, legitimate interests |
| Protect the service, prevent abuse and investigate security events | Legitimate interests and legal obligations where applicable |
| Process subscriptions, payments, refunds and support contributions | Performance of our contract with you and applicable legal obligations |
| Respond to support requests and reports | Performance of our contract with you, legitimate interests and legal obligations where applicable |
| Send optional product updates | Consent where required |
| Maintain financial records and meet tax, accounting or other legal requirements | Legal obligation |
The appropriate legal basis depends on the nature of the processing and the law that applies. Where consent is required, it can be withdrawn subject to the applicable legal and technical limits.
We do not sell personal data or use it for advertising. We do not make decisions about you solely through automated processing that produce legal or similarly significant effects, except where permitted by applicable law and subject to any required safeguards.
7. Who at Kinstap can access your information
Kinstap uses a separate administrative system with role-based access controls and additional authentication safeguards.
Authorised personnel may access the operational information required for their roles, including account and device status, payment records, support conversations, reports and relevant security records.
Private end-to-end encrypted content is designed to remain inaccessible to staff through ordinary administrative tools. This statement does not mean that every category of user information is inaccessible to staff. Information submitted through Kinstap Support, Kinstap Official interactions, reports and other readable service functions may be available to authorised personnel.
Administrative access controls and audit logs are intended to reduce misuse and support accountability. They cannot guarantee that unauthorised access or security incidents will never occur.
8. Service providers and international transfers
Kinstap relies on service providers to operate parts of the service. Depending on the feature and configuration, providers may include:
| Provider | Purpose | Information potentially processed |
|---|---|---|
| OVHcloud | Application hosting, databases and communication infrastructure | Encrypted data, account and routing metadata, network information and operational records |
| OVHcloud Object Storage | Storage of encrypted Vault backups and supported files | Encrypted objects, object metadata and storage information |
| Paystack | Eligible card payments | Payment information, transaction references and information required by the provider |
| Safaricom | M-Pesa payments in Kenya | The payment number, amount and reference required to initiate and process a payment |
| Google Firebase Cloud Messaging | Push notifications, when enabled | Device push token and notification delivery information |
The providers used and the information they process may change as Kinstap develops. Each provider may process information under its own contractual terms and privacy documentation.
Some providers may process data outside Kenya. Where applicable, we use the safeguards required by the data-protection laws that govern the transfer. The existence and adequacy of any particular transfer safeguard must be assessed for the relevant provider and processing activity.
We may disclose information to public authorities where legally required or otherwise permitted by applicable law. We seek to limit disclosures to the information lawfully covered by the request. End-to-end encryption may prevent us from providing the readable content of properly encrypted communications or backups, but it does not prevent us from providing metadata or other records we hold where disclosure is lawful.
9. How long we keep information
We retain information for the period needed for the purposes described in this policy, subject to applicable law, security needs and operational requirements.
The following are the intended retention rules for the categories listed. They must be kept aligned with the actual production configuration.
| Information | Retention approach |
|---|---|
| Encrypted messages in transit | Intended to be erased after recipient devices confirm receipt, with a target of about one hour after all confirmations; undelivered messages are subject to an expiry period, currently intended to be 14 days |
| Encrypted files in transit | Retention depends on file type and delivery path; applicable expiry rules may differ for mailbox files and larger attachments |
| Vault backups | Retained according to the account, backup and storage lifecycle; do not assume expiry when a subscription ends unless the applicable feature explicitly provides for it |
| Handle | Retained while the account exists; after release or deletion, reuse may be delayed under the applicable handle-release policy |
| Display name and profile information | Retained according to account and feature settings, until changed or deleted where applicable |
| Device and identity records, push tokens, preferences and badges | Retained while needed to operate the account, subject to deletion and applicable exceptions |
| Device session records | Retained according to the applicable session-retention policy |
| Invitation and connection records | Retained as needed to operate the service and prevent abuse, subject to applicable deletion rules |
| Payment and subscription records | Retained as required for tax, accounting, refunds, chargebacks and other legal obligations |
| Security audit events and reports | Retained as needed for security, abuse prevention, investigations and accountability, subject to applicable law |
| Server request logs | Rotated or deleted according to the operational logging policy |
Some records may be retained after account deletion where necessary for legal compliance, security, dispute resolution or the purposes described in this policy. Where feasible and appropriate, retained records are separated from direct account identifiers.
We will update this section if actual retention practices materially differ from the periods currently documented. If a precise retention period is important to your decision to use Kinstap, contact us for clarification.
10. Deleting your account
You can request account deletion through the app using the account-deletion function available in your version.
Deletion is intended to remove the account and associated server-side information identified by the applicable deletion process, including relevant device records, undelivered encrypted messages and files, Vault backups, push registrations, support conversations, preferences, badges and display information.
Deletion may also release your handle under the applicable handle policy.
Some information may remain for a limited or legally required period, including financial records, security records or information needed to establish, exercise or defend legal claims. Information already downloaded or copied by other users cannot necessarily be erased from their devices by deleting your account.
The app is also designed to remove local account data as part of the deletion process. The exact outcome depends on the version and successful completion of the deletion operation.
For further information, see Account and data deletion, provided that this public URL has been verified and published.
11. Your recovery phrase
Your recovery phrase is sensitive information used in the process of recovering your Kinstap identity on a new phone.
Kinstap is designed not to receive or store your recovery phrase. We cannot recover an identity for you if the required recovery material is lost and no supported alternative recovery method is available.
Never disclose your recovery phrase to anyone, including someone claiming to represent Kinstap. Keep it in a secure location and be aware that anyone who obtains the necessary recovery material may be able to compromise your identity.
Recovery behaviour and the information restored depend on the current app version, the available recovery material and the backup features you have used. A successful identity recovery does not necessarily mean that every message, media item, setting or other item has been restored.
12. Security and personal-data breaches
We use technical and organisational safeguards intended to protect information against unauthorised access, loss, alteration and disclosure.
These safeguards include encryption for supported communications, access controls, device authorisation, secure connections, administrative restrictions and security monitoring where implemented.
No system is perfectly secure. A vulnerability, compromised device, software defect, unauthorised access or service failure may still occur.
If a personal-data breach occurs, we will assess and respond to it and notify affected users, the relevant authority or other parties where and as required by applicable law.
For more information, read Security at Kinstap.
13. Children
Kinstap is intended for people aged 18 and over. We do not knowingly permit children to create accounts or knowingly collect personal data from children in violation of applicable law. Kinstap does not necessarily verify a user's age during registration.
If you believe a child is using Kinstap contrary to this policy, contact Kinstap Support so that we can assess the report and take appropriate action.
14. Your data-protection rights
Depending on your location and the law that applies, you may have rights to:
- Be informed about the processing of your personal data;
- Access personal data concerning you;
- Request correction of inaccurate information;
- Request deletion, restriction or objection to processing where applicable;
- Request data portability where provided by law;
- Withdraw consent where processing relies on consent; and
- Complain to the relevant data-protection authority.
Under Kenya's Data Protection Act, 2019, you may be able to lodge a complaint with the Office of the Data Protection Commissioner of Kenya.
Much of your private content is designed to remain on your device and may not be accessible to Kinstap in readable form. For information we hold, contact us using the details in Section 17. Because Kinstap does not rely on conventional email-and-password account login, we may ask you to submit a request through the app or otherwise provide appropriate verification that you are entitled to make it.
We will respond to requests within the timeframes required by applicable law. The availability of a right and any lawful exceptions depend on the relevant circumstances.
15. Cookies and web technologies
The Kinstap app is designed without advertising or third-party analytics trackers.
Public web pages may use essential technical features necessary to deliver and secure the site. The staff-only Admin Dashboard may use session technologies needed for authenticated administrative access.
The actual cookies, scripts and third-party resources used on each website depend on its deployed configuration. We will keep this section aligned with the public website and Admin Dashboard as they change.
16. Changes to this policy
We may update this policy as Kinstap's features, service providers, legal obligations and data practices change.
We will publish the updated version with a new date. Where required by law, or where a change is material, we will provide notice through Kinstap Official or another appropriate channel and obtain consent where necessary before applying the change.
The effective date will be stated when the revised policy is approved for publication. The proposed date above must not be treated as proof that this version has already taken effect.
17. Contact
For privacy questions or to exercise your data-protection rights, contact us by email or through Kinstap Support in the app.
For email requests, use the subject “Privacy request.” If you do not have a Kinstap account, email is the contact method available to you.
| Contact detail | Information |
|---|---|
| Owner and operator | Meclon Tax and Consultancy Limited |
| Business address | Emmanuel House, Suite 14C, Ongata Rongai, Kenya |
| Postal address | MPOST 254708552857-00511, Ongata Rongai |
| privacy@kinstap.com | |
| In the app | More → Support & legal → Kinstap Support |
| Public website | https://web.kinstap.com/ |