1. Who else is on the National Council?
Confirmed Council participants may be able to see other confirmed members through the official GRF account environment, member directory, Council workspace, group space, or approved Council materials, depending on the visibility rules for the relevant country pathway, Council body, group, forum, or platform area.
The authoritative source is always the official GRF system. Participants should not rely on informal lists, screenshots, forwarded spreadsheets, private chats, personal introductions, social media posts, or unofficial rosters. A person should be treated as confirmed only when their participation status has been properly recorded in the GRF system.
This protects leaders who may have political, public-sector, employer, diplomatic, professional, safety, or reputational sensitivities. It also prevents false claims that someone has joined, premature public association, unwanted outreach, sponsor targeting, media exposure, or misuse of another participant’s name.
A National Council may include leaders from different sectors, regions, institutions, communities, and professional backgrounds. However, not every confirmed participant will necessarily have the same visibility setting. Some leaders may be public. Some may be visible only to confirmed members. Some may be visible only within a specific group or Council space. Some may be restricted for safety, employer, public-sector, conflict, privacy, or country-risk reasons.
In simple terms, you may learn who else is on the Council through official GRF systems where visibility is permitted, but unofficial rosters, screenshots, and private name-sharing are not authoritative and should not be used.
2. Will I be able to see other confirmed members?
In most cases, confirmed participants may have some level of visibility into other confirmed members, but visibility is not automatic, universal, or identical for every participant.
Visibility may be structured in several layers:
Public visibility: the profile or certain fields may be visible to the public if the participant permits it and GRF allows it.
Community-member visibility: the profile or content may be visible to logged-in GRF community members.
Confirmed-participant visibility: certain profiles or materials may be visible only to confirmed Council members or pathway participants.
Friends or connection-based visibility: some account settings may allow a participant to make materials visible only to approved friends or connections.
Group or forum visibility: posts or profile elements may be visible within a specific group, forum, committee, Council space, or working area.
Administrator or Central Bureau visibility: required internal visibility may exist for verification, support, governance, safety, compliance, records, and account administration.
Restricted visibility: some participants may not be broadly visible because of safety, public-sector obligations, employer policy, political exposure, diplomatic sensitivity, conflict concerns, or personal privacy preferences.
The purpose is to support trusted collaboration without exposing people unnecessarily. Knowing who else is involved can help leaders understand the Council’s composition and seriousness, but visibility must be balanced with privacy, safety, attribution, and reputational protection.
In simple terms, yes, you may be able to see other confirmed members through official GRF channels, but visibility is controlled by role, account settings, pathway rules, safety posture, and platform context.
3. Are Council member profiles public?
Council member profiles are not public by default unless the participant’s settings, GRF’s platform rules, and the relevant participation context allow public visibility.
A participant may configure certain profile and content visibility settings through their GRF account, subject to platform capabilities and policies. GRF may also apply administrative or safety-based restrictions where needed.
A public profile must be carefully written. It should not imply that the participant represents GRF, GCRI, GRA, the Nexus Consortium, the Country Desk, the National Council, the country, their employer, a public institution, a government, or any organization unless that representation has been separately authorized and recorded.
A public profile may show approved title language, professional background, country pathway, areas of interest, and other public-safe information where permitted. It must avoid endorsement, certification, authority, procurement, finance, insurance, public mandate, government affiliation, or Nexus Universe placement claims.
Some leaders may have no public profile at all and may still be fully valid participants. Restricted visibility should not be interpreted as lower status. In many high-trust contexts, limited exposure is the responsible posture.
In simple terms, Council profiles may be public only where permitted by the participant’s settings, GRF’s platform rules, and claims-safety review. Public visibility is optional, bounded, and never a source of authority.
4. Can profiles be limited to confirmed members?
Yes. Profiles may be limited to confirmed members, community members, friends, approved connections, specific groups, or specific Council spaces, depending on the available account tools and GRF platform policies.
Member-only visibility allows confirmed participants to understand who is involved without making the roster available to unauthenticated visitors, media, sponsors, companies, political actors, public officials, or unrelated users.
A member-only profile should still be treated as controlled or context-limited information. Members should not copy, screenshot, export, republish, circulate, scrape, or use member-only profile data outside the official GRF platform. A member directory exists to support legitimate Council collaboration, not external networking extraction, media list building, sponsorship targeting, political outreach, commercial prospecting, or public disclosure.
In simple terms, yes, profiles can be limited to confirmed members or other permitted audiences, but limited-access information must stay within the context where it is provided.
5. Can I choose limited public visibility?
Yes. Leaders may choose limited public visibility through the privacy and visibility tools available in their GRF account, subject to GRF platform policies, role rules, and safety requirements.
Limited visibility may include showing only certain profile fields, making content visible only to community members, limiting posts to friends or approved connections, restricting materials to a group, hiding certain affiliations, or requesting removal from public listing.
Leaders may also contact the Central Bureau or designated GRF support channel to request changes to administrative visibility, directory listing, public exposure, profile display, participation markers, or safety-related visibility restrictions.
GRF may approve, adjust, or decline certain visibility requests where legal, operational, records, security, auditability, or governance needs require continued internal visibility. For example, GRF may still need to maintain internal records for verification, good standing, corrections, account administration, safety, and compliance.
In simple terms, yes, you can choose limited visibility through your account tools and may contact the Central Bureau for administrative visibility changes, while GRF preserves required internal records for governance and safety.
6. Can I hide sensitive affiliations?
Yes. Sensitive affiliations may be hidden, generalized, or excluded from public or member-facing profile areas where appropriate.
A participant may have affiliations that should not be publicly displayed, including public-sector roles, regulatory roles, diplomatic experience, political exposure, employer relationships, advisory roles, board roles, research collaborations, community relationships, security-sensitive work, or institutional connections that could be misread as endorsement or official representation.
A profile may use a general description such as public-sector professional, infrastructure specialist, academic researcher, finance professional, health systems expert, technology executive, civil society leader, or diaspora-linked participant without naming the specific employer or institution, where naming it could create risk or require permission.
However, hiding sensitive affiliations publicly does not remove the duty to disclose conflicts confidentially to GRF where relevant. A participant may keep an affiliation out of public view while still disclosing it through the official conflict-of-interest or governance process.
In simple terms, yes, sensitive affiliations can be hidden or generalized in public-facing areas, but relevant conflicts must still be disclosed confidentially through the official process.
7. What information appears in a Council profile?
A Council profile may include only information that is accurate, appropriate, permissioned, and consistent with the participant’s visibility settings and GRF’s platform rules.
Depending on the profile configuration, it may include:
- name;
- approved Council title;
- country pathway;
- individual-capacity statement;
- region, city, or diaspora connection where appropriate;
- broad professional background;
- sector expertise;
- contribution areas;
- areas of interest;
- committee, working-group, chair, or board-pathway roles if officially confirmed;
- public-safe biography;
- language capabilities where relevant;
- approved profile photo if consented;
- approved links or professional references where allowed;
- selected posts, updates, materials, or activity depending on the participant’s visibility settings.
A Council profile should not include private contact information, sensitive documents, unauthorized logos, unapproved employer claims, political claims, sponsor claims, project endorsement, technology certification, procurement status, investment-readiness claims, insurance claims, government representation, diplomatic status, or statements implying authority beyond the approved role.
The profile should help others understand how the participant may contribute without turning the profile into a marketing page, campaign tool, sponsor target, or status claim.
In simple terms, a Council profile should show who you are, where you fit, and how you may contribute, without creating unauthorized claims, exposure, or institutional confusion.
8. Can my profile show my title and employer?
Yes. A profile may show your professional title and employer if the information is accurate, allowed by your employer, consistent with your account visibility settings, and not misleading.
However, listing your employer does not mean your employer is participating in GRF, endorsing the Council, sponsoring the pathway, authorizing your role, joining the Nexus Consortium, or permitting you to represent it. Unless your organization has separately joined or authorized a public statement, your employer should be listed only as professional background.
A safe profile statement is:
Professional title and employer listed for identification only. Participation is in an individual capacity unless separately stated and recorded.
You should not use your employer’s logo unless both the employer and GRF have authorized that use. You should also check employer policies before listing your role in a way that may imply institutional association.
In simple terms, yes, your title and employer may appear, but only as background. It must not imply organizational participation, endorsement, sponsorship, or representation.
9. Can my profile show that I participate in an individual capacity?
Yes. For most Council participants, the profile should clearly state that participation is in an individual capacity.
This is essential because many leaders hold senior roles in companies, universities, public institutions, civil society bodies, financial institutions, technology providers, public agencies, or politically sensitive environments. Without individual-capacity language, readers may wrongly assume the participant’s organization, employer, ministry, public agency, government, community, or institution has joined or endorsed the pathway.
A safe statement is:
Participating in an individual capacity as Member, National Council Leadership of [Country], The Global Risks Forum (GRF). Organizational affiliations, where listed, are for professional identification only and do not imply institutional participation, endorsement, sponsorship, or authorization.
In simple terms, yes, your profile should be able to show that you participate as an individual, not as an organizational representative unless separately authorized.
10. Can my profile include my country of citizenship or nationality?
Yes, where appropriate and consented, a profile may include the participant’s country pathway connected to citizenship or nationality.
The National Council Leadership pathway is country-linked, and citizenship or nationality may support eligibility. However, showing a country pathway does not mean the participant represents the country, government, public authorities, embassy, ministry, regulator, municipality, public agency, or citizens as a whole.
A profile should avoid language such as representative of [Country], delegate of [Country], official national envoy, diplomatic representative, or government representative unless the participant has separate lawful authority from the competent public institution and GRF has recorded the correct status.
A safe form is:
Member, National Council Leadership of [Country], The Global Risks Forum (GRF). Participating in an individual capacity.
In simple terms, yes, your profile may show your country pathway, but citizenship or nationality does not create sovereign authority, public mandate, diplomatic status, or government representation.
11. Can my profile include diaspora or regional connection?
Yes. A profile may include diaspora, regional, city, local, or professional-community connection where relevant and safe.
Diaspora leaders can be important to national resilience pathways because they may connect global expertise, finance, research, technology, policy, institutional relationships, and professional networks back to the country pathway. Regional and local connections may also help the Council understand where a participant’s knowledge, lived experience, or networks are grounded.
However, these connections must be described accurately. A diaspora connection does not mean the participant represents diaspora communities. A city connection does not mean the participant represents the city. A regional connection does not mean the participant speaks for that region.
A safe phrasing is:
Diaspora-linked participant with professional interest in [country/region/sector], participating in an individual capacity.
In simple terms, yes, diaspora and regional connections may appear where useful, but they must not imply representation of a community, city, region, or country.
12. Can my profile include sector expertise?
Yes. A profile may include sector expertise where it is accurate, relevant, and not overstated.
Sector expertise may include water, energy, food systems, health, critical infrastructure, cities, AI, cybersecurity, finance, insurance, capital markets, development finance, biodiversity, education, logistics, policy, governance, diplomacy, foresight, community resilience, research, media, technology, or other fields relevant to the Council’s work.
However, sector expertise is not GRF certification. A profile should not say or imply that GRF certifies the participant as an expert, validates their qualifications, endorses their services, approves their employer, or gives them authority in that sector.
The profile may describe expertise based on actual professional background, but the participant should be able to support the description if asked.
In simple terms, yes, your profile may include sector expertise, but it must be accurate and must not imply GRF accreditation, endorsement, or certification.
13. Can my profile include my areas of interest?
Yes. A profile may include areas of interest where the participant chooses to display them and GRF’s platform allows that field to be visible to the selected audience.
Areas of interest help other members, Chairs, Leads, committees, working groups, Country Desk functions, and platform administrators understand where the participant may wish to contribute. They can also help route the participant into relevant forms, groups, forums, dockets, committees, and workstreams.
Areas of interest should be distinguished from expertise. A participant may be interested in AI safety, water resilience, sovereign risk, or public health without being presented as a certified technical expert in those fields.
A profile can use categories such as Primary Expertise, Contribution Areas, and Areas of Interest to avoid confusion.
In simple terms, yes, your areas of interest may appear, but they should not be confused with certification, formal expertise, or authority.
14. Can I update my profile?
Yes. Participants may update their online profile through the privacy, profile, account, and posting tools available under their GRF account, subject to platform policies and approval requirements where applicable.
Updates may be needed when a title changes, employer changes, biography changes, visibility preference changes, areas of interest evolve, committee status changes, a chair role begins or ends, a profile contains an error, a conflict arises, or a safety concern requires reduced exposure.
Some updates may be fully member-controlled. Others may require GRF review, especially where they involve approved titles, Council roles, institutional references, public claims, logos, visibility markers, or role status.
Participants may also contact the Central Bureau or GRF support channel to request administrative changes that are not available through self-service account tools.
In simple terms, yes, you can update your profile through your account tools, and you may contact the Central Bureau for administrative visibility or profile issues requiring GRF support.
15. Can I request removal from public listing?
Yes. A participant may request removal from public listing or reduction in public visibility.
Removal may be appropriate for safety, employer policy, public-sector constraints, political sensitivity, family privacy, media exposure, country risk, conflict-of-interest concerns, professional obligations, or personal preference. GRF may also remove or restrict a public listing if continued visibility could create risk to the participant, the Council, or any institution.
Removal from public listing does not necessarily remove the participant from the Council. The participant may remain visible internally, visible to administrators, visible to confirmed members only, visible only in specific groups, or recorded in controlled systems.
If the participant withdraws entirely, GRF may still maintain historical records where needed for auditability, compliance, correction, good-standing history, and institutional memory.
In simple terms, yes, you can request removal from public listing without necessarily ending your participation.
16. Can other members contact me directly?
Other members may contact you only through approved mechanisms and within the boundaries of GRF’s communication, privacy, and conduct rules.
If the GRF platform provides member-to-member communication tools, connection tools, group tools, or private messaging, those tools should be used according to platform policies and visibility settings. Participants may be able to restrict contact to community members, friends, approved connections, group participants, or other configured audiences.
Direct contact should remain professional, relevant, non-commercial, non-political, non-harassing, and aligned with Council work. Members should not use the directory or profile system to solicit business, seek investment, promote products, recruit for political activity, pressure for sponsorship, request government access, circulate unofficial meetings, or move Council work into side channels.
In simple terms, member contact should be professional, permissioned, and consistent with account settings. The Council environment is not a sales, lobbying, extraction, or pressure network.
17. Are member-to-member interactions routed through the GRF account environment?
Council-related member-to-member interactions should remain inside the GRF account environment or approved GRF communication lanes wherever possible.
This does not mean members can never know each other professionally outside GRF. Many leaders may already have relationships. However, once a conversation concerns Council work, dockets, proposals, stakeholder leads, government access, sponsors, projects, technologies, finance, insurance, procurement, profile visibility, claims, controlled materials, or institutional engagement, it should be brought back into the official GRF system.
Account-based routing protects both members. It creates a record, reduces misunderstanding, protects privacy, and prevents informal side channels from becoming the real operating system.
In simple terms, personal relationships may exist outside GRF, but Council business belongs inside the official GRF environment.
18. Are private messages allowed?
Private messages may be allowed if GRF’s platform provides or permits them, but they must be used within platform policies, participant privacy settings, and Council conduct rules.
Private messaging should not become an unofficial Council record system. It should not be used for formal proposals, approvals, controlled materials, stakeholder leads, sponsor discussions, procurement-related matters, finance or insurance issues, investment discussions, public claims, complaints, governance decisions, or sensitive Council matters.
If a private message raises a Council matter, the recipient should route it to the proper form, docket, group, committee, support channel, or official pathway.
Private messages must also follow conduct rules. Harassment, pressure, commercial solicitation, political campaigning, unwanted outreach, intimidation, repeated unwanted contact, or requests to move controlled Council work outside official channels should be reported.
In simple terms, private messages may be available for limited professional contact, but they cannot replace official Council forms, dockets, records, or protected channels.
19. How does GRF protect members from unwanted outreach?
GRF protects members from unwanted outreach through visibility settings, member-controlled privacy tools, Central Bureau support, member-only access, contact controls, consent-based communication, platform policies, conduct rules, and enforcement.
Participants should not be exposed to uncontrolled sponsor approaches, vendor pitches, media inquiries, political messages, investor solicitations, procurement requests, or repeated direct contact from other members. A Council profile should not become a target list.
GRF may limit profile fields, hide contact information, restrict directory access, adjust visibility, require routing through official pathways, block abusive users, suspend messaging privileges, or act against members who misuse access.
Participants also have tools. They may configure profile visibility, post visibility, connection settings, group visibility, and account privacy settings where available. They may also contact the Central Bureau or GRF support for visibility or misuse concerns.
In simple terms, GRF protects members through platform controls, account settings, Central Bureau support, and enforcement against misuse.
20. How does GRF protect against scraping, spam, phishing, or profile misuse?
GRF protects against scraping, spam, phishing, and profile misuse through controlled directory access, privacy settings, limited public exposure, platform rules, restricted downloadable data, monitoring where available, and enforcement against unauthorized copying or republishing of profile information.
Member profiles should not expose unnecessary personal contact details. Public pages should avoid sensitive information. Member-only directories should not be exported, copied, screenshotted, scraped, or used to build external lists.
Participants should be cautious about messages requesting money, credentials, documents, confidential materials, government introductions, sponsorship access, investment discussions, insurance matters, procurement access, or off-platform communication. Suspicious messages should be reported.
If a profile is misused, GRF may require takedown, issue correction, restrict access, suspend accounts, change visibility settings, or escalate the matter.
In simple terms, GRF protects profiles by reducing unnecessary exposure, controlling access, and treating scraping, spam, phishing, and misuse as serious integrity issues.
21. Can I publish the names of other Council members?
No. You should not publish the names of other Council members unless those names are already public through an official GRF-approved source and your specific use is accurate, safe, permissioned, and consistent with GRF rules.
Even if you can see another member inside a member-only directory, group, Council workspace, or community area, that does not mean you may republish their name. Internal visibility is not public consent.
You should not announce, tag, list, quote, photograph, or associate another participant publicly without permission. Their participation may be member-only, restricted, sensitive, or not intended for public attribution.
Publishing names can create political, reputational, employer, media, safety, or institutional risk. It can also imply that those members support your statement, project, event, organization, political view, sponsor approach, or public position.
In simple terms, do not publish other members’ names unless GRF has made them public or specific permission has been granted for that use.
22. Can I publicly state that I serve alongside other leaders?
Yes, but only in general, approved, non-identifying language unless GRF has approved specific names or public references.
A safe statement is:
I participate in an individual capacity as a Member, National Council Leadership of [Country], The Global Risks Forum (GRF), alongside other confirmed leaders contributing to the country pathway.
This kind of statement communicates participation without exposing others or implying that they endorse your views.
You should not say “I serve with [names]” unless those individuals are publicly listed by GRF or have given permission and the statement is accurate and approved. You should also avoid exaggerating the status of the group, such as claiming government representation, diplomatic standing, official national mandate, Board authority, project approval, or institutional endorsement.
In simple terms, you may say you serve alongside other leaders in general terms, but do not name or imply support from specific members without permission.
23. Can media, sponsors, officials, or companies request access to Council members?
Media, sponsors, officials, companies, universities, investors, insurers, public institutions, civil society bodies, and other third parties may request access, but they should not receive direct member access by default.
Requests should be routed through the official GRF pathway. GRF may determine whether the request is appropriate, whether the member consents, whether the purpose is public-safe, whether conflicts exist, whether the request creates pressure or undue influence, and whether a controlled briefing, institutional pathway, media pathway, sponsor pathway, or public-safe response is more appropriate.
Sponsors should not receive privileged access to members as a benefit. Companies should not use the Council to prospect. Media should not bypass GRF communications rules. Officials should not treat individual members as official representatives unless that role has been separately authorized.
In simple terms, third-party access to Council members must be routed, consented, and controlled. It is not automatic and cannot be sold, implied, or pressured.
24. What happens if someone misuses my name, title, or profile?
If someone misuses your name, title, profile, image, post, affiliation, or participation status, you should report it through the official GRF support, claims, correction, or protected reporting channel.
Misuse may include claiming that you endorsed a project, listing you as a speaker without consent, naming you as a representative, using your profile in sponsor materials, implying your employer is involved, suggesting you support a political position, quoting you without permission, copying your profile to another website, scraping your data, using your post outside its visibility setting, or using your name to attract investors, sponsors, officials, media, or institutions.
GRF may review the matter, request takedown, issue correction, restrict the offending participant’s privileges, suspend access, update your profile visibility, assist with administrative changes, or take further action. If the misuse creates public reliance, a public-safe clarification may be required.
You should preserve evidence, including screenshots, links, messages, dates, names of people involved, and where the misuse appeared.
In simple terms, report misuse immediately, preserve evidence, and let GRF handle correction, takedown, access restriction, visibility changes, or escalation through the official process.
25. Can GRF restrict visibility for safety reasons?
Yes. GRF may restrict profile visibility, member-directory access, contact functions, public listing, meeting participant lists, group visibility, attribution, photographs, posts, comments, or public references for safety, privacy, integrity, or institutional reasons.
Safety reasons may include political sensitivity, public-sector obligations, employer restrictions, harassment risk, media exposure, country instability, community protection, retaliation risk, family privacy, regulatory sensitivity, diplomatic sensitivity, conflict-of-interest concerns, or threats of misuse.
GRF may also restrict visibility for entire country pathways, specific meetings, controlled sessions, committees, working groups, Board matters, protected concerns, sensitive dockets, or high-risk jurisdictions.
Restricted visibility should not be seen as lower status. In high-trust environments, protection is often a sign of seriousness. Some of the most important contributors may require the least public exposure.
In simple terms, yes, GRF can restrict visibility whenever safety, privacy, institutional sensitivity, participant protection, or platform integrity requires it.
26. What is the difference between administrative visibility and profile visibility?
Administrative visibility refers to what GRF, the Central Bureau, and authorized administrators can see for verification, support, governance, account administration, compliance, good standing, security, records, and safety.
Profile visibility refers to what other users, members, groups, friends, confirmed participants, or the public can see on your profile or activity feed.
These are different layers. A participant may hide certain profile information from the public while GRF administrators still maintain required internal records. Administrative visibility is necessary for governance, auditability, security, correction, identity verification, and participant support. Profile visibility is the participant-facing and community-facing display layer.
Leaders may contact the Central Bureau to request changes to administrative display, public listing, directory exposure, or visibility settings that are not self-service. However, GRF may preserve required internal records even when public visibility is reduced.
In simple terms, administrative visibility is what GRF needs to govern and support the pathway; profile visibility is what other users or the public may see.
27. Can I change administrative visibility by contacting the Central Bureau?
Yes. Leaders may contact the Central Bureau or designated GRF support channel to request changes to administrative visibility, public listing, directory display, participation markers, profile exposure, or safety-related visibility controls.
GRF may review the request based on privacy, safety, public-sector obligations, employer constraints, political sensitivity, platform rules, audit requirements, and governance needs. Some changes may be made quickly. Others may require review because they affect records, role status, good standing, profile claims, or public-facing attribution.
Administrative visibility cannot always be eliminated because GRF must retain certain records for verification, security, compliance, correction, and institutional memory. However, GRF can often adjust what is shown publicly, what appears in directories, what fields are visible, and what exposure level applies.
In simple terms, yes, you can contact the Central Bureau to request visibility changes, but required internal records may remain in place for governance and security reasons.
28. Can I configure who sees my online profile, posts, updates, and materials?
Yes. Leaders may use the privacy and visibility tools available under their GRF account to configure who can see their profile, posts, updates, materials, activity, or selected content, subject to platform policies and the rules of the group, forum, or area where they are posting.
Depending on available settings, content may be visible to:
- the public;
- all GRF community members;
- confirmed Council or pathway participants;
- friends or approved connections;
- a specific group;
- a specific forum;
- a specific committee or working area;
- administrators only, where supported;
- no public audience, where profile hiding or limited visibility is available.
Participants should review visibility settings before posting. A post made in a public forum or public group may be public by nature even if other parts of the participant’s account are limited. A post made in a members-only group may remain limited to that group, subject to platform rules and handling obligations.
In simple terms, yes, you can configure visibility for your account and materials where the platform provides those tools, but the visibility of each post also depends on where you publish it.
29. Are posts in public forums or public groups automatically public?
Yes. Posts made in public forums, public groups, public comment areas, or public-facing platform spaces should be treated as public by nature.
A participant should not post controlled Council information, private member details, confidential materials, stakeholder leads, government-facing signals, sponsor information, screenshots, meeting notes, raw submissions, controlled annexes, or sensitive community information in public areas.
Public forums are appropriate for public-safe dialogue, general discussion, public education, community engagement, and approved public-facing content. They are not appropriate for Council dockets, internal strategy, controlled materials, nomination discussions, claims disputes, conduct concerns, procurement-sensitive issues, finance or insurance matters, or unapproved institutional references.
If a participant accidentally posts sensitive information in a public area, they should remove it where possible and report the issue through the official GRF channel.
In simple terms, yes, public forums and public groups are public spaces. Post only what is public-safe.
30. Do I own and control my personal data and account privacy tools?
Leaders should have meaningful control over their account profile, privacy settings, public visibility, posts, updates, and materials through the tools provided by the GRF platform, subject to GRF policies, legal requirements, governance records, and platform functionality.
This means a participant may be able to edit profile details, choose visibility settings, manage audience settings, restrict posts, update materials, change connection settings, request profile removal, or contact the Central Bureau for administrative visibility changes.
At the same time, some GRF records must be preserved for institutional purposes. These may include verification records, participation status, undertakings, submissions, dockets, decisions, corrections, incident records, good-standing history, and compliance records. These records are not the same as public profile content. They support the integrity of the system.
In simple terms, you control your profile and privacy settings where the platform provides those tools, while GRF retains required governance records for verification, safety, auditability, correction, and compliance.
31. Can I decide who sees my posts and updates?
Yes, where the GRF platform provides audience controls, you may choose the intended visibility of your posts and updates, subject to the rules of the space where you post.
For example, you may be able to post to the public, GRF community members, friends, approved connections, a specific group, a forum, or another permitted audience. However, the audience setting must be understood together with the posting context.
A post made inside a public forum may be public. A post made inside a private group may be limited to that group. A post made to friends may be visible only to approved connections if the platform supports that control. A post made inside a Council workspace may still be subject to Council handling rules and should not be copied elsewhere.
No account setting gives permission to disclose controlled Council materials. Privacy controls manage audience visibility; they do not override GRF handling, confidentiality, claims, or attribution rules.
In simple terms, you may choose your post audience where tools allow, but you must still respect the rules of the space and never disclose controlled Council information improperly.
32. Can I post Council materials to my profile or group?
Only if the material is public-safe or specifically authorized for that space.
Participants should not post raw Council submissions, meeting notes, controlled annexes, member lists, stakeholder leads, protected concerns, nomination materials, internal dockets, sponsor leads, government-facing notes, technical vulnerability details, finance-readiness materials, or confidential information to personal profiles or groups.
Approved public-safe materials may be shared according to their allowed distribution rules. If a material is marked controlled, restricted, no-forward, internal, draft, or not public-safe, it should not be posted.
Group context also matters. A members-only group is not automatically safe for controlled Council material unless that group is approved for that material. A public group is never appropriate for controlled material.
In simple terms, post only public-safe or authorized materials. Do not move controlled Council work into profiles, forums, or groups without permission.
33. Can I change who sees my previous posts or materials?
Yes, where platform tools allow, a participant may change the visibility of previous posts, updates, or materials. This may include moving content from public to community-only, friends-only, group-only, or hidden status.
However, changing visibility does not erase the fact that content may already have been seen, copied, screenshotted, indexed, quoted, or shared by others. If the prior post contained sensitive or controlled information, the participant should report the issue to GRF so containment, correction, or takedown steps can be considered.
If the post involved Council status, public claims, institutional names, logos, other members, or sensitive material, a visibility change may not be enough. A correction or clarification may be required.
In simple terms, you may be able to change visibility for prior posts, but if sensitive information was exposed, notify GRF and follow the correction process.
34. What responsibilities come with member-controlled visibility settings?
Member-controlled visibility settings give leaders flexibility, but they also create responsibility.
Participants should understand the audience before posting, avoid sharing controlled Council information, protect other members’ identities, avoid unauthorized institutional references, respect group rules, use accurate titles, avoid endorsement claims, and correct mistakes promptly.
A participant should not assume that limited visibility means no risk. Members-only posts can still be misread, copied, or shared. Group posts may still be subject to GRF handling rules. Public posts can be indexed, quoted, and seen outside the intended audience.
Participants should also keep their profiles and materials accurate. If a role ends, visibility changes, a title changes, or a claim becomes outdated, the participant should update the profile or request correction.
In simple terms, visibility tools give you control, but they also require judgment, accuracy, and respect for Council handling rules.
35. What is the safest default for leaders who are unsure about visibility?
The safest default is to keep sensitive information limited, use individual-capacity language, avoid naming others, avoid institutional claims, post only public-safe materials, and ask GRF or the Central Bureau before publishing anything that may create confusion.
A safe public profile can be simple:
Member, National Council Leadership of [Country], The Global Risks Forum (GRF). Participating in an individual capacity. Areas of interest: [selected public-safe areas]. Organizational affiliations, if listed, are for professional identification only and do not imply endorsement or representation.
A safe posting rule is:
If the content mentions Council work, other members, public institutions, sponsors, projects, technologies, finance, insurance, procurement, government access, Nexus Universe, or internal submissions, treat it as controlled until GRF confirms it is public-safe.
In simple terms, when unsure, limit visibility, use approved language, avoid naming others, and ask before posting.
