COMMUNITY INITIATIVE · DISTRICT 2452
Privacy policy
Provisional notice · Updated 17 November 2026
Member community and moderation
Community access requires approved club membership. Community profiles show usernames, not actual names. Identity sharing requires mutual private consent; revoking consent stops future display but cannot undo information already seen. District chat is visible to verified members; private messages are visible to their participants, but all submitted messages are screened by the AI service before delivery. Messages flagged for abuse are blocked and retained for administrator review. Automated screening can make mistakes and cannot detect every abuse. Email incident reporting to support@ilegal.solutions is not active until the sending domain is configured. Do not submit confidential information.
People's details and sign-in
General club facts remain public, and visitors may ask three questions about non-personal information. Officer names and personal contact details displayed by this platform require sign-in and must come from approved public sources. Guest answers do not use full captured source text or extended notes that may contain people's details. If information is unavailable after sign-in, consult the relevant club website. Having an account does not permit disclosure of private personal data.
Operator and notice status
Amer Nabulsi operates this independent community initiative. This is a provisional privacy notice dated 17 November 2026, not a certification of GDPR or local-law compliance. The operator’s legal address, direct privacy contact, applicable legal bases, processor locations, retention schedule and any required representative or data-protection officer must be confirmed before public launch. Do not send privacy requests to Rotary or the district: they are not identified as this initiative’s data controller.
Information processed and purposes
Account information includes email, display name, optional avatar and language preference, plus sign-in information handled by the account provider. Signed-in questions and answers are stored to maintain your saved conversation. Optional thumbs up/down, one-to-five scores and written feedback from guests and account holders are stored privately for administrator quality review. They do not automatically train or fine-tune the AI, and are not included in public-source exports or external training transfers. Questions and relevant conversation context are sent to the AI service to produce answers. Hosting and security providers may process network addresses, device/request information and logs. Public club and officer records are drawn from approved public sources. Avoid sensitive or third-party personal data in questions or feedback.
Legal bases and choice
Where applicable, processing necessary to provide the requested account and conversation service may rely on performance of a service arrangement; necessary security may rely on a documented legitimate interest, subject to balancing and local requirements. Optional analytics would require appropriate consent where required. These bases are not interchangeable across all nine countries: the operator must assess and document the applicable basis, notices, consent and registrations. Withdrawal of consent does not affect earlier lawful processing.
Providers, sharing and international transfers
Lovable Cloud provides hosting, account and data services; Lovable’s AI service routes questions to the configured AI provider. Firecrawl processes administrator-selected public source URLs and documents, not private account exports. Google/Lovable sign-in, when selected, is also subject to those providers’ practices. No AWS training transfer is configured; approved-source exports exclude chats and profiles. Data may be processed outside your country. Actual locations, subprocessors, agreements, transfer assessments and any required safeguards such as EU standard contractual clauses or local approvals must be verified before public launch; no localisation or adequacy guarantee is made here.
Cookies, analytics and IP limits
Essential browser storage supports account sessions and language preferences. A first-party HttpOnly cookie identifies a temporary guest conversation and enforces three questions for 30 days, including after closing the browser. Its token is stored only as a hash on the server. Guest questions and answers are sent to the AI service and stored privately so you can resume or sign in to save them to your account. Expired guest records are deleted when guest access is next processed; backups follow hosting retention practices. Clearing cookies or switching browsers can reset this allowance. IP-based blocking is not enabled. Google Analytics is not connected; non-essential analytics require consent where legally required. Hosting telemetry may follow the platform’s own practices.
Retention and security
Account conversations currently remain stored; automatic retention deletion is not configured. Capture versions remain available for administrator review. A final, purpose-based retention and backup-deletion schedule is required before launch, including handling inactive accounts, security logs and withdrawn content. Account-owned access controls protect saved conversations and role-checked access protects administration. No system can guarantee absolute security. The operator must assess incidents and notify affected people and authorities within applicable legal time limits where required.
Your rights and complaints
Depending on applicable law, you may request access, correction, erasure, restriction, objection, portability, consent withdrawal and information about processing and transfers. You may complain to the competent supervisory authority or court, including the Cyprus data-protection authority where applicable. GDPR requests are normally answered within one month, subject to lawful extensions; other countries’ deadlines apply where relevant. Identity verification may be needed without collecting excessive information. Profile corrections are available through My account; export, erasure and other requests need an operator contact, which has not yet been supplied. There is no solely automated decision intended to produce legal or similarly significant effects.
Children and updates
This initiative is not designed to collect children’s personal data. Minors should use it only with appropriate parent or guardian involvement and the permissions required by local law, without sharing personal information. Country-specific age and consent requirements must be assessed before launch. Material changes to this notice will be dated and explained; new purposes requiring consent must not be introduced silently.
District-country legal references
GDPR applies according to its territorial rules, not simply citizenship. Local laws may impose additional consent, sensitive-data, transfer, registration or representative requirements. This list is not an exhaustive legal opinion; applicability, amendments and regulator arrangements require local counsel review.
- Cyprus
GDPR (EU 2016/679) and Law 125(I)/2018
Legal reference ↗ - Jordan
Personal Data Protection Law No. 24 of 2023
Legal reference ↗ - Bahrain
Personal Data Protection Law No. 30 of 2018
Legal reference ↗ - UAE
Federal Decree-Law No. 45 of 2021; DIFC/ADGM regimes may apply separately
Legal reference ↗ - Lebanon
Law No. 81/2018 on Electronic Transactions and Personal Data; later changes require local review
Legal reference ↗ - Armenia
Law on Protection of Personal Data, adopted 18 May 2015
Legal reference ↗ - Georgia
Law on Personal Data Protection, adopted 14 June 2023; current amendments require local review
Legal reference ↗ - Palestine
Applicable privacy, communications and cybercrime protections require local legal confirmation; no comprehensive PDPL verified for this notice
- Sudan
Applicable privacy, communications and cybercrime protections require local legal confirmation; no comprehensive PDPL verified for this notice