Privacy notice

1. Introduction & scope

This notice explains how information is handled through the AI Hubs United beta: the public website, member accounts and profiles, following and activity, topic proposals and supports, posts and replies, message requests and direct messages, reports and moderation, events and registrations, News and editorial features, AI-assisted features and Contact enquiries.

It describes current service practices, not a guarantee of legal compliance. Read it alongside our Terms of use and Community guidelines.

2. Who is responsible

AI Hubs United is the service through which this community is operated. “AI Hubs United”, “we” and “the service” in this notice refer to that service and its operation, not a specified incorporated entity.

During the current beta, privacy and data-rights requests can be submitted through our Contact page. No registered operator address or designated data-protection officer is represented by this notice.

3. Data we collect

Account & authentication

Your email and account identifier, authentication/session information, confirmation and recovery state, and security metadata generated by authentication services. Credentials are handled by the authentication service, not displayed to other members.

Profile & community identity

The display name, headline, company, city, bio, expertise/interest tags and LinkedIn link you supply; your selected home hub; optional contact details and visibility/notification choices; profile photo; and account/onboarding status and activity timestamps. Optional email notification delivery is not currently switched on. We do not verify nationality through hub selection.

Social & community activity

Follow relationships, topic proposals and supports, posts, replies and reactions, and the visible community activity and counts presented on profiles. Topic categories, tags and optional intent labels are stored when supplied.

Messaging

Message requests and their status, direct message content, conversation participants and associated timestamps/metadata needed to provide messaging.

Safety & moderation

Reports and server-created evidence snapshots, flags and review information, personal block relationships, staff decisions, reasons and audit records.

Events

Registration records, selected ticket type, registration/cancellation status and attendance/check-in. The model supports payment references for future paid ticketing; paid checkout is not active.

Contact & support

The name, email, selected enquiry category and message submitted through Contact, plus information needed to route, resolve and protect the enquiry process.

Technical & security information

Session and authentication metadata, request/error diagnostics and network/device/browser information to the extent generated or retained by the application and its infrastructure providers. Providers may handle IP addresses and request logs for delivery and security; this is not a claim that the app keeps a separate comprehensive device or browsing-history database.

4. How we use data & legal bases

Data is used to operate the service, not sold as member personal data. Where the applicable law requires a legal basis, the relevant basis depends on the purpose and jurisdiction:

• Accounts and community features: providing the requested service, generally performance of a contract or steps before entering one.
• Security, fraud/spam prevention and moderation: legitimate interests in a safe, functioning professional network and, where applicable, legal obligations.
• Optional visibility and communications: member choices and consent where specifically requested; changing a setting changes the relevant future visibility.
• Event registration: delivering the requested registration and event service, including pre-contract steps where applicable.
• Support and privacy requests: providing assistance and fulfilling applicable legal obligations.
• Internal community insights: legitimate interests in understanding and improving real community participation, subject to the privacy limits described below.

These categories describe purposes and the bases that may apply; they do not establish that a single legal basis is valid for every user or jurisdiction. Where processing relies on consent, it may be withdrawn without affecting prior lawful processing.

5. Public & member-visible information

Published News and event information are public. Member profiles and community content are primarily available within the signed-in community, subject to access and privacy controls. “Public community activity” means visible shared community contributions, not private messages or unrestricted access to all account information.

Your professional profile, home hub, follower/following counts and visible topics/contributions may be shown to eligible members. Email and phone are private by default and shared with other members only when you enable their visibility. Bio, LinkedIn and message-request settings provide additional choices in Settings.

Posts, replies and topic participation may be visible across country hubs and the global community. A home-hub animal badge is a chosen professional/community affiliation, not nationality or citizenship verification.

6. Private messages

Direct messages are private to conversation participants under the service’s access controls. Staff do not generally browse conversations, and private message bodies are not routinely scanned or sent for AI moderation.

A participant may report specific message content. The reported evidence and necessary context can then be reviewed by authorised staff. That reporting boundary does not give staff general browsing access to unrelated private conversations.

Blocking prevents new message requests and messages between the pair. It does not erase historical messages. Under current database rules, deleting a sender’s account removes their authored message rows and linked participation records. Other records, reported evidence, copies held by others and backups may follow different storage or legal-retention rules; account deletion is not a guarantee of erasing every copy.

7. AI-assisted features

Staff can request AI-assisted assessment of selected flagged community content. First-contact request checks remain deterministic/baseline-only. AI assists review; people make enforcement decisions, and an AI flag alone does not cause an automatic ban. Unreported private DM bodies are not inputs to these reviews.

News supports source-grounded AI-assisted drafting for human editorial review. Automated News generation is currently disabled; drafts are not automatically published. Internal owner insights use community activity aggregates and may include named contributor activity within the internal view, not private messages/contact fields. Exports and on-demand AI summaries use a separate privacy-limited aggregate projection with small-cohort protection; named contributors do not enter those summary/export inputs.

The member AI Pulse is a community-information aggregate, and the weekly connection suggestion uses public professional/community information, with weekly selections and dismissals stored to keep suggestions stable. These features do not require sending private conversations to a model.

AI providers accessed through the platform’s AI gateway may process the limited inputs needed for requested AI-assisted features. Models may change. AI output can be incomplete or wrong and is not a substitute for human judgment.

8. Moderation, reports & blocks

Reports include evidence snapshots and context so staff can assess the reported content. Reporter identity is available to authorised staff and the reporter, not disclosed to the reported member. Flags, review reasoning and individual moderation scores are not public member-profile information.

Staff actions and reasons are recorded for accountability. Block relationships support personal boundaries and restrict pairwise follows, requests and messaging; they do not impose a platform-wide sanction. Staff roles and access controls limit moderation and administrative records.

See the Community guidelines for the reporting and human-review process. Appeals can be submitted through Contact.

9. Events & payments

Free-event registrations, ticket selections, cancellations and check-in can be stored within AI Hubs United. Event staff can access attendee/registration information needed for operations, including display name and community, and export operational lists. Other members do not receive the staff registrant list.

Paid ticketing and Stripe checkout are not active. If paid ticketing is enabled, Stripe will process card payments. AI Hubs United will receive payment status/reference information but will not store full card numbers. Payment and event-specific cancellation information will be presented when that flow is introduced.

10. News & editorial content

Published News is editorial information rather than member personal data in general. Articles may contain attributed information about people from public sources. Sources, publication references and editorial metadata support attribution and review.

Automation and review metadata, source candidates and unpublished drafts remain staff-only until applicable editorial material is reviewed and explicitly published. AI assistance does not automatically turn a draft into public content.

11. Service providers & recipients

Limited information is processed by service providers as needed to deliver the platform. Current categories include Lovable application/hosting infrastructure, Lovable Cloud database, authentication and storage services, and AI providers accessed through the platform AI gateway for the limited features described above. Stripe is a future payment provider only if paid ticketing is activated.

Information may also be disclosed to professional advisers or lawful authorities when reasonably needed for legal claims, service protection or a legal obligation. We do not sell member personal data. Using processors is not a promise that data is never shared; access and inputs are limited by the purpose and service controls.

This notice does not assert verified data-centre locations or particular provider contract terms.

12. International processing

Service providers may process information in countries outside your location. Where international-transfer rules apply, the relevant providers’ arrangements and applicable legal mechanisms or safeguards must be considered and relied on as appropriate.

Specific transfer mechanisms and hosting locations have not been verified in this notice. We do not claim that a particular contractual safeguard is configured or that all data remains in your country. Contact us with questions about international processing.

13. Retention & deletion

Retention depends on the purpose and the service’s current storage rules. We do not promise an exact deletion schedule that has not been implemented:

• Account and profile information is ordinarily kept while the account is active, subject to changes or deletion.
• Community content is retained until deleted or removed under available controls; related records and backups may remain where needed.
• Moderation evidence and audits may be retained where reasonably needed for safety, legal obligations and accountability.
• Contact enquiries are retained as necessary to resolve and document them.
• Event records are retained as necessary for event administration and applicable obligations.

Account deletion may remove linked records under current rules, but backup copies, records shared with others and necessary fraud/security/legal evidence can follow different retention requirements. Exact operational periods may be defined and updated as the service matures.

14. Security

The service uses authenticated access, database row-level access controls and role-restricted functions. Profile, event and News uploads use private storage and short-lived signed links where applicable. Images are resized/re-encoded to reduce embedded metadata. Staff decisions and privileged actions have audit controls.

These measures reduce risk but do not make any system perfectly secure. Protect your sign-in details and report suspected account misuse through Contact. Previously issued signed links may remain valid until expiry.

15. Cookies & browser storage

Browser storage is used for authentication/session continuity, temporary onboarding state and interface preferences; a sidebar preference cookie may be used where that interface is present. Infrastructure and authentication services may use necessary session or security mechanisms. The member application does not currently implement an advertising-cookie or marketing-tracker system.

Infrastructure diagnostics are distinct from advertising tracking. If additional analytics or non-essential cookies are introduced, this notice and consent choices will be updated where required. Clearing essential storage may sign you out or reset local service state.

16. Your choices & rights

Where applicable law provides them, rights may include access, correction, deletion, restriction, objection, portability, withdrawal of consent and a complaint to the competent supervisory authority. Rights, exceptions and required identity checks vary by law and jurisdiction.

You can edit your profile/privacy choices, download the available account-data export and request account deletion in Settings after signing in. An export is not represented as including every internal safety record or another member’s private information.

For other requests, use Contact and choose Privacy & data rights. We may need enough information to verify your identity and clarify the request. Please do not send passwords or unnecessary sensitive information.

17. Children & eligibility

AI Hubs United is intended for adult professional/community users. Our Terms require members to be at least 18. This is a service eligibility rule, not a claim that identity or age verification is implemented.

If you believe an under-18 account is using the service, contact the team so the circumstances can be reviewed.

18. Changes to this notice

This edition was last updated on 30 October 2026. We may revise it as the service and practices evolve, mark the new date and communicate material changes where appropriate. The date is a policy revision date, not a date that changes on each visit.

19. Privacy & data-rights contact

Submit privacy questions, data-rights requests and related legal enquiries through Contact. Use Privacy & data rights for privacy requests, or the relevant legal category for other enquiries.

For related standards and service terms, see the Community guidelines and Terms of use.