← Back to Yebo

Yebo — Privacy Policy & Terms of Use

Last updated: [date]

The short version: Yebo doesn't have a server, a database, or an account system. There is nothing of yours for us to see, store, sell, or lose, because it never reaches us in the first place. Everything you enter lives in your own browser, and if you choose to connect Google Drive, it syncs directly between your browser and your own Drive — never through us.

This page is written to be accurate about exactly how the app works, not boilerplate. If we ever change how the app handles data, this page gets updated to match.

1. What Yebo Stores, and Where

On your device. Everything you enter — your business name, logo, address, payment links (Venmo/PayPal/Zelle/other), invoice history, chosen color theme, and app preferences — is saved using your browser's local storage. It stays on that device, in that browser, unless you take an action that moves it elsewhere.

In your own Google Drive (optional, only if you connect it). If you choose to connect Google Drive, Yebo creates a single file (yebo-data.json) in your Drive and keeps it in sync with what's in your browser, so your data follows you across devices. That connection is made directly between your browser and Google's servers. It does not pass through us, because there is no "us" in the middle — we don't run a server that could see it even if we wanted to.

While Drive is connected, your browser also keeps Google's short-lived access token (it expires after about an hour) in local storage, so returning to the app soon after doesn't need another sign-in. It never leaves your device except to talk to Google, and disconnecting removes it.

The Google permission Yebo requests (drive.file) is intentionally narrow: it only allows the app to see and edit the one file it created. It cannot browse, read, or touch anything else in your Drive.

What's in that file, specifically: your business profile (name, email, address, logo, payment links, theme choice) and your full invoice history, including any split-payment (deposit/balance) invoices.

2. What Yebo Never Collects

We don't have:

  • User accounts, sign-ups, logins, or passwords for the app itself
  • A backend server or database of our own
  • Analytics or usage tracking
  • Advertising, ad networks, or ad tracking
  • Cookies that we set

If it isn't listed above as something we store, we don't have it — not "we don't look at it," but structurally, there is nowhere for it to go.

3. Third-Party Services This App Talks To

Being server-free doesn't mean zero third parties are ever involved — a couple of things load directly in your browser from other companies' servers, which is worth being upfront about:

  • Google Fonts — the app's typefaces are loaded from Google's font servers. Loading a font means your browser makes a direct request to Google, which sees the requesting IP address, the same way it would for any website using Google Fonts.
  • Google Identity Services (accounts.google.com) — powers the "Connect Google Drive" sign-in flow. This is Google's own login screen, not something we build or see the contents of.
  • Cloudflare CDN (cdnjs) — a handful of small, well-known open-source libraries (for PDF export, QR code generation, and the payment-page animation) are loaded from Cloudflare's public CDN rather than bundled into the app itself.
  • Google Drive API — only contacted if and when you connect Drive, as described above.

None of these services receive your invoice data, business info, or anything you type into the app — they're only involved in loading fonts, code, and (if you opt in) the Drive connection itself.

4. Payment Links

Yebo can generate a "Scan to pay" link and QR code for your invoices, linking to a page listing your Venmo, PayPal, Zelle, or other payment details. A few important clarifications:

  • Yebo does not process, handle, or touch any payment. We're not a payment processor. Tapping "Pay with Venmo" or "Pay with PayPal" sends the person to that company's own site or app, under that company's own terms and privacy practices — not ours.
  • Zelle doesn't support payment links industry-wide, so instead of a broken "pay" button, Yebo simply displays the contact info you provided (email/phone) for the payer to copy and use in their own banking app.
  • The payment-page link itself is generated entirely client-side — your payment details are encoded directly into the link/QR code, not stored on any server.

5. Your Control Over Your Data

Because everything lives locally (and optionally in your own Drive), you're always in direct control:

  • To remove data from this device: clear your browser's site data for this app, or use the in-app delete controls for individual invoices.
  • To stop syncing to Drive: disconnect Google Drive from within the app at any time. This revokes the app's access token; the yebo-data.json file remains in your Drive (since it's your file, in your Drive) unless you delete it yourself.
  • To fully delete everything: clear local browser storage and delete the yebo-data.json file from your Drive, if you connected it.

We have no ability to do any of this on your behalf, because we have no access to do it in the first place.

6. Children's Privacy

Yebo is a business tool intended for use by adults running or managing a freelance/small business. It is not directed at children, and we do not knowingly collect information from children, in keeping with everything above — we don't collect information from anyone, of any age.

7. Changes to This Policy

If how the app handles data ever changes — for example, if a future feature introduced a server-side component — this page will be updated to accurately reflect that, and the "Last updated" date at the top will change accordingly. We won't quietly change what's true here without updating the page.

8. Terms of Use

No warranty. Yebo is provided "as is," free of charge, without warranties of any kind, express or implied. We don't guarantee it will be error-free, uninterrupted, or fit for any particular purpose.

Your responsibility. You are responsible for the accuracy of the invoices, business information, and payment details you create and send using this tool. Yebo does not verify, audit, or guarantee any of the content you generate.

Limitation of liability. To the fullest extent permitted by law, we are not liable for any damages, financial or otherwise, arising from your use of this app — including but not limited to data loss (e.g., clearing browser storage without a Drive backup), invoicing errors, or issues arising from third-party payment services you link to.

Third-party services. Your use of linked third-party services (Google Drive, Venmo, PayPal, Zelle, etc.) is governed by those companies' own terms and policies, not ours.

No liability for third-party outages. If Google, Cloudflare, or any other third-party service this app depends on is unavailable, slow, or changes its behavior, that's outside our control.

Contact

Questions about this policy: legal@yebo.nyc

This document was drafted to accurately reflect Yebo's actual technical implementation as of the date above. It is written for clarity and accuracy, not by a lawyer — if you plan to publish this for a business with real users, it's worth a quick review by one, particularly around the Terms of Use / liability section, which varies by jurisdiction.

← Back to Yebo