Privacy Policy
IBridge helps newcomers learn local customs, events, useful links, and local offers. This policy explains what data we collect, why, and your choices. We do not sell your data and we do not use data brokers. We show labeled first-party Sponsored campaigns from local advertisers who pay IBridge directly. On Explore (posts) and Events, if you have no local ad left for that UTC day, that slot may show a Google AdMob native ad instead. Offers stays local campaigns only. Google labels those ads with its own Ad badge. We do not send your community profile to Google.
1. Data we collect
Depending on how you use the app, we may process:
- Account & identity: email address, display name, password hash (if you register with email), and identifiers from Google Sign-In or Sign in with Apple when you choose those options.
- Profile & preferences: preferred language, country/region selection, reputation/points, and role (e.g. member, moderator).
- Content you create: tips, comments, votes, reports, and related metadata (timestamps, status, moderation decisions).
- Organisation events: if you register, we store your seat, attendance, waiting-list place, and optional feedback for that organisation’s event.
- Volunteer meetings: if an organisation invites you as a volunteer, we store your name, email, phone, expertise, and photo, and the times you publish (an online link or an in-person address). If you ask for a time, we store that request and whether it is pending, confirmed, or declined. The in-person address is shown on the free time. The volunteer’s phone and the meeting link are shown to the person who asked only after the volunteer confirms. We notify the volunteer of a new request, and we notify the person who asked when it is confirmed or declined. After a confirmed meeting has ended, the person who asked can leave a rating and a comment. The volunteer and the organisation admin can read it.
- Phone number (optional): if you verify a phone number, we store the number (E.164) and derived country code for access and moderation scoping.
- Search queries: text you search, sent to our servers to return matching tips/resources. We do not maintain a long-term personal “search history” product feature.
- Device tokens: Firebase Cloud Messaging (FCM) tokens so we can send notifications (e.g. moderation or account-related alerts).
- Advertising measurement (anonymous): a device or account viewer key used only to count unique daily views and clicks on IBridge Sponsored campaigns and to cap how often the same local ad is shown. This is not sold or used for third-party retargeting.
- Google ads (fallback only): when a Google ad is shown, Google may process an advertising identifier, IP address, and ad interaction data under Google’s privacy policy. In the EEA/UK we ask for your consent before requesting those ads. You can refuse. The app still works, and local Sponsored cards are unchanged.
- Advertiser accounts: if you create an advertiser profile, business name, website, campaign creatives, billing/wallet records, and payment processor identifiers (Stripe).
2. How we use data
- Provide and operate the app (authentication, feed, search, events, links, teens content, Offers).
- Moderation, trust & safety, fraud/abuse prevention.
- Translate or display content in your preferred language.
- Send transactional / in-app notifications you enable.
- Serve and bill labeled Sponsored campaigns (impressions, clicks, coupons) for advertisers who pay us.
- Show a Google ad in an Explore or Events slot only when no local Sponsored ad is left for you that day. We do not bill local advertisers for those Google ads.
- Customer support and fixing bugs / improving reliability.
We do not use your community profile (posts, name, interests, or messages) to target Google ads, and we do not sell it to data brokers.
3. Legal bases (EEA/UK where applicable)
We process data where needed to:
- Perform our contract with you (provide the service you request);
- Ask for your consent before requesting Google ads in the EEA/UK;
- Comply with legal obligations; and/or
- Pursue legitimate interests such as securing the service and moderating community content, balanced against your rights.
4. Sharing
We share data only with processors that help us run IBridge, for example:
- Hosting / database: Railway (API and data storage).
- Authentication / push: Google (Sign-In, Firebase Cloud Messaging) and Apple (Sign in with Apple), as applicable.
- Payments (advertisers): Stripe, to process wallet top-ups.
- Advertising (fallback): Google AdMob, only to fill an Explore or Events slot when no local Sponsored ad is available for you that day.
- AI translation providers: when content is translated on demand (e.g. Google Gemini / OpenAI), only the text needed for translation is sent.
We may disclose information if required by law or to protect users and the service from abuse or security threats.
5. Retention
We keep account and content data while your account is active and as needed for moderation, legal, and security purposes. You may request deletion of your account (see Contact). Server logs and short-lived caches are retained only as long as needed for operations. If you register for an organisation event, we keep that registration, attendance, and any feedback after the event ends so the organisation can report what happened. A check-in code is not stored as an image. It stops working when attendance is finalized. A registration pause applies only to the organisation that issued it. Anonymous feedback is stored without your user id. Events a normal user posts are deleted after they end. A volunteer meeting request stays with that organisation while the volunteer profile exists. Removing the volunteer removes their times and requests.
6. Security
We use industry-standard measures such as HTTPS, hashed passwords, and access controls. No method of transmission or storage is 100% secure.
7. Children’s privacy
IBridge is not directed at children under 13 (or the minimum age required in your country). Teens-related content is informational guidance; we do not knowingly collect data from children below the applicable age without appropriate consent.
8. Your rights
Depending on where you live, you may have rights to access, correct, delete, or export your personal data, and to object to or restrict certain processing. Contact us to exercise these rights. You may also lodge a complaint with your local data protection authority.
9. International transfers
Our infrastructure and subprocessors may process data in the EU, US, or other countries. Where required, we rely on appropriate safeguards (such as standard contractual clauses) with providers.
10. Changes
We may update this policy. We will post the new version with an updated effective date. Continued use of the app after changes means you accept the updated policy.
11. Contact
Privacy questions or deletion requests:
mohammadrezaimn@gmail.com
To delete your account and associated data, follow the steps on our Delete Account page. See also our Terms of Use.