tribes for Android · Effective October 13, 2026 · Referral disclosure added October 18, 2026, amended October 18, 2026 · Operator: App Development For You LLC ("we")
In short: tribes has no accounts, and no server that stores posts. We, the developer, do not receive or sell your posts, photos, videos, or names. Those stay on the phones you link, and a shared post travels only between those phones, end-to-end encrypted over Tor. A private diary never leaves the phone that wrote it. If a parent on the Google Play version accepts a referral code and then buys, that phone sends us the code and Google's order number, and nothing else. The referral code a parent enters is stored on that parent's phone and shared encrypted with the other parent's phone in the same family, never with child phones; it and Google's order number go to our server only when a parent buys with a code. On iPhone, the referral code a parent enters is stored on that parent's phone and shared encrypted with the other parent's phone in the same family, never with child phones; it and Apple's transaction number go to our server only when a parent buys with a code.
What tribes is
tribes is a private Circle Chat for a small group ("tribe") of families who know each other. Each family has an Adult phone run by a parent or guardian, and children use Child phones that are linked to their parent's Adult phone. Phones talk directly to each other over the Tor network. There is no central server for posts, photos, or names. The only extra call, described below, is a referral code and an order number after a parent accepts a code and buys.
Information on your phone
tribes handles more than a name. All of the following is stored on the phone, encrypted with a key held by Android's keystore. Android cloud backup and device-to-device transfer are turned off. Screenshots and screen recording are blocked inside the app.
Names you type: your display name, your family name, a child's first name, a tribe name, and an organization name.
Posts, comments, and reactions (Like, Love, Care, Haha, Wow, Sad, Angry), and the same things shared with you.
Photos on posts, and an optional profile picture. A tribe can have a picture. A photo is re-encoded on the phone before it is kept or shared, which removes location (GPS), camera model, and the time it was taken.
Videos up to 20 seconds. "Record a video" opens your camera app, which records the sound. tribes does not ask for the microphone. The video file can include that sound. It is converted on the phone to a small MP4 written without location, dates, or camera model.
A private diary. Every post is saved there. A Private entry never leaves the phone. A parent cannot read a child's diary, and there is no setting to turn the diary off. Share with my circle saves the same diary entry and also sends it in Circle Chat; see below.
A key and an onion address created on the phone. They identify the phone to the phones you link with. They are not an advertising ID, and the app does not read the Android advertising ID.
A parent PIN on an Adult phone, stored only as a salted hash (PBKDF2). The PIN digits are not sent. When the PIN is created, that phone shows a recovery code once and asks the parent to write it on paper and keep it where children cannot reach it. The phone stores only a slower salted hash of that code. The code itself is not stored and is not sent. Entering it sets a new PIN on that phone and does not erase the phone. Wrong tries wait longer each time, and after about 10 the phone locks for a long time. A parent who still knows the PIN can create or replace the code, and the old code stops working. Your date of birth is not stored. The app remembers only that an Adult phone was confirmed as an adult. If the age check says the person is under 18, the phone remembers that fact for 24 hours (a timestamp, not the date), so the age screen is not simply retried. That memory stays through Erase and is deleted when the app is uninstalled.
An optional note a parent may type when approving a child's request to connect (for example the parent's name and a phone number). It is not required.
Reports, hide lists, and block lists.
On the Google Play version only: the parent phone that buys keeps Google Play's purchase token and order id on that phone.
On the Google Play version only, an age-range signal read from the Play Store app on that phone when an Adult phone or organization is set up, when a parent phone links with a child, and about once a day after that. The phone keeps a coarse result: verified (Play reported an ID-checked 18 or over), not verified (Play did not share a result, so the date-of-birth screen was used), blocked (supervised or under 18), or still needs a Play age check. The date of birth, the age numbers, and Play's install id are not stored. The result stays on that phone. It is not sent to us, to the other parent, or to a child phone. A copy installed from our website does not ask Play. If a parent phone later gets a supervised or under-18 result, parent actions on that phone lock. The iPhone app does not ask Apple for an age range. The adult check on iPhone is a date of birth the person types, plus a parent PIN. That date is not stored.
On a Google Play parent phone only, a referral code the parent chose to keep (for example JANE-7K4Q9M). It can come from a link, from the Play install referrer, or be entered at setup or in Settings. A parent can also enter it on the screen where they buy (an optional row, “Have a referral code?”). It is stored only after the parent taps Use code. The referral code a parent enters is stored on that parent's phone and shared encrypted with the other parent's phone in the same family, never with child phones; it and Google's order number go to our server only when a parent buys with a code. It is also encrypted with the rest of the data on each parent phone. The family keeps one code, the first one entered; if both parents enter one, the earlier one is kept on both phones. Remove or Change in Settings asks for the parent PIN and applies to both parent phones. An organization phone and a copy from our website do not store it.
A short debug log in memory for this run (up to 600 lines): times, display names, tribe and family names, short onion addresses, counts, and errors. It does not contain post text, photos, or keys. It is not sent unless you copy it and choose to send it.
What is shared, and with whom
Sharing below means phone to phone, inside tribes. It is not sent to us. A child's phone talks only to its family's parent phones (one parent, or both). It does not open a connection to another child's phone. The parent phone passes approved Share with my circle messages along.
Share with my circle messages (text, photos, videos, the author's name, and the family name), comments, reactions, and profile pictures go only to people that person is already connected with, in one Circle Chat: the families in their tribes, and a person they have a direct friend link with. A friend link is between two people. It does not copy one tribe into another tribe. Each channel has its own key. A shared post stays on the phones that received it until the person who posted it deletes it. The 7-day limit applies only to the sealed copies waiting in the mailbox or on a friend relay, not to posts already delivered. The sender's phone keeps its own copy, including the diary entry.
A Private diary entry stays on the phone that wrote it and is never sent, including to a parent. There is no setting to turn Private off. Parents see a child's Share with my circle messages and connections. They do not see the diary.
A child's Share with my circle message goes through the child's parent phone. By default ("Authorize posts") the parent approves each Share with my circle message or comment before it leaves. A link is one direction at a time. By default the friend's family approves that direction; the child's own parent is asked only if they turned on Adult consent. On a direct request the other child is not asked. Turning a direction back on needs a new request. Two parents stay mutual, and a parent companion stays mutual. A tribe Head is not asked to approve a friend.
The optional parent note (name, phone number, or whatever the parent types) is sent only to the other child's parent, before that parent approves. It is not a Circle Chat message.
The parent PIN hash is shared inside the family, so a child's phone can check either parent's PIN. The PIN digits are not sent. The recovery-code hash stays on the phone that made it. It is not sent to the other parent or to a child's phone.
A parent who forgot the PIN can ask the other parent phone to allow a reset. That request stays between the two parent phones. The other parent approves with their own PIN. Both phones then wait 24 hours, and either parent can cancel. The new PIN is chosen on the phone that asked, after the wait. A child's phone cannot start or finish a reset. Nothing about the code or the request is sent to us. There is no server, no email, and no account for this. After the PIN changes, the new PIN hash still syncs to the children's phones the same way as before.
A child's phone can be shown the names of people in the family's tribes, and of brothers and sisters, so the child can ask to connect. Those people's posts are not shown until the connection is approved. A family that is still "Head only" in a tribe is not listed for this until the Head opens it.
Photos and videos are re-encoded on the phone before they are stored or shared, which removes location and camera details. A Private photo or video never leaves the phone.
Nothing is public or searchable. There is no directory of users that we operate.
Organizations. A parent can run a one-way organization page (for example a school class) from their Adult phone. It has its own address and key. Families ask to follow it, and the organization approves. The organization receives the family name that asked, reports about its posts and, only if it turns comments on, comments sent to it. It never receives a family's Circle Chat. On an organization's post, viewers see only the word Reacted. No counts are shown, and no names. A comment on an organization's post is seen only by the organization and the commenter's own family. A family can show an organization's card (name, picture, follow code, never its posts) to the parents in its tribes.
Offline delivery (encrypted mailbox)
When someone you are sending to is offline, tribes can leave the message in a mailbox on our server so it arrives later without both phones being online at the same time.
The message is end-to-end encrypted on your phone before it is sent. Only the phones it is meant for have the key. We cannot read it, and that includes photos, videos, names and comments inside it.
Phones reach the mailbox only over Tor, using random mailbox numbers made on the phones. We do not get your IP address, account, phone number or name, so we don't know who sent a message or who it is for.
The server keeps only the locked message, its size and the time it arrived. It keeps no access logs and no IP addresses.
A copy is deleted as soon as the recipient's phone picks it up. If it is not picked up, it is deleted after 7 days.
Messages not picked up within 7 days are lost. A phone that stays offline longer than that will not receive them from the mailbox.
Each mailbox has size limits (videos are up to 20 seconds). A Private diary entry is never sent to the mailbox.
What we receive
We do not operate a server that stores tribes content, and the app does not send us posts, photos, videos, or names. There are no analytics, advertising, tracking, or crash-reporting tools in the app, and the advertising-ID permission is removed. We do not sell data. We cannot see or recover your content from our side.
Google Play version. Updates come from Google Play. The app's own network traffic is Tor, phone to phone, except the referral POST in the next item. Purchases go through the Google Play Store app on the phone (Play Billing Library).
TRIBES code (0.32.0). One purchase works on up to 5 phones in your family. When a phone buys, restores, or uses a family TRIBES code, it sends one HTTPS request (not Tor) to https://appdevelopmentforyou.com/tribes/api/license/v1/ with the store's receipt or the TRIBES code, a random id the app made (not your phone number), the platform, and a phone name for the My phones list, which you can change. No names of people, no posts, no photos. Our server keeps that phones list (a hash of the random id, the phone name, platform, and when it was last seen) and does not keep IP addresses. A phone not used for 90 days is removed from the list. The phone checks in about once a week. The code reaches your child and co-parent phones inside the encrypted family sync. A copy from our website never sends this.
10 Day evaluation period (0.32.25). After setup, the Google Play and App Store versions send an HTTPS request (not Tor) to https://appdevelopmentforyou.com/tribes/api/license/v1/eval when the app starts and at most every 6 hours. It contains a device id (on Android a one-way hash of the Android ID; on iPhone a random id kept in the Keychain), the platform, the phone's public key, the random id the app made for the TRIBES code, the TRIBES code if the phone has one, and the sticker number or referral code you arrived with, if any. No names, posts, photos or contacts are sent. Our server keeps hashes of these ids, the start and end of the 10 days, and when the phone was last seen, so a reinstall does not start a new period, and it keeps the sticker number or referral code. It does not keep IP addresses. Organization phones never send this.
Referral code and order number (0.25.0). Only if a parent on the Google Play version has a referral code for the family (entered on that phone, or on the other parent's phone, which shares it), and then buys TRIBES on that phone, the app sends one HTTPS request to https://appdevelopmentforyou.com/tribes/api/referral. The request contains the code, the word android, Google's order number, the product id (tribes_unlock, or legacy tribes_family / tribes_kid_seat), the purchase time, and the app version. Nothing else is sent. No names, no family, no posts, no photos, no device id, no account id, and not the purchase token. There are no cookies and no account header. This request is ordinary HTTPS, not Tor. Restoring purchases does not send an old order. Each order is sent once, even if both parents have the code. If the network fails, the phone tries again later, at most once an hour, and stops after 30 days. No thanks, or Remove in Settings, means nothing is sent. A child phone, an organization phone, and a copy from our website never send this.
Tor. Relays can see that a phone uses Tor. They cannot read tribes messages. If a network blocks that connection, the phone tries other ways on its own (Snowflake, obfs4 bridges, or meek through a CDN). A parent can also paste bridge lines. Those lines stay on the phone. This traffic is still the connection to Tor. We do not receive it.
Legal pages. Privacy, Terms, and Child safety open in your browser at https://appdevelopmentforyou.com/tribes/. That is a normal page request. The site can see the IP address of the request. The app does not attach posts, names, or photos.
Codes you share (personal code, organization code, tribe invite). These travel from one phone to another, by in-app QR, by text message, or by a link. We do not receive them and no tribes server handles them. A personal code contains the person's public key, display name (up to 40 characters), family name (up to 60), the family Adult phone's Tor address and public key, a parent or child flag, and a signature. It has no photo, phone number, email, location, or date. A child's code has the child's name and key plus the parent Adult phone's address and keys, so anyone who sees it learns the child's name, family name, and those addresses. Personal and organization codes do not expire and cannot be revoked; a tribe invite is single-use and expires after 3 days. A code alone cannot read anyone's posts: posts are encrypted with keys that exist only after the connection is approved. By default the friend's family approves a child's connection; the child's own parent PIN is required only if that parent turned on Adult consent. A person who has only a copied code can only put a request in a parent's pending list. An organization code contains the organization's name, short description, Tor address and public key. If a code is shared as a link (.../tribes/join?p=... or ?c=...), the code is in the link's address. If the app is installed and the link opens in the app, our website is not contacted; otherwise the page loads, and our web server does not log the code (see the next item). When tribes is installed from Google Play after opening such a link, Google Play passes the code to the app as an install referrer; the app reads it once, keeps it only in memory, and sends nothing automatically.
Join links and QR stickers. Some stickers, signs and flyers carry a QR code that opens https://appdevelopmentforyou.com/tribes/join, sometimes with a number such as ?s=17 that says which sticker or sign it was. Opening it is a normal page request. The web server's log keeps only the time, the page, the browser type, and the sticker number. It does not keep IP addresses, and it does not keep any other part of the link, such as a personal or organization code. We use it only to count how many times each sticker or sign was scanned, keep the daily totals, and delete the raw logs after about 14 days. We do not link a scan to a person, a phone, or anything inside the app. The join page is static. The app ignores ?s= and sends nothing.
Referral code, iPhone parent phones only. If a parent accepts a code and then buys tribes on that iPhone, the App Store build sends one message to https://appdevelopmentforyou.com/tribes/api/referral. The message is the code, the word ios, Apple's transaction number, the product id, the purchase time, the app version, and the signed transaction. It does not include a name, a family, a post, or a device id. It is not sent over Tor. The TestFlight build does not send it. A restore does not send an old purchase again.
Email. If you email us (Settings → Contact developer, or from a report), we receive what you write and your email address, and use it only to answer you.
Debug log. "Copy debug log" puts the in-memory log on the clipboard. We receive it only if you paste it into a message to us.
Text or share. "Send by text message" and "Share" hand a code you already have to your own messaging app. tribes does not send the text.
Side-loaded test builds (not the Google Play build) may also request https://ccishopsheet.com/daybook/children/version.json about twice a day, and download an update from that same folder. The request uses a fixed label, tribes-updater, and sends no account and no tribes content. The server sees the IP address of the request. You can turn this off in Settings → About & updates. The Play build does not do this.
Purchases (Google Play version)
The Google Play version is a one-time purchase. Each new phone first gets a 10 Day evaluation period (see above). One purchase works on up to 5 phones in your family (see TRIBES code above). Payments are handled by Google Play, under Google's privacy policy. The app never receives your card number, your legal name, or your Google account. Play Billing talks only to the Play Store app on the phone. On that phone, tribes reads the product id, purchase token, and order id, checks them, and keeps them in the encrypted app data. Those values are not copied to the other parent's phone. The purchase token is not sent to us. The order id is sent to us only together with a referral code the parent already accepted, as described above.
The family's TRIBES code reaches the other parent phone and the children's phones inside the encrypted family sync, so those phones can use the same purchase without a second payment. The purchase can be restored from Google Play with the same Google account.
Google Play keeps its usual record of each sale (order number, product, price, and country, and, only where Google is not the merchant of record, state and postal code for taxes). If you contact us about an order we can look it up by the email address on the order. Only parents can buy, always with the parent PIN. A child's phone never shows a purchase screen. Versions installed outside Google Play contain no purchases.
Children's privacy
tribes is designed for families, and children may use it with their parent's permission. A Child phone only works after a parent links it to their Adult phone; by linking it, the parent agrees to these terms for the child. We do not collect personal information from children. On a child's phone:
The child can share text, photos, short videos, a profile picture and a display name, but only as Share with my circle, and only with their own parent phones, their family's tribe, and people a parent approved. A Private diary entry is not included.
A child sees an organization's posts only if their Adult phone turns it on for that child (off by default). A child's request to follow an organization goes to their Adult phone, which decides. Children cannot message an organization.
The parent's Adult phone can see what the child shares with their circle, require approval of every Share with my circle message and picture, remove that shared content, and remove connections. A Private diary entry is not sent to the parent.
Shared messages stay until the person who posted them deletes them, and they can be deleted at any time. The 7-day limit applies only to mailbox and relay copies. On any phone, a post can be taken off with Remove from this phone, and Clear posts older than… in the app removes older posts from that phone by hand. "Erase tribes on this phone" removes all data on that phone, diary included. On a child's phone, a parent types the Adult PIN on that phone, or the Adult phone allows the erase. A phone that has simply lost contact with its Adult phone cannot erase itself.
We never receive information about children, and we do not sell it. Other families receive only the Share with my circle messages a parent approved, phone to phone.
Camera: only when you scan a QR code or take a photo. Recording a video opens the camera app. tribes does not ask for the microphone.
Notifications and a foreground service (data sync): to sync and tell you about new messages and requests.
Wake lock: held only for one sync round so it can finish when the screen turns off.
Network state: to see whether the phone has a network before it tries Tor.
Billing (com.android.vending.BILLING): the Play Billing Library, so a parent can buy or restore on the Play build. The sideload build does not include it.
Install referrer: the Play Install Referrer library. The app reads the referrer from Google Play once, keeps it only in memory, and sends nothing. It is not sent to the developer.
The Play build does not include the sideload updater permissions (install packages, update packages without user action). The advertising-ID permission is removed. There is no location permission.
Deleting your data
Delete a Circle Chat message with its ••• menu, or a diary entry from Diary. Shared posts stay until the person who posted them deletes them. The 7-day wording above applies only to mailbox and relay copies waiting to be delivered. You can also remove posts from your own phone in two ways: Remove from this phone on a post, or Clear posts older than… to remove older posts by hand. These only affect your phone. A private diary entry never leaves the phone that wrote it, and a parent cannot read a child's diary. Settings → Erase tribes on this phone deletes all tribes data on that phone, diary included, and uninstalling also deletes it. On a child's phone, a parent types the Adult PIN on that phone, or the Adult phone allows the erase. We hold no copy, so there is nothing for us to delete.
Crash and diagnostic reports (opt-in)
TRIBES asks once whether you want to send crash and diagnostic reports. They are off unless you turn them on, and you can turn them off at any time in Settings. A report contains only technical details: the app version, the phone model and an error trace with addresses, keys and numbers removed. Reports never contain your posts, photos, messages or contacts.
App version check
To keep everyone on a version that works with the rest of their family, the app asks our server for the lowest supported app version when it starts and at most every 6 hours. The request carries no account, contact or content information. If your version is too old, the app asks you to update.
Changes
If this policy changes, we will update this page and the date above, and show the change in the app when it matters.
Contact
App Development For You LLC
701 East Franklin Street, Suite 105 #1094
Richmond, VA 23219 support@appdevelopmentforyou.com
(804) 404-6359
App Development For You LLC · 701 East Franklin Street, Suite 105 #1094, Richmond, VA 23219 · support@appdevelopmentforyou.com · (804) 404-6359
Friend relay
Friend relay: if a friend's phone hasn't confirmed your post, a parent phone that is friends with both of you may hold a sealed, encrypted copy and hand it over when they sync. It can't read it. It holds at most 50 MB (text and photos, never video) and deletes the copy once it's delivered or after 7 days. Child phones never relay. If nothing confirms it within 30 minutes, the locked mailbox still gets it. The relay phone does not open the copy and passes it on only over the Tor connections it already uses to sync. Nothing is broadcast.