Rybbly Privacy Policy

This policy explains what data Rybbly (“we”, “us”) collects from Businesses and Creators who use the Rybbly platform, why we collect it, and how it’s protected. Using Rybbly means you agree to the practices described here.

Account information: name, email address, and password (handled by Firebase Authentication — Rybbly never sees or stores your raw password).

Profile information: for Businesses — city, business type, budget range, website, and campaign goals. For Creators — city, content category, platforms, handle, follower count, engagement rate, languages, and bio.

Real Follower Percentage (RFP) data: if you run a self-check, we store the Instagram profile link and the follower, average-likes, and average-comments figures you enter, along with the calculated score.

Campaign & application data: campaigns you post or apply to, application messages, and in-app chat messages between a Business and a Creator on an accepted application.

Payment records: the UPI transaction ID, amount, and credit package you submit when buying credits. Rybbly does not process or store card numbers or UPI PINs — payments happen directly between you and our UPI ID, and we only record the reference you give us to confirm it.

Support tickets: the subject, message, and any replies you exchange with our support team.

We use this data to operate Rybbly’s core function — matching Businesses with relevant Creators by city, category, and audience quality — and to run the credits, campaign, application, messaging, and support systems described in our Terms & Conditions. We also use transaction IDs specifically to detect and block duplicate or reused payment submissions.

A Creator’s public profile fields (name, city, category, handle, followers, engagement rate, RFP score) are visible to Businesses browsing or matching for campaigns. A Business’s campaign details are visible to Creators browsing open opportunities. Once a Business accepts a Creator’s application, both parties can see each other’s contact/profile details and message directly in-app.

Rybbly administrators can access account, campaign, payment, and support data as needed to operate the platform, review flagged content, verify payments, and respond to support requests.

We do not sell your personal data to third parties.

Rybbly is built on Firebase (Google) for authentication, database, and hosting — your data is stored on Google Cloud infrastructure and subject to Google’s own security practices. We use Cloudflare Turnstile on our sign-up and login forms to help block automated/bot submissions; Cloudflare may process limited technical browser data as part of that check. Neither service is used to sell or advertise to you based on your Rybbly activity.

Rybbly uses your browser’s local storage to remember your signed-in session (via Firebase Authentication) and your light/dark theme preference. We don’t use third-party advertising or tracking cookies.

All traffic to Rybbly is encrypted over HTTPS. Access to your data in our database is governed by security rules that restrict each account to its own data (and whatever a matched counterpart or admin legitimately needs to see, as described in Section 4) — no user can read or modify another account’s private data directly.

You can review and update most of your profile information directly from your dashboard. To request a copy of your data, ask us to correct inaccurate information, or request account deletion, contact us using the details below — we’ll act on verified requests as required by applicable law.

Rybbly is a business-to-creator marketplace and is not directed at, or intended for use by, anyone under 18. We do not knowingly collect data from children.

We may update this Privacy Policy from time to time to reflect changes to Rybbly or applicable law. Continued use of the platform after an update constitutes acceptance of the revised policy.

Questions about this Privacy Policy or your data can be sent to rybblyai@gmail.com or via the in-app Support ticket system from your dashboard.