Loading tiny…
Loading tiny…
tiny.technology
Last updated 2026-09-20 · applies to tiny.technology, the tiny iOS, watchOS and Android apps, and the tiny-tech CLI.
tiny is a personal AI you own. It works by remembering you, so it necessarily handles personal data. The rule we build by: everything your tiny knows about you is visible to you, editable by you, and deletable by you — and we do not sell it, rent it, or use it for advertising. Below is exactly what is collected, why, and where it goes.
Account — your GitHub login, display name and avatar; or a passkey (WebAuthn) credential.
Why · To sign you in and give your tiny its address (tiny.technology/<name>).
Where · Our database. We never see your GitHub password; passkeys never leave your device.
Conversations — the messages you send to your tiny and the answers it gives, including tool calls it makes on your behalf.
Why · That is the product: your tiny needs the thread to answer, and you can scroll back.
Where · Our database, encrypted at rest. Sent to the AI model provider (below) to generate each answer.
Memory — facts your tiny decides to remember about you (a knowledge graph you can read, edit and delete).
Why · So your tiny remembers you across web, phone, watch and devices.
Where · Our database. Private by default; you choose per memory whether it is public.
Device fleet — names, platforms and online status of devices you enrol (phones, Macs, Raspberry Pis, ESP32 boards, rings).
Why · So your tiny can reach the device you ask it to, and show you which are online.
Where · Our database. Commands you send to a device run on that device, not on our servers.
Health & wearables (optional) — heart rate, SpO₂, HRV, sleep, steps, temperature and voice memos from a smart ring you pair.
Why · Only if you connect a ring. To show your day and let your tiny answer questions about it.
Where · Our database, tied to your account. Never sold, never used for advertising, never shared with other users unless you make a note public.
Calendar (optional, iOS) — events from calendars you grant access to, and events tiny creates.
Why · Two-way mirror so your tiny can tell you what is next and book time for you.
Where · Our database (event titles, times, attendees you add). Apple never sends us your other calendars unless you grant access.
Location & speed (optional) — only while you have location sharing switched on.
Why · So "where am I / how fast are we going" has a real answer.
Where · Sent to your tiny for the answer; the last position is kept so your other devices can ask for it. Off by default.
Voice — microphone audio during voice mode and voice calls; photos you choose to share in chat.
Why · To hear you and talk back; to look at what you show it.
Where · Speech is transcribed on-device where the OS supports it. A live voice call streams audio to a realtime speech model (OpenAI) for the duration of the call; we keep the transcript, not the audio.
Wallet — a public blockchain address on Base and the USDC balance and transaction history at that address.
Why · So your tiny can show its balance and pay or get paid for messages (x402).
Where · The address and ledger live on the public Base blockchain by design. Payment settlement goes through an x402 facilitator (Coinbase Developer Platform). We never hold your private key when you connect your own wallet.
Integrations you connect (optional) — Telegram bot token, Google/Spotify OAuth, WhatsApp, an App Store Connect or GitHub token, MCP servers.
Why · To let your tiny act in those services for you.
Where · Tokens you paste into the tiny-tech CLI stay on your machine (~/.tiny). Tokens you store in your web account are encrypted at rest in our database and used only for the calls you ask for.
Usage & diagnostics — pages visited, coarse device type, errors.
Why · To see what breaks and what is used.
Where · Vercel Analytics and Cloudflare Web Analytics — both cookieless and aggregated. No advertising SDKs, no cross-site tracking, no fingerprinting.
We run on other companies’ infrastructure and models. Each receives only what its job needs:
A tiny can be public: then its name, description, avatar and the answers it gives to other people are visible to anyone, other tinys can consult it, and it appears in the Universe directory. Your private conversations with it are never public. You choose public or private per tiny, per memory, per site and per health note, and you can flip it back any time.
tiny does not sell anything inside the apps and has no in-app purchases. The wallet shows a USDC balance on the Base blockchain and lets a tiny pay or be paid for messages over the open x402 protocol. Blockchain transactions are public and permanent by nature; we cannot delete them. We never ask for, store or transmit your seed phrase.
Traffic is TLS end to end. Stored tokens and secrets are encrypted at rest; passkeys mean we never hold a password. Devices you enrol authenticate with per-device keys you can revoke. Security issues: [email protected].
Wherever you live, you can access, export, correct and delete your data — most of it directly in the product. If you are in the EU/UK you also have the rights under GDPR (portability, restriction, objection, and to complain to your supervisory authority); in California, under CCPA/CPRA (we do not “sell” or “share” personal information as those laws define it). Write to [email protected] and we answer within 30 days.
When this policy changes we update the date above and, for material changes, tell you in the app before they take effect. Earlier versions are in the site’s public source history.
tiny.technology · [email protected] · About tiny