Privacy & GDPR

Control your profile visibility, AI data processing, data export, and account deletion.

JOGL Network gives you direct control over your data. Everything below is available in Settings.

Profile visibility (Settings → Account)

Public profile — a switch. When it's off, only members of your communities and your connections can see your profile.
Per-contact visibility — each contact/social item can be public, connections-only, limited to all or specific communities, or private (set on your profile).
Who can message you and who can send you connection requests — in Settings → Notifications → Messaging.

Archiving your profile (Settings → Account)

You can archive your profile, which hides it from search results. Your data is preserved, but the app offers no way to un-archive it yourself — the settings page lists archiving under Danger zone as irreversible, so ask support if you need it undone. Archiving is also the required first step before deleting your account.

AI data processing location (Settings → Data)

The AI Data Processing preference offers Global and Europe (EU). It applies to your own AI flows — global search, self-enrichment, and interviews on your profile. Your preference can only add EU processing, never remove it: where a community also requires EU, the stricter of the two wins. Which community counts depends on the flow — a self-enrichment run takes the one it runs in, a profile interview is attached to no community at all, and only a search across all your communities looks at every community you belong to. So belonging to one EU community does not put every flow on the EU lane. Embeddings are not affected.

Data residency, when active, covers where the language model runs. Embeddings and some external data sources (web research, LinkedIn data) are outside its scope; see your community's settings and your DPA for specifics.

Exporting your data (Settings → Data)

Export Your Data → Download Data produces a JSON file of your data (a GDPR Article 15/20 export), including your profile, settings, private notes, extracted facts, and preferences. The file is named jogl-data-export-<date>.json.

Deleting your account (Settings → Account)

Account deletion is a deliberate, two-step action:

Archive Profile first (this hides it from search).
Delete Account — this purges your private notes and their AI-structuring setting, removes your profile along with your community memberships and your booking data (your bookable slots, your event booking opt-ins, your meeting settings and any connected calendar), and signs you out.

This deletes your profile, not the account behind it. What it removes cannot be brought back, so export your data first if you want a copy — but it is not a full erasure, and what it leaves behind is more than your name and address. It removes what step 2 lists and the records that hang off your profile; your sign-in account is kept, and so is everything the deletion step does not itself remove:

Your sign-in identity and email address, and the contact details stored on the account (email addresses, phone numbers, social links).
Direct messages you sent and the conversations holding them — the person you wrote to still has their copy.
Your connections, and your notification, messaging and connection-request preferences — and the notifications themselves keep arriving. A device you allowed push on stays subscribed (signing out from the profile menu unsubscribes it; deleting your account does not), and email notifications still go to the address on the account. Both can carry a preview of a new message. Turn notifications off under Settings → Notifications before you delete if you do not want them.
Your conversations with the assistant — the chat and search history in the app.
Meetings you took part in at an event — the requests between you and another attendee, and the meetings that came of them. Deleting your account clears your bookable slots and settings, not your meeting history.

To have all of it removed, email support@jogl.io and ask for erasure.

Revoke your API keys and connected apps before you delete. Both hang off the sign-in account rather than your profile, and the deletion step revokes neither:

API keys minted under Settings → API/MCP belong to the billing account that owns them. A key you created keeps authenticating afterwards until it is revoked or reaches the expiry it was given.
Connected apps — the OAuth (MCP) connectors listed on the same page — keep their access too. An app you authorized goes on working after the deletion, and an authorization you gave but never used can still be turned into a working credential.

Revoke each one you no longer want honoured first, on the API keys page, where both have a Revoke action.

Cookies

Review and change your cookie preferences at any time from the profile menu (Learn more → Manage cookie preferences) or from the sign-in screen.