Privacy Policy
Last updated: 22 October 2026 · Applies to com.yaz.app
Yaz is a “save-for-later” app for links. This policy explains exactly what Yaz accesses, what it stores, where that data lives, and the choices you have - across the mobile app, the browser extension, and the optional Telegram backup.
The short version. Yaz works fully offline with no account, and your library stays on your device. If you turn on the optional Telegram backup, each link you save is also posted as an ordinary, readable message to your own private chat with the Yaz bot. These messages are not end-to-end encrypted - they are stored by Telegram like any other chat. Our server only relays requests to Telegram and stores none of your data. We don’t sell your data and we don’t show ads.
1. What Yaz collects
Links you choose to save
When you save a link, Yaz stores the information you give it: the URL, and - fetched automatically from the public page - its title, description, thumbnail/preview image, site name, and detected platform (e.g. TikTok, YouTube, Instagram). You can also add your own note, tags, title, folder, favorite flag, and reminder. Yaz acts only on links you explicitly save; it does not monitor your browsing or your other apps.
If you turn on Telegram backup - your Telegram identity
Telegram backup is optional and off by default. To connect, you tap Start in your chat with the Yaz Telegram bot. Yaz then receives your Telegram user ID (which is also your chat ID with the bot), first name, and username. These are used only to address your own chat with the bot and to show “Connected as @username” in the app. Yaz does not request your phone number or profile photo.
If you turn on Telegram backup - the backup messages
While connected, each link you save in Yaz is posted to your private
chat with the Yaz bot as a normal text message containing its
title, URL, folder names (as hashtags, e.g. #Recipes), and your
note if it has one. Editing a link updates its message;
deleting a link deletes its message. A pinned file,
yaz-backup.json, in the same chat holds your whole library
(links and folders) so it can be restored on a new phone or after a
reinstall. This content passes through our server on its way to
Telegram but is not stored by us.
A session token
After you connect, a signed session token is stored securely in your
phone’s keychain (via expo-secure-store). It is tied to
your own Telegram chat, expires after 180 days (renewed automatically
while you use the app), and is sent over HTTPS to authorize backup
requests.
If you join the beta - your email address
When you submit your email on this website to join the Google Play closed test, we store that email address solely to enroll you as a tester and send the invite. This is separate from the app itself and is covered in How data is used below.
2. What Yaz does not collect
- No browsing history, and no pages you didn’t explicitly save.
- No contacts, no location, no advertising identifiers.
- No third-party analytics or ad SDKs in the app.
- The Telegram bot cannot read your other Telegram chats or contacts - a bot only ever sees its own chat with you.
- Links you send to the bot are not saved to your library - the bot just replies with a hint to save from the Yaz app.
3. How data is used
Your data is used only to provide the features you asked for:
- Saved links - to build, display, search, and organize your library.
- Telegram identity - to address your own chat with the bot and show which account is connected.
- Backup messages & file - to give you a readable copy of your links in Telegram and restore your library on a new phone.
- Session token - to keep you connected and authorize backup requests.
- Beta email - to enroll you in the closed test and send the invite link.
We do not:
- sell, rent, or share your data with third parties for advertising;
- use your data for profiling, creditworthiness, or lending decisions;
- use your beta email for marketing unrelated to the test.
4. Where data is stored
- On your device. Your library is the source of truth and lives in on-device storage (SQLite). With Telegram backup off, your library never leaves your device.
-
In your own Telegram chat (backup on). Your links are
posted as readable messages, plus the
yaz-backup.jsonfile, in your private chat with the Yaz bot. They are stored by Telegram on its servers like any other chat and are not end-to-end encrypted. - The Yaz server (backup on). A small, stateless API hosted on Vercel holds the bot’s credentials and relays the app’s requests to Telegram. It has no database and stores no user data. Vercel keeps short-lived request logs (such as method, path, status, and your Telegram chat ID - never message contents or tokens).
- Beta email list. Tester emails submitted on this site are stored in a database hosted by Supabase and used only as described above. Supabase is not used by the app.
All network transmission uses HTTPS / TLS.
5. Third-party services
- Telegram - used to connect your account and as the place your backup messages and backup file are stored, in your own chat with the Yaz bot. Telegram’s own privacy policy applies to that content.
- Vercel - hosts the stateless Yaz API, which processes backup requests in transit and stores nothing.
- Supabase - stores only the email addresses submitted through this website’s beta sign-up form.
- Link previews. To build a preview, the app fetches the public page of a link you save (its Open Graph / oEmbed metadata) directly from that site, the same way a browser would.
6. Security
- Encrypted in transit. Everything between the app, our server, and Telegram travels over HTTPS / TLS.
- Not end-to-end encrypted. Backup messages and the backup file are ordinary Telegram messages. Anyone with access to your Telegram account can read them, and Telegram stores them like any chat.
- Your chat only. Every request is authorized with a signed session token bound to your own Telegram chat, so one user can never reach another user’s chat.
- Nothing stored on our server. The Yaz API has no database; there is no copy of your library for us to lose.
- Secure on-device storage for your session token via the platform keychain.
No method of transmission or storage is 100% secure. If you need your links to stay private from Telegram, leave Telegram backup off - your library then stays on your device only.
7. Retention & deletion
- Local data remains on your device until you delete links or uninstall the app.
- Telegram backup messages and file stay in your chat with the Yaz bot until you delete them. Deleting a link in Yaz deletes its message.
- Delete Telegram backup (in the app’s Telegram screen, under Settings → Sync) removes every message and the backup file Yaz posted in your bot chat and disconnects. You can also delete or clear the chat yourself in Telegram. See the Delete account & data page.
- Our server keeps nothing beyond Vercel’s short-lived request logs described above. There is no server-side account or stored data to delete.
- Beta email. Email us to be removed from the tester list at any time.
8. Your rights & choices
- Use Yaz with no account - keep everything local.
- Disconnect Telegram at any time in the app; this removes the session token from that device. Your links stay on the device and in Telegram.
- Access & export - your full library lives on your device, and (with backup on) in your own Telegram chat, including the
yaz-backup.jsonfile. - Delete - remove individual links, or your whole Telegram backup, at any time.
Depending on where you live, you may have additional rights (access, correction, deletion, portability). Contact us and we’ll help.
9. Children
Yaz is not directed to children under 13 (or the minimum age in your country), and we do not knowingly collect their data. If you believe a child has provided us data, contact us and we’ll delete it.
10. Google Play Data Safety summary
This table summarizes our practices to match Google Play’s Data Safety framework.
| Data type | Collected? | Purpose | Shared? |
|---|---|---|---|
| Email address (beta sign-up) | Yes, if you join the beta | Enroll tester & send invite | No (stored with Supabase as our processor) |
| User IDs (Telegram user ID, first name, username) | Yes, if you turn on Telegram backup (not stored on our server) | Address your own bot chat; show the connected account | No |
| Saved links, notes & folder names | Stored on your device; sent to Telegram only if you turn on backup | App functionality & backup | Only with Telegram, at your request, when backup is on |
| Location, contacts, browsing history, ad IDs | No | - | No |
Data is encrypted in transit (HTTPS / TLS) but is not end-to-end encrypted once it is in your Telegram chat. You can delete your data yourself in the app or in Telegram, and we do not sell your data.
11. Changes to this policy
If we make material changes, we’ll update the “Last updated” date above and, where appropriate, notify you in the app. Continued use after an update means you accept the revised policy.
12. Contact
Questions, data requests, or deletion requests:
jossyfreelancer@gmail.com