Legal
Privacy Policy
Effective 2026-10-23
Sika is built so that we hold as little about you as possible. This policy explains what we do process, why, and the choices you have.
1. Who we are
Sankofa Network ("Sika", "we", "us") provides the Sika messaging app, the relay and push services that support it, and this website. We are the controller of personal data described in this policy. Our address is Akwa Ibom State. You can reach us at privacy@sikaos.app.
2. The short version
- Messages, photos, files and call audio are end-to-end encrypted. We cannot read or listen to them.
- You do not need a phone number or email address to use Sika. You can add one if you want friends to find you or want to move to a new phone.
- If you add a phone number or email, we keep a scrambled form of it and which Sika key it belongs to. We never see your messages.
- Market listings you post to the town market are public and stored on our servers. Offers, chats and payments with a buyer stay private as before. Browsing the market needs no account and is not logged.
- Channels are public. A channel you make and what you post in it are stored on our servers and anyone can read them, without an account. Which channels you follow is stored with your Sika key. To make a channel or a podcast you need both a verified phone number and a verified email, and to post you need one of them; the channels service only learns which of the two you verified, never the number or email. Your private chats never go to the channels service. Posts you save, and the copy of channels kept for reading offline, stay on your phone. A post you share into a chat travels end to end like any message.
- Hall forums are public. Topics and replies you write in a hall's forum, including up to four pictures on a topic and voice replies, with your Sika key and when you wrote them, are stored on our servers and anyone can read them. Only members of the hall and its elders can write there. When you start a topic or reply, your phone follows it so you hear about new replies; you can turn this off for each topic. Which topics you follow stays on your phone.
- Halls are public too. A hall is one page for a community: its channels, a notice board and invitations to its groups. A hall you make, and which halls you join, are stored on our servers with your Sika key. Only the number of members is shown, never who they are. The groups on a hall stay private and end to end encrypted: the page holds only an invitation, and an admin lets each person in.
- If you choose Sika cloud for a backup, the backup file goes to our storage. It is locked on your phone with your backup code before it leaves, and we never receive the code, so we cannot open it. We keep your Sika key, the size and fingerprint of the file, when it was stored, and a scrambled form of a value your phone works out from the code, which lets a new phone find the file with the code alone. Each cloud backup replaces your last one; you can delete it in the app, deleting your account deletes it, and one not renewed for 400 days is deleted. If you switch on automatic daily backup, your phone replaces the cloud backup once a day while Sika is open, without files; the backup code is kept only in your phone's secure storage and is never sent to us.
- If you send a GIF, your phone asks our server, which asks our GIF partner Giphy. The partner sees our server's address and the words searched, never your phone, your Sika key or the chat. The GIF you pick is fetched through our server and then sent in the chat as an ordinary encrypted file. We do not keep searches or GIFs; our server holds a short-lived record of requests only to limit abuse.
- A video status is too big to send to each contact, so your phone locks it first and puts the locked file in our storage for a day. Only the people you share it with get the key to open it. We cannot watch it. With Premium a video status can be three minutes long: your phone shows our storage your signed Premium copy when it asks for room, and the storage checks it and keeps nothing of it.
- A bigger file you send in a chat (over 256 KB, up to 100 MB, such as a video) is locked the same way and its locked copy is kept in our storage for up to fifteen days, so it reaches the other person even while your phone is off. Only the people in that chat get the key. We cannot open it.
- Sika Business is free with a verified phone number or email. Your business name, area and opening hours go to your contacts inside your profile, end to end, with a copy of your plan signed by us so their phones can check the business mark. Greeting and away messages and quick replies stay on your phone and are sent as ordinary encrypted messages. A paid plan is only a note of which plan you have; it never gives us access to anything you say.
- Sika Premium is prepaid for a week or a month and never renews by itself. You pay on our payment partner's page (Flutterwave); we keep a record of each Premium payment (a reference, your Sika key, the period, the amount and currency, and whether it was paid). If you choose, your contacts see a Supporter mark in your profile, sent end to end with a copy of your plan signed by us; you can turn it off.
- You can buy Rubies on Flutterwave's page and spend them on gifts, or on plans from Sika (Premium, Business Pro, a shop address, Chat Team, a developer plan), inside Sika. They cannot be turned back into money or moved to another person's balance. Our Ruby service keeps your Sika key, your Ruby balance and every Ruby in or out, your purchases, and for each gift who sent it to whom, which gift and when. It never sees your chats, your contacts or the note you write with a gift, which travels end to end in your chat. Gifting status: the more Rubies you have gifted, the higher your status mark, which the Ruby service signs and shows beside your name on the gifts you send; it is shown only while your gift shelf is visible. You can refuse gifts; "only from my contacts" is checked on your phone, because our service cannot see your contacts. Your gift shelf shows others how many of each gift you were given, never who gave them; you can hide the shelf or any one gift. If you report a gift, the service keeps the report (which gift, your key, the reason, when) until a reviewer closes it, and several reports can pause the sender's Rubies while we look.
- Public lives: a live video from a channel, a hall or a shop is public, like a public post, and is labelled Public. It goes through our media server, which can see it, so it is not end to end encrypted. Viewers can only watch; their comments go to our server, which checks them and passes them to the room, and are not kept after the live. We keep who went live, from which space, when, who the host blocked, and any report (live, reporter, reason, time) until a reviewer closes it. Staff can end a live. A viewer can give the host a Ruby gift during a live. The Rubies service signs a receipt, the live service checks it and shows the gift to the room, and we keep, until the live is over and for our records of Rubies, which gift, from which Sika key, to which host, and when, so the people who gave the most can be shown. If a host on a paid plan turns on Save a replay for a public live, our media server records it and we keep the recording on our storage for 30 days, where anyone who can see the live card can watch it; the host can delete it at any time, and we keep who made it, when and how long. Private lives are never recorded. Boost: a business can pay to have a channel, hall, stall or listing shown, labelled Sponsored, to people browsing a town and category. We keep who bought it, what it points to, the town and category, the time, and how many times it was shown and tapped each day. We do not keep who saw or tapped it; to stop one phone being counted twice in a day we keep a scrambled code for that day only and delete it the next day. When a business buys a Boost we ask the public spaces or market service who owns the item, to be sure it is theirs. A partner such as Kliqa can book a Boost for its own advertiser; it receives only the Boost's status and its totals of shows and taps, never anything about the people who saw it. Boost is never shown in chats, calls or Status, and nobody is paid to look at it. If you ask to be allowed to go live, we keep your Sika key, the few words you wrote about what you will broadcast, the time, and the answer, so staff can decide and you can see the result. A host can also stream from another app (such as OBS): the stream goes to our media server and shows in the live like the phone's camera would, and its stream key is deleted when the live ends. Private lives, started from a chat for the people in it, are different: the picture and sound are encrypted on the phones with a key that travels only inside the end to end chat message, so our media server forwards sealed frames and cannot see or hear them. For a private live we keep only that it happened (who started it, when, how long, viewer minutes); we do not keep its title or the chat it was shared in. Private lives have no comments, and staff can end one but cannot watch it.
- Sponsored cards: a business with Sika Business Pro can pay, in Rubies or, where Kliqa offers it, through Kliqa, to promote its own channel, hall, listing or stall in a town and topic for 1, 7 or 30 days. Our staff review each one. A promotion is labelled Sponsored and shows above the Discover lists and the market results, up to two at a time, and has a Report button. To pick them, your phone sends the town and topic you are looking at, signed with your Sika key like any request to our accounts service, and nothing else: no chats, no contacts, no location and no history, and no profile of you is built or used. We count shows and taps for each promotion by day. To stop one phone being counted twice we keep a scrambled one-day code made from your key; the key cannot be got back from it, and it is deleted within a day. If you report a Sponsored card we keep your report with your Sika key, so one person cannot report the same card twice. The business is never told who saw, tapped or reported its promotion; it sees only totals.
- If a business buys a promotion through Kliqa (kliqa.africa), Kliqa gives us only the business's Sika public key, what to promote, and the town, topic and length. We give Kliqa back only the promotion's status, its totals of shows and taps, and a statement for billing. Nothing about the people who see a promotion passes either way. What Kliqa itself does with its own customers' data is described in Kliqa's own privacy policy.
- We run no outside advertising network, we do not sell personal data, and this website sets no cookies and runs no tracking.
3. What we process, why, and for how long
| Data | Why | Lawful basis | Kept |
|---|---|---|---|
| Relay mail metadata: sender key, recipient key, size, time | To deliver sealed messages to people who are offline and to prevent abuse of the service | Contract; legitimate interests | Until delivered, and for at most 30 days if undelivered |
| Push registration: your public key and a device token from Google Firebase Cloud Messaging | To wake your phone when something is waiting | Contract | Until you turn notifications off, the token expires, or you remove the app |
| Wake-up signal: the recipient key and whether it is a message or a call | To send the wake-up. It carries no sender and no content | Contract | Not stored |
| Connection data: the network address your phone connects from, and the app version and processor type when it checks for updates | To keep the connection open, to deliver an update built for your phone, and to defend our services against abuse | Legitimate interests | Only for the life of the connection and in short-lived operational logs. We do not use it to build a profile of you |
| Call set-up messages and relayed audio | To connect calls. Audio is encrypted between the phones | Contract | Not stored by us |
| Big group calls (more than four people): a short-lived ticket naming your Sika key and the call's random room number, and, on the call server, who is in which room and when, with their network address | To forward the call's sound and pictures between the people in it. Every frame is encrypted on the phones with a key the server never has, so it cannot see or hear the call | Contract | Tickets expire after ten minutes and are not stored by us; the call server's provider keeps its connection records for a limited time under its terms |
| Group invitations and preview requests | To let an administrator confirm a group to a person who holds an invitation | Contract | Held on the administrators' phones |
| Money gifts in SikaPay: who sent it, who it is for, the amount, the short note the sender wrote, and the steps (paid, claimed, taken back or returned) | To hold the money safely between the two people, pay the receiver or return it, and limit misuse | Contract; legal obligation | As long as needed to resolve problems and meet legal duties |
| Orders in SikaPay: parties, description, the items with quantities and prices when listed, amount, steps, the shipping note a seller adds (courier, tracking number, expected day, how it was handed over, and the fingerprints of photos attached to a parcel, a delivery confirmation or a dispute, never the photos themselves, which go only to the other person in the encrypted chat), and whether the seller had Sika Business Pro when the order was made (checked from the seller's signed plan, which is not kept) | To hold a payment until delivery between two users and resolve disputes | Contract; legal obligation | As long as needed to resolve disputes and meet legal duties |
| Developer webhooks in SikaPay (only if a developer sets one): the web address and signing secret the developer chose, and a record of each message sent to it (the deal's details as the developer already has them, the time, and the answer the developer's server gave) | To tell the developer's server what happens to their deals, retry when it does not answer, and show the developer what was sent | Contract | The address and secret until the developer removes them; delivery records for 30 days |
| Complaints you make: your Sika key, the order it is about if any, what you and we write, notes staff add that only staff see, and the dates | To answer you, to show that we answer on time, and to improve. Staff see it; it is not shared outside Sika except where the law requires | Contract; legal obligation | For as long as the law requires us to keep complaint records, and then deleted |
| Community panels in SikaPay (only on a deal that names one): the panel's name and its reviewers' Sika keys (public), and in a dispute, each reviewer's vote and short note | So people a community trusts can hear a dispute first; a reviewer sees the deal's description and amount and what the two people wrote about the problem, never the chat, the photos or the people's keys. The two people see only the tally and the outcome. Either person can take the decision to Sika | Contract | With the order's record, as long as needed to resolve disputes and meet legal duties |
| Photos and short videos (up to 64 MB each) you choose to share with the Sika reviewer in a dispute: the file, locked (encrypted) on your phone, and a record of which Sika key stored it, its size, a fingerprint of the locked file and when. The order's history also keeps a reference to the locked file and the key to open it, itself locked so that only the reviewer's key opens it | So a reviewer can look at the photos and videos you chose to show when deciding a dispute. Nothing is shared unless you say yes. Our servers cannot open the file; only an approved reviewer, in the admin console, with a key that is never kept on a server in a form our servers can use (the server holds only copies locked to each admin's own phone, and the admin's public key). Every time a reviewer opens one, it is written to the audit log | Consent; contract | The locked file is deleted automatically ninety days after it was stored (the storage may take up to a further day to remove it). The record is deleted after ninety-one days. The reference in the order's history stays as long as the order does |
| Chat files over 256 KB: the locked (encrypted) file, and a record of which Sika key stored it, its size, a fingerprint of the locked file and when | So the person or group you sent it to can fetch it while your phone is off. The key to open it goes from your phone to theirs, end to end; we never have it and cannot open the file. The record lets us check a file before handing it out and keep a daily limit | Contract | The file is deleted automatically fifteen days after it was stored (the storage may take up to a further day to remove it). The record is deleted after sixteen days |
| Video statuses: the locked (encrypted) video file, and a record of which Sika key stored it, its size, a fingerprint of the locked file and when | So the people you share a video status with can fetch it. The key to open it goes from your phone to theirs, end to end; we never have it and cannot watch the video. The record lets us check a file before handing it out, keep a daily limit, and let only you delete it | Contract | The file is deleted automatically one day after it was stored (the storage may take up to a further day to remove it); you can delete it sooner by deleting the status. The record is deleted after two days |
| Cloud backup (only if you choose it): the encrypted backup file, your Sika key, its size, fingerprint and date, and a scrambled value derived from your backup code | To let you restore your account on a new phone | Consent (you choose it each time) | Until you replace or delete it, or 400 days after it was last stored |
| Daily backup of the order database, encrypted with a key held by our team and not by the hosting provider | To recover orders after a failure | Contract; legitimate interests | 30 days, then deleted |
| A seller's identity check in SikaPay (optional, to be paid more): the phone number you type is sent to AfriVerify, Sankofa's identity service, which sends you a code and takes your ID and selfie on its own page. SikaPay keeps only whether you passed, your level, the type of ID, the date and a scrambled form of your AfriVerify identity (so one person raises only one Sika key); never your name, ID number, number or photo. Or, if you choose, you send a photo of your ID and a selfie: they are locked on your phone so that only a named person at Sika can open them, kept for 14 days for this check, then deleted; we keep only whether you were approved and at what level. Or, if you choose, we ask the payment partner for the name your bank holds for your payout account and compare it with the name you type; we keep only that it matched and a scrambled form of the account, not the name | To let a seller who has proved who they are be paid more, and to meet payment and anti-fraud duties | Consent; legal obligation | As long as the seller uses SikaPay payouts, and as long as legal duties require |
| A seller's payout account in SikaPay: bank or mobile money provider, account or phone number, optional name on the account | So the payment partner can pay the seller when a buyer confirms delivery | Contract | Until the seller changes it, and as long as legal duties require for payments made to it |
| Public market listings you choose to post (and, with Business Pro, the short shop name you claim, which makes a public page of your listings at name.sikaos.app, and with the shop address add-on, the web address of your own that you point at it, such as shop.yourbrand.com, which is served through Cloudflare): the name you trade under, title, description, price, category, condition, the town or area you type (never your exact location), photos, an optional voice description, your Sika key and when you posted it | So people who are not your contacts can find what you sell. Listings are public: anyone can read them, without an account, and each has its own web page (sikaos.app/l/ and the listing's number) that you or anyone can share to other apps; the page shows what the listing already shows | Contract | Until you remove the listing. A listing you have not renewed for 30 days is no longer shown. Photos no listing uses any more are deleted after a day |
| Supermarket staff: when a Supermarket owner names a person who may help run the shop, a short note signed by the owner that holds the owner's Sika key, the staff member's Sika key, what that person may do (list items, see orders, answer buyers). A staff member allowed to see orders can read that shop's own sales (the same details the owner sees); each such read is logged on our server with both keys, and cannot change an order. When a staff member posts, changes or removes a listing, we keep a short record for the owner (the staff member's key, what they did, the listing's title and when), the newest 500 per shop and at most 90 days. If the owner lets staff answer buyers, the owner's phone passes the messages buyers send to that shop on to those staff members (still end to end encrypted), and each answer reaches the buyer under the shop's name with a line saying which staff member wrote it. A message you send to a Supermarket shop may therefore be read by its staff and until when. A listing a staff member posts also carries that note | So buyers' phones can check that the person posting for a shop was allowed to, and so the owner can take someone off at once. These notes are public, like the listings they belong to | Contract | Until the owner takes the person off or the note runs out (at most a year); the record of an owner's removal is kept as long as the shop exists. Notes kept inside a listing stay while the listing does |
| Public channels you make: the name, what it is about, the country and the town or area you type (never your exact location), topic, photo, your Sika key as owner, the Sika keys of the admins you choose, and when you saved it | So people can find and follow your channel. Channels are public: anyone can read them, without an account | Contract | Until you delete the channel. Photos nothing uses any more are deleted after a day |
| Developer tools, only if you open them in Settings: your Sika key as the developer, the names you give your API keys and bots, a scrambled fingerprint of each key (never the key itself), how many requests each key made on each day, and the Sika key of each bot, which signs the bot's public posts, and the https address (and a signing secret, kept encrypted) you give for a bot's webhooks, with the public events sent to it and whether they arrived (kept for three days) | So programs you write can post in public channels you or others run, and so limits and plans can be applied. Bot posts are public and marked Bot. Nothing here reaches a private chat, file or call | Contract | Until you revoke a key or delete a bot. Daily counts are dropped after two days. The activity log (below) is kept for 400 days |
| Sign in with Sika, only if you approve a sign-in on a website or app: your Sika key, the website or app you approved and what it asked for, the name you chose to share with it (if any), when you approved and when it last used the sign-in, and short-lived codes and tokens (kept only as scrambled fingerprints). The website or app sees a different identifier for you than every other one, never your Sika key unless you allow that in red, and never your messages, contacts, files or money. If you approve an AI assistant to read your orders, it can ask for the status of one of your own orders (paid, shipped, delivered), and the order service answers only that, with no names, addresses, messages or payout details; the question is logged with the assistant's name and the time, not what was asked or answered. If you approve an assistant to ask you to make payment links, each waiting request (the item, the amount, which assistant asked and what you answered) is kept by the sign-in service for about a month; nothing is made unless you approve it on your own phone, and then your phone makes the link with your own key. A record of each approval and sign-in, with that scrambled identifier and no content | To let you sign in to other websites and apps without a password, show you which ones you connected, and let you remove one at any time | Contract | The connection until you remove it (it stops working at once), refresh tokens for at most 30 days unused and 6 months in all, codes for one minute, access tokens for ten minutes, and the record for 400 days |
| Business notices, only if you agreed to them through Sign in with Sika: the business, the kinds of notice you agreed to (order updates, login codes, offers), a private identifier for you at that business, the text of each notice sent to you with its time, and whether it was delivered, read, answered or stopped. A notice is not a private chat: the service that sends it can read it so it can check it against approved wording and count it | To let a business tell you about your own orders, deliveries and sign-ins, and to let you stop any business or kind of notice at any time | Consent | Until you stop the business (sending stops at once); notice text for 90 days; login codes only for as long as they are valid; counts without text for 400 days |
| Developer activity log, and Enterprise organisations: for every change made with your keys or from your app (a key made, changed, rotated or revoked, a webhook set, a seat added or removed), who did it (the key, you, or a named seat), what, to what, when and whether it worked; no address, no request content and no secret. For an Enterprise organisation also the Sika keys of the people you add as seats and their role (developer, finance or auditor), and the agreement staff recorded (the invoice reference, who granted it, the agreed limits and its end date), and, if staff checked the company register, the organisation's registered name, registration number and country and who checked it (only the registered name and the country are shown to other people, as a verified mark on its bots and shop, and only while the Enterprise plan runs) | So an organisation can see and prove what happened on its account, and so people can act for it with only the access their role gives | Contract | The log for 400 days. Seats and the agreement until you remove them or the agreement is ended (seats then stay on record but do nothing until it is granted again, unless you remove them) |
| Verified organisation mark: when a post is on your screen, the app asks our developer service whether the post's author (a public Sika key, or a bot's key) belongs to an organisation staff have verified. The question carries that public key and, as with any request, your network address; the answer is no, or the organisation's registered name and country. The service does not keep a record of who asked or what they were shown, only a short in-memory counter by address to stop floods | To show the verified mark, so you can tell a registered company from a copycat. Answers are remembered on your phone for ten minutes | ||
| Views of Sika's own notices: when the Sika Official chat shows a notice, and only if your read receipts switch is on, your phone sends the notice's number to our public service, signed with your Sika key. We count one view for each phone, notice and day. To count once, the service keeps for that day only a scrambled code made from your key, the notice's number and a random value of that day; the random value and the codes are deleted when the day ends, so afterwards nobody, including us, can tell whether your key was counted. What remains is a total of views for each notice and day, which only Sika's own account can read. Your phone remembers for two days which notices it already reported | So Sika can see whether an important notice, such as a safety warning, reached people, without knowing who read it. Turn read receipts off in Settings, Privacy, and nothing is sent | ||
| Channel posts and podcast episodes: the text, photos and recording you post (an episode can be up to 30 minutes), your Sika key and when you posted it | To show the post to everyone who opens the channel, and to tell its followers. Posts are public | Contract | Until you, the owner or an admin deletes the post, or the channel is deleted |
| Comments on channel posts: the words you write, your Sika key, which post and comment (if any) you answer, and when | To show your comment to everyone who opens the post. Comments are public like the post, and are not end to end encrypted | Contract | Until you or the channel's owner or admins remove it, or the post is removed. A comment hidden by reports stays on record for the reviewers until they decide |
| Edits of your own public post, comment, topic or reply: the new words, your Sika key, which item, and when | To show the corrected words beside the original, with an "edited" mark. Edits are public like the item, are possible for 48 hours after posting, and are not end to end encrypted | Contract | Until you or someone allowed to remove the item removes it; the edit goes with the item |
| Website chat box, for businesses that switch it on: the business's Sika key, the name, welcome line and colour it chooses, the relay address its phone uses, its public key, and the websites it allows | To show the chat box on those websites and let visitors send sealed messages to the business. This is public information the business chooses to publish. Messages themselves are sealed to the business's key: our servers and the relay carry ciphertext and cannot read them | Contract | Until the business turns the chat box off |
| Visitors to a website with a Sika chat box: nothing is stored by us about the visit. The visitor's browser keeps a key it made, and the conversation, on that device only. The relay briefly holds sealed messages for the business and sees the visitor's public key, the time and the size | So the visitor can chat without an account, and so messages wait for the business if its phone is offline. A visitor can clear this by clearing the site data of sikaos.app in the browser | Contract | Sealed messages wait on the relay for a few days at most; the rest stays in the visitor's browser |
| Your vote in a poll on a channel post: your Sika key, which post, which choice, and when | To count one vote each and show totals. Only totals are shown to others; the choice you made is not shown to anyone, but our servers can see it. Not end to end encrypted | Contract | Until the post is removed |
| Follows: which channels your Sika key follows, and when you started | To show you the channels you follow and to count followers. Only the number of followers is shown, never who they are. The app follows the Official Sika Account (the news and safety notices at the top of your chat list) for you once, the same way, so its notices reach your phone; you can mute it. Every phone also listens on one shared topic for the rare urgent notice that must reach everyone even if the account is muted, the same way it listens for new app versions | Contract | Until you stop following, or the channel is deleted |
| Halls you make: the name, what it is about, the country and the town or area you type, topic, photo, your Sika key as owner, the Sika keys of the elders you choose, the channels it shows, and the names and invitation links of the groups you add | So people can find your community's channels and ask to join its groups. Halls are public: anyone can read them, without an account. An invitation lets nobody into a group by itself; an admin says yes to each person | Contract | Until you delete the hall |
| Forum topics and replies: the title and text you write, up to four pictures on a topic, a voice recording if you add one, whether it is a question, which reply it answers, your Sika key and when you wrote it; and the hall's choices of pinned, locked and accepted answer | To show the forum to everyone who opens the hall. Forums are public | Contract | Until you or the hall's elders delete it, or the hall is deleted |
| Hall members: which halls your Sika key joined, and when | To show you the halls you joined and to count members. Only the number is shown, never who they are | Contract | Until you leave, or the hall is deleted |
| Near me: the country and the town or area you type, sent when your phone asks for posts from channels in that area. Sika does not use your location | To show posts from channels that chose your area | Contract | Not stored. The place you typed is kept on your phone only |
| Browser notifications for the staff inbox, only if you turn them on: your inbox browser's device key and the address your browser's push service (Google, Mozilla, Apple or Microsoft) gave it | To show "you have a new message" when the inbox tab is closed. The nudge is empty: it names no sender, no text and not even that it is a message, and the browser's push service learns only that something was sent to that browser | Consent (you turn it on in the inbox) | Until you turn notifications off or unlink the browser, the browser drops the subscription, or the push service reports it gone |
| Sika on the web (the Sika app in your browser, for example on an iPhone): your keys, contacts and messages stay in your browser, locked with a passphrase only you know; our servers hold none of them. Browser notifications, only if you turn them on: your Sika key and the address your browser's push service (Apple, Google or Mozilla) gave it | To show "you have a new message" while the app is closed. The nudge is empty: it names no sender, no text and not even that it is a message, and the push service learns only that something was sent to that browser | Consent (you turn it on in Settings) | Until you turn notifications off or delete everything in Settings, the browser drops the subscription, or the push service reports it gone |
| Sika on the web, only if you turn on "Show who wrote and what": a copy of your keys kept on your own phone, sealed under a key your browser makes and does not give out, and messages that arrived while the app was closed, sealed the same way until you open the app. Nothing of this reaches our servers | To show the sender and the words in a notice while the app is closed. The copy of your keys lets Sika open your mail without your passphrase, so anyone who can use your unlocked phone can read new messages in notices | Consent (you turn it on in Settings) | Until you turn it off (the copy and anything waiting are deleted) or delete everything in Settings |
| Sika on the web, if you link it to your phone: a certificate for this browser on your signed list of devices (a name and a public key, the same as for any linked device), and a lookup of a contact's signed device list when you write to them | To let your phone and this browser both send and receive as you, and to send a message to each of a contact's devices. The lookup tells our accounts service which person's list was asked for, from this browser's network address, and nothing about messages | Consent (you scan the code on your phone) | Until your phone removes the browser from Linked devices, or you delete everything in Settings |
| AI help in the staff inbox, only on Chat Team accounts and only if a staff member turns it on in the inbox: the last messages of the chat they have open (at most twelve), the business's saved quick replies, and the device key and account key of the browser asking | To write a suggested reply that a person reads, edits and sends. Our accounts service passes these messages to an AI model provider (Anthropic) for that one answer. This is the one case where text from a private conversation leaves the device, and it happens only when staff press Suggest a reply. Customers cannot use it. Nothing is sent to the customer unless a person presses Send | Consent (staff turn it on in the inbox and confirm a warning) | Not stored by us. We keep a short count of requests per account for a day to limit use. The provider handles the text under its own terms |
| Pay links for buyers who do not have Sika: the order (what it is for, the amount and fee, its status and dates) and a random buyer code that belongs to no one. We do not ask the buyer for a name, phone number or email | So a seller can get paid through Sika's protected payment by someone without the app. The buyer opens the link, pays on our payment partner's page and later confirms the order arrived or reports a problem. The link's secret part sits after the # sign, so it is not sent to any server when the page opens. The payment partner collects the buyer's payment details itself | Contract | As long as the order, the same as other orders |
| New post alerts: the channel, its name and the first words of the post, sent to Google Firebase Cloud Messaging for the phones that follow it | So followers hear about a new post while the app is closed. Your phone joins a topic for each channel you follow, so Google learns which channel topics your phone listens to; our push service keeps no list of followers. Forum replies work the same way: the topic's title, the first words of the reply and the replier's Sika key go to the phones that follow the topic | Contract | Not stored by us. Your phone leaves the topic when you stop following |
| Verified check for channels: the channels service asks our accounts service whether a Sika key has a verified phone number and whether it has a verified email, and gets only yes or no for each | To require a verified account before someone makes a channel or posts, which limits spam and abuse | Legitimate interests | A yes is remembered for ten minutes; nothing else is kept |
| Reports about a channel, post, hall, forum topic or reply: who reported it, the reason and an optional note | To hide and review channels, posts and halls that break the rules | Legitimate interests; legal obligation | Until the report is reviewed, and as long as legal duties require for content taken down |
| Seller ratings: the stars and optional words a buyer leaves after a completed protected order, and how many protected orders a seller completed | So buyers can trust sellers with a record that only real deals can make | Contract; legitimate interests | As long as the seller's account exists. The stars, words and day are public on the seller's shop; the buyer's name and key are never shown |
| Reports about a listing: who reported it, the reason and an optional note | To hide and review listings that break the rules | Legitimate interests; legal obligation | Until the report is reviewed, and as long as legal duties require for listings taken down |
| Verification: the phone number or email you add, the one-time code, and the Sika key that asked for it | To send you a code and confirm the number or email is yours | Consent; contract | The number or email is held only while the code is valid (10 minutes), then kept only as a scrambled one-way form. The code is deleted when used or expired |
| Reactions on public posts: when you react to a channel post, a forum topic or a forum reply, the Sika key you reacted with, the emoji you chose and which item it was | To show how many people reacted with what, and which one is yours, and to keep to one reaction per person | Contract; legitimate interests | Until you take your reaction back, or the post is removed. Only counts by emoji are shown to other people. Reactions in private chats are end to end encrypted and never reach our servers |
| Linked devices: if you link a second phone or a computer, the list of your devices (each device's name, its public key and the date it was linked), signed by your main phone. A contact's phone can fetch it to know which devices are yours | So your messages reach each of your devices, and your contacts' phones can tell your devices from a stranger's | Contract | Until you remove a device (the list is replaced) or delete your account. It shows how many devices you have and what they are called, never a message, a contact or a private key |
| Account: a scrambled one-way form of your verified phone number or email, the Sika key it belongs to, your optional username, and whether people may find you | So friends can find you and so you can move to a new phone | Consent; contract | Until you remove it or delete your account. We cannot turn the scrambled form back into your number |
| Two-step verification, if you turn it on: a salted one-way form of your six-digit PIN, and a count of wrong tries | So your phone number cannot move to another phone (for example after a SIM swap) without your PIN | Consent; contract | Until you turn it off or delete your account. We cannot turn the stored form back into your PIN |
| Plans and Sika Business: which plan your Sika key has (for example free Sika Business), until when, and how it was given | So the app, and your contacts' phones, can check a plan or the business mark without asking us each time. Free Sika Business needs a verified phone number or email | Contract | Until the plan ends or you turn it off. The signed copy your phone keeps lasts 30 days at most |
| Public lives: your Sika key as host, the space, the title, start and end times, viewers the host blocked, reports (live, reporter, reason, time), and each month's viewer minutes against your live plan; comments pass through and are not kept | To run lives, let hosts moderate, handle reports and stop abuse | Contract; legitimate interest (safety) | Live records 12 months; reports until closed |
| Sponsored cards (Sika Boost). For a business that buys one: its Sika key, what it promotes, the label, town, topic and length, and the totals of shows and taps by day. For people who look: only a scrambled one-day code made from your key, and, if you report a card, your Sika key, which card, the reason and when | To show labelled promotions for a town and topic, to count shows and taps once per phone per day, to bill the business, and to review reports of misleading or unsafe promotions | Contract; legitimate interests (counting once, preventing abuse) | The one-day code: deleted within a day. Totals and the promotion's record: with the business's account and billing records. A report: with the promotion's record |
| Rubies: your Sika key, your balance and each Ruby in or out (a chained record), purchases (a reference, the pack, the amount and currency, when), each plan you paid for in Rubies (which plan, for how many days, the Rubies, when), and for each gift the sender, the recipient, the gift and the time; whether you show your gift shelf and which gifts you hid; gift reports (gift, reporter, reason, time) and any pause on an account | To keep your balance right, count each payment once, give each gift a receipt that cannot be faked, handle refunds, and stop gift abuse | Contract; legal obligation (accounting records) | The balance record as long as accounting law requires; gift records 24 months |
| Premium, Sika Business Pro, Supermarket and developer plan (Builder, Business) payments: a reference, your Sika key, which plan, a week or a month, the amount and currency, when you started paying and which payment partner took it and whether that partner confirmed it | To turn Premium on only for a confirmed payment, to count each payment once, and to handle refunds | Contract; legal obligation (accounting records) | As long as accounting law requires |
| Friend lookups: scrambled forms of the numbers and emails a phone asks about, from its contact list or typed in | To tell you which of them are on Sika | Consent | Not stored. Daily limits apply. A scrambled phone number can still be guessed by someone who tries every number, so we limit lookups, and you can switch off being found in Settings, Account |
| Feedback: message, topic, optional rating and contact, and from the app the app version, phone model and language | To improve Sika and reply when you ask us to | Consent; legitimate interests | Up to 24 months |
| Spam protection: a daily-rotating, one-way hash of your network address | To limit abuse of the feedback form | Legitimate interests | Up to 24 hours |
| Download counts by day, file and build | To understand adoption. Not linked to you | Legitimate interests | Aggregated, no personal data |
| Contact links opened in a browser: the link itself, which holds the public Sika key and the name its owner chose to share | To show the page and open the app | Legitimate interests | Only in the server logs below. The page stores nothing |
| Server logs at our hosting provider | Security and reliability of the website | Legitimate interests | Short-lived, as set by the provider |
Your profile picture and About line are sent only to your contacts, as end-to-end encrypted messages. We do not receive them. Messages you send to our support address pass through our email routing provider to our mailbox, and we keep them as long as needed to answer you.
Your account keys, chats, contacts, files and settings are stored on your phone. We do not receive them. If you create a backup, it is a file that only you can open with the code you set, whether you keep it yourself or in Sika cloud.
4. What we never process, and what the app asks your phone for
We never process the content of your messages, photos, files or call audio, and we never hold your private keys.
Nearby (Android, early version) uses the phone's Bluetooth, with no server of ours involved. In a Nearby room, anyone near you can read what you post and see your Sika key, and your phone also passes on other people's room posts and sealed packets. When Bluetooth backup is on and a private message cannot be sent for lack of network, the message can travel to your contact through the phones near you, sealed so that only your contact can open it. With the backup on, your phone also sends your contacts a signed list of one-time public keys, in an ordinary sealed message through the relay (we cannot read it); a contact uses one key for one Bluetooth message to you, and your phone deletes that key's private half the moment it opens the message, so a copy of your phone taken later cannot open a Bluetooth message you already read. The phones that carry it can see that a sealed packet passed, never who it is for or what it says, and keep it for at most a day. You can turn Nearby and the backup off at any time in Settings.
The app asks your phone for permissions only for the feature that needs them: notifications and full-screen alerts, to tell you about messages and incoming calls; the microphone, for calls and voice notes; the camera, to take photos and videos in Sika's own camera, to scan codes and for video calls (a photo or video stays on your phone until you send it, and a photo is sent without its location or other hidden details); your contacts, only when you tap Find friends, and only to compare scrambled phone numbers with the people who allow being found (the list itself never leaves your phone); and the photos, videos and files you choose to send. Translate on a message runs on your phone: the first time, with your say-so, the phone downloads the two language packs from Google, which learns only that a pack was fetched; the message text is never sent anywhere. For 19 African languages there is an optional African languages pack: with your say-so the phone downloads one language model file (about 670 MB) from Sika's own download server, which sees your address as for any download but never the text you translate, because that runs on the phone alone. The pack is the open TranslatePsy-AfriSLM model by Tether Data (Apache 2.0), built on Qwen3.5 by Alibaba Cloud (Apache 2.0), run with llama.cpp (MIT). It is machine translation and can be wrong. Share screen in a call sends a picture of your screen, only when you tap it and Android agrees, inside the call, end-to-end encrypted like the rest of the call; Android shows a notice for as long as it lasts. A call link holds a random room name and a key after the # sign, which a browser never sends to a website; the call goes through a media server that forwards frames already encrypted on the phones, so it cannot see or hear anything. Anything you send travels as end-to-end encrypted messages. The app reads your location only when you tap Share location in a chat and pick exact or around here; it goes only into that chat, end-to-end encrypted, and is never sent to our servers or kept. The app does not read your call history. You can withdraw any permission in your phone's settings; the matching feature then stops working.
5. Who receives data
We use infrastructure providers as processors under written terms, for example Vercel (website hosting), Neon (the website's database), Cloudflare (domain name, email routing for our support addresses, and file storage for app downloads), GitHub (software releases), Giphy (GIF search, reached only through our server as described above), Google Firebase Cloud Messaging (push wake-ups, one alert sent to every phone at once when a new version is out, which names no one, and alerts for new posts in public channels, sent to the phones that follow the channel), Africa's Talking (text messages with sign-in codes), LiveKit (the server that forwards big group calls; it receives only encrypted frames, your Sika key and the room number), Resend (emails with sign-in codes), Flutterwave (the payment partner for SikaPay orders: buyers' money is held in our Flutterwave account until the order finishes; it receives the amount, the order description and reference, an address of ours made from part of the buyer's Sika key in place of the buyer's email, and, for a payout, the seller's account; for Sika Premium and Sika Business Pro it receives the amount and the payment reference, and either an address of ours made from part of your Sika key or, if you have verified an email on Sika, that email, so Flutterwave can send you its receipt (we pass it on when you pay and do not store it with the payment); it does not receive messages or contacts; card, bank and mobile money details you type on its payment page go to Flutterwave, not to us), and managed database and hosting providers for the relay and order services, with daily encrypted order backups kept at GitHub. The current list, with what each one does and receives, is at sikaos.app/subprocessors. They process data only on our instructions. We disclose data to authorities only where the law requires and only what the law requires. Because content is end-to-end encrypted, we cannot disclose it.
6. International transfers
Our providers may process data in countries other than your own. Where required, we rely on recognised safeguards such as standard contractual clauses.
7. Your rights
Depending on where you live, including under the GDPR, the UK GDPR, the Ghana Data Protection Act, the Nigeria Data Protection Act, the Kenya Data Protection Act and the South African POPIA, you may have the right to access, correct, delete, restrict or object to our processing of your personal data, to receive it in a portable form, and to withdraw consent at any time. To exercise a right, email privacy@sikaos.app. We respond within 30 days. You may also complain to your data protection authority.
Most data about you lives on your phone, where you control it. You can delete it at any time from Settings or by removing the app.
Two rights work straight from the app, under Settings, Account. Request my account info shows everything our accounts service holds about your Sika key (the scrambled form of your verified number or email, your username, whether people may find you, your plans and your payment records) and lets you save or share it. Delete my account removes your verified number and email, your username and your plans from our servers at once, then erases Sika from your phone. Payment records stay for as long as accounting law requires, as the table above says. Public posts, channels, halls and listings are deleted from where you made them; Rubies and SikaPay orders are covered by email to us.
8. Security
We protect data with end-to-end encryption, encrypted storage on your phone, minimal retention, access controls and signed releases. See our security overview. No system is perfectly secure, and we will notify you and the relevant authority of a breach where the law requires.
9. Children
Sika is not directed to children under 16, and we do not knowingly collect their personal data. If you believe a child has used Sika, contact us and we will act promptly.
10. Cookies
This website sets no cookies and uses no analytics or advertising trackers.
11. Changes
If we change this policy in a way that matters, we will update the effective date above and tell you in the app before the change takes effect. In particular, before we start to process anything not listed in section 3, such as phone numbers or email addresses for sign-up, a contact list for finding friends, or public posts, we will add it here, explain why and for how long, and ask for your consent where the law requires it.
12. Contact
Sankofa Network, Akwa Ibom State, Nigeria. privacy@sikaos.app.