Privacy Policy
ARBEEF is an augmented-reality fighting game for iPhone and Android made by Egor Sharapov ("we", "us"). This policy explains what data the app and this website handle, why, and what you can do about it. The short version: we keep as little as we can, your photos are not stored on our servers, your finished fighters are kept in our cloud only so you can play them on your other phones (you can turn that off), and what happens in a fight is not recorded.
1. Who is responsible
Egor Sharapov, an individual developer, is the data controller for ARBEEF. Questions and requests go to hello@arbeef.app.
2. What we collect and why
Account
On iPhone you sign in with your Apple ID. Apple gives us a stable anonymous identifier for your account and, if you choose to share it, your email address (Apple's "Hide My Email" relay addresses work too). On Android you sign in with your Google account. Google gives us a stable identifier for your account and your email address; we store the email only if Google says it is verified, and we do not store your name or profile picture. We use the identifier to keep your credit balance attached to you and the email, when present, only to contact you about your account. We never see your Apple or Google password.
On iPhone you can also play as a guest without signing in. The app then keeps a random secret in your phone's Keychain, and we store only a fingerprint (hash) of that secret to recognise the same guest account after a reinstall. A guest account has no email. If you later sign in with Apple, the guest account and its credits move into your Apple account.
Photos and generated fighters
To create a fighter you send us a photo. Our server forwards it to Tripo (Tripo3D, operated by VAST) to generate a cartoon concept and a 3D model, and does not keep a copy. Tripo processes the photo under its own privacy policy. The finished fighter is downloaded to your phone; we keep a short-lived job record (status, error, temporary download links) so the app can pick up the result if it was interrupted.
Fighters in the cloud
So that you can play your fighters on your other phones (iPhone or Android, signed in to the same account), the app keeps a copy of each finished fighter in our cloud storage: its 3D model files, its name and when it was made and changed, never the photo, up to 300 fighters per account. The copy is stored with Cloudflare (R2), tied to your account, and only you can read it, through our server. It is on once you sign in (with Apple on iPhone, with Google on Android; a guest account on iPhone keeps fighters only on the phone); the app tells you so once, before the first copy is made. Turn it off any time in the app under Settings → Fighters in your account: that deletes the copy from our storage, and your fighters stay on your phone. Deleting a fighter also deletes its cloud copy. On iPhone the app also keeps its own copy of your fighters in your iCloud, which is Apple's storage under your Apple ID, not ours.
Only upload photos you have the right to use. If you photograph another person, make sure they are fine with it.
Purchases and credits
On iPhone credits are bought through Apple's In-App Purchase. Apple handles payment; we never see your card. We receive the transaction identifier and product from Apple, verify it, and record it in a credit ledger (purchases, spends, automatic refunds for failed generations). Apple also notifies us about refunds and revocations so we can adjust your balance.
On Android credits are bought through Google Play Billing. Google handles payment; we never see your card. The app sends us the purchase token and product; we verify them with Google Play, record the order identifier in the same credit ledger and confirm the purchase to Google. Google Play notifies us about refunds and revocations so we can remove the corresponding credits.
Push notifications
If you allow notifications, the app sends us your device's push token (from Apple Push Notification service on iPhone, Firebase Cloud Messaging on Android) and we keep it with your account to tell you about your startup beefs — a new challenge, a rival in the room, a beaten bot. A new token replaces the old one; we delete it when Apple or Google tells us it is no longer valid, or when you delete your account.
Fights
Multiplayer runs between two phones. In the same room they talk directly over the local network (Wi-Fi or peer-to-peer). When you fight someone far away through a fight link, the phones first connect through our server, which forwards fight messages and both fighters' 3D models between them and keeps neither. Where the networks allow it, the phones then switch to a direct connection set up with the help of Cloudflare's STUN/TURN service: to make it, each phone shares its network addresses (IP addresses and ports) with the other player's phone. If a direct path is not possible, the traffic goes through Cloudflare's TURN relay, which forwards it without reading or storing it. In a fight over a link you can turn on voice chat (it is off unless you do): your voice then goes directly from your phone to the other player's, or through Cloudflare's TURN relay, and is never recorded or stored — by us or in your fight reels. A fight room lives only until its first fight and no longer than 7 days; it holds a code, a secret, the host's player name, the host's fighter name and picture for the link preview, and timestamps. What happens in a fight — positions, inputs, camera frames — is not stored by us; we only learn, through the analytics below, that a fight started and ended, who won, how long it lasted, the connection type (local, relay or direct) and its latency — never your IP address. The camera image is processed on the device by its AR framework (ARKit on iPhone, ARCore on Android) to find the floor and the arena anchor and is never uploaded.
Diagnostics and usage
- PostHog collects product analytics and crash reports.
- Usage: how far you get in the app — whether the arena was placed, whether a fight finished, who won and how long it took, whether a fighter generation succeeded and how long it took, whether a credit purchase went through (the pack and its price, never your payment details).
- Crashes and errors: device model, OS and app version, a stack trace, and the last few app states before the problem.
- Cloudflare hosts our API and this website and keeps standard request logs (IP address, request path, timing) for a short period for security and debugging.
- Apple may share crash logs and analytics with us if you opted in on your device; that is governed by Apple's privacy settings.
- Google may share crash and performance data from Android devices with us through Android vitals in Google Play if you opted in to sharing usage and diagnostics on your device; that is governed by Google's settings.
This website
This site sets no cookies and stores nothing in your browser except the language you pick. It sends PostHog two kinds of events: that a page was viewed (its address, the referring site and campaign tags, browser, OS and screen size) and that an App Store button was tapped. They carry no identifier that outlives the page: every visit counts as a new, anonymous visitor. PostHog uses your IP address to look up your approximate location (country and city), then discards it. Fonts are loaded from Google Fonts, which sees your IP address.
3. How long we keep it
- Account and credit ledger — until you delete your account.
- Sign-in tokens — up to 90 days, then they expire on their own.
- Apple purchase notifications — 90 days.
- Generation job records — a short period after the job finishes.
- Fighters in the cloud — until you delete the fighter, turn the switch off or delete your account. We keep a note of a deleted fighter's identifier and when it was deleted, so your other phones remove it too.
- Push token — until it is replaced, becomes invalid, or you delete your account.
- After deletion — we keep only a marker that your Apple or Google identifier has already received its free starter credits, so they cannot be claimed again. Nothing else.
- Crash and analytics data — up to one year in PostHog, then deleted.
4. Your choices and rights
- Delete your account in the app under Settings → Delete account (on iPhone and Android), or by emailing hello@arbeef.app from the address on your account or with your account details. It removes immediately your account, credit balance and ledger, sign-in and push tokens, the cloud copy of your fighters, and your referral code; startups you own become unclaimed. Only the marker described above is kept.
- Delete a fighter in the app; it is removed from your phone, our cloud copy and our job records, and on iPhone from your iCloud.
- Keep fighters only on your phone: turn off Settings → Fighters in your account; the cloud copy is deleted.
- Access or correct your data, or ask us to delete it, by emailing hello@arbeef.app. We answer within 30 days.
- Refunds for purchases go through Apple or Google Play, wherever you bought, per their policies.
Depending on where you live you may have additional rights (for example under the GDPR or the CCPA), including the right to complain to your data protection authority. We honour those rights on request.
5. Where data goes
Our API and the cloud copy of your fighters run on Cloudflare's global network; Tripo runs in the United States and/or the EU; PostHog stores our analytics in the United States; Apple (on iPhone) and Google (on Android) handle sign-in, payments and push notifications. By using ARBEEF you accept that your data may be processed in those locations, protected by the providers' standard contractual terms.
6. Children
ARBEEF is not intended for children under 13 (or the age required in your country to consent to data processing). We do not knowingly collect data from them; if you think a child has created an account, email us and we will delete it.
7. Changes
We may update this policy as the app changes. The effective date at the top tells you when it was last revised; material changes will also be announced in the app.
See also the Terms of Service.