PeachyBind is operated by Bernardo Costa, an individual based in Portugal, who acts as the data controller for personal data processed through cookies and similar technologies. This notice explains how cookies and similar technologies are used on the public website, web collector studio, and related apps. For how personal data is handled overall, see the Privacy Policy. Questions: astrylvyan@gmail.com.
Cookies are small text files stored on your device. Similar technologies (local storage, session storage, pixels, SDK identifiers on mobile) can serve comparable purposes. Some are set by PeachyBind; others by partners such as Google when ads or sign-in run.
| Category | Purpose | Typical legal basis (EEA) |
|---|---|---|
| Strictly necessary | Keep you signed in on the web studio, protect sessions (including Firebase Authentication and App Check), and load the app securely. | Legitimate interests / necessary for the service you request |
| Preferences | Remember choices such as theme or support-strip opt-in where stored locally. | Legitimate interests / performance of a contract |
| Advertising (when enabled) | In the signed-in web studio (wide desktop support strip) and in mobile apps, Google AdSense (web) or AdMob (mobile) may use cookies or device identifiers after consent where required. Unity may receive consent signals when mediated through AdMob. | Your consent where required by law (e.g. EEA/UK); otherwise legitimate interests where permitted |
| Partner sign-in | Google Sign-In may set cookies when you authenticate in the web studio. | Performance of a contract / your request to sign in |
| Diagnostics (mobile) | Firebase Crashlytics may associate crash reports with an installation identifier (not used for marketing). | Legitimate interests (reliability and security) |
PeachyBind does not use a separate third-party web analytics SDK (such as Google Analytics 4) in current app builds.
Static marketing pages on peachybind.com (home, FAQ, how-it-works, legal) do not load Google AdSense or Funding Choices; site ownership for ads is declared via ads.txt on the apex domain.
Operational logs on servers are described in the Privacy Policy and are not browser cookies.
| Context | Examples | Purpose |
|---|---|---|
| Marketing pages (peachybind.com) | Minimal hosting or CDN cookies only; no AdSense display tag and no Funding Choices CMP on these static HTML pages | Deliver pages securely |
| Collector studio (beta.peachybind.com /app) | Firebase Auth session; browser local storage for app state; Google Funding Choices / IAB TCF when the optional support strip requests ads; AdSense script loads only after consent via the in-app web loader | Account access, sync, optional ads after consent |
| Mobile apps (Android / iOS) | Firebase / Google SDK storage; advertising ID when ads run; App Check tokens; Google UMP when ads use production units | Auth, sync, ads (with consent where required), security |
Exact names and lifetimes can change when I update Firebase, Google ads, or app versions. Third-party providers may set their own cookies when their features load — see their policies (Google Cookies, Stripe Cookies when checkout is shown).
You can exercise broader privacy rights (access, deletion, objection) as described in the Privacy Policy.
Questions about cookies or privacy: astrylvyan@gmail.com. I may update this notice; the date above will change.
Privacy Policy · Terms of Service · Delete account · Community Guidelines