Security
Security at Sika
Privacy is the product. This page explains how it is protected and how to help us keep it that way.
How Sika protects you
- End-to-end encryption. Messages, files and call audio are encrypted on your phone and decrypted only on the recipient's phone. Our servers cannot read them.
- Keys stay with you. Your identity key is created on your phone, and its private half never reaches a server. Messaging keys and payment keys are separate.
- Encrypted storage. Chats, contacts and files are stored encrypted on your phone. An optional PIN locks the app.
- Verified contacts. Compare a safety number with a contact to confirm that nobody sits between you.
- Signed releases. Every Android release is signed with one release key. The app checks an update before it installs it, and warns you if your copy was taken apart and signed again by someone else, with a button to the real download.
- Servers that carry, not read. Our servers carry sealed mail, wake your phone, relay calls, and keep locked copies of some files and video statuses for a short time so the other person can fetch them while your phone is off. They hold no keys and see no content of private chats, files or calls. Mail waiting for a phone is deleted once it is delivered, or after a limited time. Our servers can see who mails whom, when, and roughly how much. One opt-in exception: if a business on Chat Team turns on AI help in its staff inbox and a staff member presses Suggest a reply, the last few messages of that one chat go to an AI provider so it can draft a reply. Staff are warned before they turn it on, customers cannot use it, nothing is stored by us, and nothing is sent to the customer unless a person presses Send. The Privacy Policy lists how long each thing is kept.
- We tell you first. If you add a phone number or email, our servers keep a scrambled form of it and the Sika key it belongs to, so friends can find you. They still see no message, file or call. Some features need our servers to know more, for example who is on Sika, what is posted publicly, or where your cloud backup is. Private chats stay end-to-end encrypted, public content is kept clearly apart from them, and we update this page and the Privacy Policy before such a feature reaches you.
- Public content is public, and signed. Channels, forum topics, halls and market listings are stored on our servers and the app marks each one Public. What is posted is signed by whoever posted it, so every phone that shows it can check that it was not changed. Making a channel needs a verified phone number and email. People can report public content, and enough reports hide it until our reviewers look. Near me uses only the town or area you type, never your location. Joining a hall is counted, and who joined is never shown. Offers, chats and payments with a seller never pass through the market server.
- Plans, marks and receipts you can trust. Your plan, a business mark and your receipts are signed by Sika and checked by your phone, so they cannot be copied from another account or made up. A plan is only a flag: it is never a key and never a copy of a message. Safety and privacy features are never paid.
- Payments are confirmed with our payment partner. Premium, Rubies and Store purchases are credited only after our payment partner confirms the exact payment. What a phone or a web page says is never enough, and each payment counts once. Sika never sees your card or mobile money details.
- Protected orders keep a tamper-evident history. Each step of a protected order is recorded so that a changed or removed entry is caught. Delivery photos stay on the phones; only their fingerprints are kept with the order.
- Disputes never have only one voice. A community panel, if the deal names one, reads what the two people wrote and never sees the chat or the photos. Either person can take its decision to Sika, which decides last.
- How Sika staff are held back. Each member of staff sees and does only what their role allows. Sensitive actions need extra approval, large payouts need a second person, and every action is written to a log with the reason.
- Dispute photos and videos, only if you share them. When an order is in dispute you may choose to show your photos or a short video to the Sika reviewer. Each file is locked on your phone before it leaves, only approved reviewers can open it, nobody who can read our servers can, and each opening is logged. We keep only the locked file, for a limited time. Saying no leaves the dispute to the written reasons and the history.
- Sponsored cards are counted, not tracked. A promotion is chosen by the town and topic you are looking at, never by anything about you. We count shows and taps for each promotion by day; a scrambled one-day code stops one phone counting twice and is deleted within a day. The business that paid sees only totals, never who saw, tapped or reported. Kliqa, when it books a promotion, gets only its status and totals back.
- The verified mark is looked up, not logged. When a post shows a verified organisation mark, your phone asked for the author's public key only. We keep no list of who asked, and the answer is the registered name and country, nothing about you.
- Notice views are totals. When Sika counts how many people opened one of its own notices, the code used to count a phone once is scrambled, kept for that day only and deleted with its random value when the day ends. Sika sees a number for each notice, never who. Nothing is sent if your read receipts switch is off.
- Bluetooth messages use one-time keys. With the Bluetooth backup on, a contact seals each Bluetooth message to a one-time key you shared, and your phone destroys that key when the message is opened. A copy of your phone taken later cannot open a message you already read. This is only for the Bluetooth route; it has not yet been tested on two phones.
- Rubies. Every Ruby in or out is recorded in a tamper-evident history that is checked regularly. A gift comes with a receipt your phone verifies, so nobody can fake one. Rubies cannot be cashed out or sent to another balance. A refund is a new entry, never a deleted one.
- Video statuses and bigger files, locked on your phone. A video status or a larger chat file is encrypted on your phone before it is uploaded, and only the locked copy is stored for a limited time. The key travels only inside the chat and never reaches our servers. The receiving phone checks the file before opening it.
- Public lives are public. A live from a channel, hall or shop is for everyone, so it goes through our media server in the clear and is labelled Public. Private calls and private lives stay end to end encrypted. Viewers get a ticket that can only watch, and every comment is checked by our server.
- Big group calls stay end to end. A larger group call goes through a call server that forwards each person's sound and picture. Every frame is encrypted on the phone and shared only inside the group, so the server forwards what it cannot open.
- Backups only you can open. A backup is a file locked with a code you hold, whether you keep it yourself or in Sika cloud. We never receive the code, and attempts to find a cloud backup are limited.
- Automatic backup keeps the code on the phone. If you switch on daily backup, the code stays in your phone's secure storage so the phone can lock each new backup. It is never in the backup file and never sent to us. Switching it off, or deleting the cloud copy, forgets it.
- GIFs go through us. Your phone never talks to the GIF partner. Our server does, so the partner sees our server and the words searched, not you or your chat. A GIF you send is an ordinary encrypted file.
- Sika Chat, a chat box for websites. A visitor chats through a small window that runs on sikaos.app, so the website itself cannot reach the visitor's messages. Messages are sealed to the business, so our servers carry only ciphertext, and only the websites the business named can show the window. The visitor's data stays in that browser and is cleared when they clear site data.
- Reactions on public posts. A reaction goes to our servers with a request signed by your key, and only a verified phone number or email can react. We keep your key, the emoji and the item, and show other people only the counts. Reactions in private chats travel end to end encrypted like any message.
- Second devices keep their own keys. A second phone or a computer makes its own key, and your main key never leaves your main phone. A contact's phone accepts mail only from devices on your latest signed list, and a device you remove can never be added back. The list shows how many devices you have and what they are called, never a message, a contact or a private key.
- Two-step verification against SIM swaps. If you set a two-step PIN, your phone number can move to another phone only with that PIN, even when someone has your SIM. Wrong tries lock the number for a time. Your messages never depended on your number: your Sika key is your identity, and it stays on your phone.
- Business notices are not private chats. When a business you agreed to hear from sends you a notice (an order update, a login code, or an offer if you turned offers on), the notice passes through a Sika service that checks it against wording Sika approved and counts it. That service can read the notice. It is labelled Business notice in the app and kept apart from your private chats, which stay end to end encrypted and are never read. You can stop any business, or any kind of notice, at any time, and it stops at once. Replies you write go to the business as your own private message.
- Developer webhooks are signed. Messages SikaPay sends to a developer's server are signed so the developer can check them, and are sent only to public https addresses.
Report a vulnerability
We welcome reports from security researchers. If you believe you have found a vulnerability in a Sika app, a Sika service or this website, email security@sikaos.app.
Please include what you found, the steps to reproduce it, and the impact you believe it has. Encrypt sensitive details if you can, and ask us for a key.
What to expect from us
- We acknowledge your report within three business days.
- We keep you informed while we investigate and fix the issue.
- We credit you in our release notes if you wish, once the fix is available.
- We will not take legal action against research carried out in good faith under this policy.
What we ask of you
- Test only with accounts you own, and do not access, change or delete other people's data.
- Do not run denial-of-service tests, spam, or social engineering against our team or users.
- Give us reasonable time to fix the issue before you disclose it publicly.
In scope
The Sika apps, the services behind them, and this website. Reports about third-party services should go to their operators.