Cherri × Fireweb

Privacy Policy

Scope and responsibility

CHERRI Y.M. SOFTWARE LTD operates Cherri and Fireweb, including the mobile app, community boards and assistants. This policy combines the former Cherri privacy policy and the board privacy notice. Updated 4 November 2026. Contact: contact@cherri.app. Read our Terms of Service for use of these services.

Information we process

We process your phone number, name, account identifiers, optional photo, language, community memberships and connections; verification and consent records; posts, images, uploaded files, extracted text, replies and relevant community knowledge; private assistant messages, responses and activity; and technical data such as IP address, device/browser details, timestamps, errors and security logs. Mobile contact-discovery, location or ride features may also use contacts, location, ride details and the social connections you provide or permit. Board signup does not require access to your address book. Additional mobile permissions are requested by the relevant feature.

Phone verification

We first use Google Firebase Authentication to send a code and verify your phone. Our server validates the resulting signed token and checks that it belongs to the phone being verified. Firebase and reCAPTCHA process phone numbers, IP/device information and challenge signals for verification and abuse prevention. Google receives and stores submitted phone numbers for spam and abuse prevention across Google services. If starting Firebase verification fails, Twilio may deliver the verification SMS instead. Wrong or expired codes do not automatically trigger a second provider’s SMS. See Firebase privacy information and Twilio’s privacy notice.

Why we use information

We use information to authenticate you, maintain your Cherri account and connections, manage community access, display posts and threads, search community knowledge, answer your questions, provide the features you choose, record permissions, respond to support and deletion requests, and protect and improve the service. Where the mobile app uses Firebase Analytics or Crashlytics, Google also processes usage or diagnostic information for those features. We do not require analytics access as part of the board’s SMS form.

Who can see community information

Members of the selected community can see posts, poster details, images, replies and author names. An author’s WhatsApp contact button exposes their verified phone number to those members. Replies and uploaded information can become searchable community knowledge. Text-only knowledge may be returned in assistant answers even if it is not displayed in the poster gallery. Community members can save or forward what they see; treat anything you publish accordingly. If a clear community request or offer cannot be answered from the knowledge base, the assistant may turn it into a poster with request details and your author information so members can respond. Do not include confidential information in such a request.

Private assistant conversations and AI

Your private assistant history is associated with your account, rather than displayed as a general community thread. To answer, AI services can receive the current message, relevant earlier private chat and relevant community information. Providers process that information to perform the requested service. A request may also be published as described above; private greetings and unrelated chat are not intended for publication. AI-generated answers may contain errors. We do not obtain access to your other WhatsApp conversations or groups through ordinary signup or a direct chat with Cherri. The current board pilot searches community knowledge instead of asking other members’ agents.

Hosting, providers and optional WhatsApp

Microsoft Azure hosts the service, account data and uploaded material. Providers involved in operation can include Google Firebase/reCAPTCHA, Twilio for SMS fallback, AI processing services, and Meta when you choose WhatsApp features. Authorized support or technical personnel may access information as needed to operate and protect the service. Providers may process data in other countries. We may disclose information where required by law, to protect rights or safety, or as part of a business transfer with appropriate safeguards. Third-party websites and direct chats opened through links have their own privacy practices. Joining the board alone does not enable WhatsApp updates; available notification and matching choices are presented separately. STOP pauses WhatsApp messages; HELP requests support.

Cookies, storage and security

The board uses a secure, HttpOnly account session cookie with a lifetime of up to 14 days, and local browser storage for language preference. The Firebase verification flow uses temporary authentication state and reCAPTCHA; Google may use its own cookies and related browser technologies for that process. Signing out clears the board session. We use reasonable access controls and technical safeguards, but no internet service or storage method is completely secure. Protect your device and avoid uploading sensitive material unnecessarily.

Retention, choices and rights

We retain information as needed for service operation, legitimate security, record-keeping and legal obligations. You can edit or delete your own board posts, choose what to publish, change available preferences and sign out. For account access, correction, deletion, knowledge removal or questions about a reply, email contact@cherri.app; we may verify your identity before acting. We honor applicable privacy rights. Deleting a post cannot recall copies made by other members, and some records may remain where necessary for legal, security or backup purposes. Historical consent records are not rewritten by a policy update.

Children and changes

The service is not intended for children under 13. Contact us if a child has supplied personal information so we can investigate and take appropriate action. We may update this policy as the service changes, display the revision date, and provide additional notice or obtain consent where required. Questions: contact@cherri.app.