{"id":111,"date":"2026-10-17T15:46:33","date_gmt":"2026-10-17T15:46:33","guid":{"rendered":"https:\/\/forum.instituteofinnertechnology.com\/?page_id=111"},"modified":"2026-10-17T15:46:33","modified_gmt":"2026-10-17T15:46:33","slug":"forum-meetings-privacy","status":"publish","type":"page","link":"https:\/\/forum.instituteofinnertechnology.com\/sv\/forum-meetings-privacy\/","title":{"rendered":"Institute Forum Meetings \u2014 Privacy Notice"},"content":{"rendered":"
\n\n

Last updated: 17 October 2026.<\/strong> This notice describes the Google account connection and meeting functions of Institute Forum Meetings.<\/p>\n\n\n\n

Who operates this integration<\/h2>\n\n\n\n

Institute Forum Meetings is operated by Swedish Institute of Inner Technology AB for its invitation-only community at forum.instituteofinnertechnology.com. For questions about this integration, a copy of your meeting-related information, or a deletion request, contact hello@sensualinstitute.com<\/a> and identify the forum account concerned. This notice concerns the Google meeting integration; it is not a complete notice for all other forum features.<\/p>\n\n\n\n

Your choice to connect Google<\/h2>\n\n\n\n

Google access is optional and starts when an authorized space organizer chooses Connect my Google account<\/strong>. You choose an account and review the permissions on Google’s authorization page. We do not receive your Google password. A separate connection is stored for each organizer’s forum account. No shared Google authorization is substituted when your connection is absent or cannot be used.<\/p>\n\n\n\n

Connecting Google does not join the forum, grant a space role, or disclose private forum content to the public. Owners, moderators and site administrators can schedule; joining a meeting does not require giving this integration Calendar permission.<\/p>\n\n\n\n

Information received from Google<\/h2>\n\n\n\n

Account identity:<\/strong> Google’s account identifier, email address and email-verification result identify the connected account. The verified email is displayed to you so you can confirm which account will host a meeting.<\/p>\n\n\n\n

Authorization information:<\/strong> access and refresh tokens, expiry information and granted permissions allow the server to carry out meeting operations without asking you to sign in again each time. These are authorization credentials, not your Google password.<\/p>\n\n\n\n

Calendar event responses:<\/strong> the integration receives Google’s event response when creating or checking a forum meeting. It uses the event identifier, creation status and conference information to obtain the Google Meet joining link. The installed meeting code does not list or search unrelated events, read Gmail, retrieve contacts, access Drive files, or retrieve meeting recordings or transcripts.<\/p>\n\n\n\n

Permissions and their purpose<\/h2>\n\n\n\n

The current integration requests openid<\/code> and email identity permission to identify your Google account, and https:\/\/www.googleapis.com\/auth\/calendar.events<\/code> to create an event in your primary Google Calendar and retrieve that event’s Meet link.<\/p>\n\n\n\n

The Calendar permission is broader than the operations this integration performs.<\/strong> It can authorize access to events beyond the meetings created here; the current meeting code uses it only to create and retrieve the forum meeting events it handles. It is not a permission restricted to one newly created event. The permission requested on Google’s authorization screen is the permission used by the currently installed integration.<\/p>\n\n\n\n

Information sent to Google and shown in your space<\/h2>\n\n\n\n

When you schedule, Google receives the meeting title, start and end times, an event identifier, a request for a Meet conference, and a description identifying the relevant forum space and the Institute forum. Avoid putting confidential information into a meeting title or space name unless you intend it to appear in the calendar event. The event is requested with private visibility, but your Google account’s own access and administration rules still apply.<\/p>\n\n\n\n

The forum stores the title, space reference, organizer’s forum identifier, connected Google identifier and email, event identifier, time zone, start and end times, joining link, processing status and notification records. The meeting title, time and joining link are displayed to active space members and site administrators. Your connected email is displayed in your own scheduling controls; it is not added to the meeting list by this integration.<\/p>\n\n\n\n

When you select Email current space members<\/strong>, the forum sends the meeting title, time, space address and joining link to the email addresses of current active space members through its configured email service. This does not use your Gmail mailbox, request Gmail access, or upload a Google Calendar guest list. The optional email checkbox is not selected by default. A recipient can retain or forward a message, and Google applies its own admission rules to Meet links.<\/p>\n\n\n\n

Storage and access<\/h2>\n\n\n\n

Google authorization credentials are encrypted before the integration stores them in the WordPress database. The encryption is bound to the individual forum account and Google application. Google API requests use HTTPS. Meeting records and the organizer’s account identifiers are stored separately as WordPress data; they are not all encrypted by the integration’s token-encryption mechanism.<\/p>\n\n\n\n

The forum’s hosting and database systems process the information needed to operate this feature. The configured email service processes optional meeting notifications. Copies of forum data may also be included in site backups and technical logs. Authorized technical administrators may have access to those systems for support and security. Contact the operator for current service-provider, hosting-location and backup information. This notice does not claim that data stays exclusively in Sweden or the European Union. Google processes the information sent to its services under its own applicable terms and privacy information.<\/p>\n\n\n\n

Use restrictions and human access<\/h2>\n\n\n\n

Google-derived information is used for the meeting functions described here and the security and support necessary to operate them. It is not sold, used for advertising or credit decisions, or supplied to train general-purpose artificial-intelligence models. Access by people is limited to meeting information you choose to share, specific support access you authorize, and necessary security or legal handling. These restrictions apply to the operation of this integration, including support access and processing by service providers.<\/p>\n\n\n\n

Institute Forum Meetings’ use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy<\/a>, including its Limited Use requirements. This is our policy for this integration’s use of Google data. It is not a claim that Google has verified or endorsed the application.<\/p>\n\n\n\n

Disconnecting, retention and deletion<\/h2>\n\n\n\n

Choose Disconnect my account<\/strong> in the Meetings section to remove the integration’s live saved authorization credentials for your forum account. A non-secret disconnected marker is retained. Other organizers’ connections are unaffected. A request already sent to Google may complete even if you disconnect while it is in progress.<\/p>\n\n\n\n

Disconnecting here does not itself revoke the app’s permission in your Google Account. You can also remove Institute Forum Meetings through your Google Account’s third-party connections<\/a>. The integration will then need a fresh usable authorization for future Google operations.<\/p>\n\n\n\n

Disconnecting does not automatically delete the forum’s stored meeting records, cancel the corresponding Google Calendar events, or remove messages already sent to members. The current integration does not automatically erase meeting records when their scheduled end time passes. Ask the operator to delete forum-side meeting information; delete or manage the corresponding event separately in Google Calendar. Data held by Google or by email recipients follows their own retention arrangements.<\/p>\n\n\n\n

The integration’s current retention behavior is as follows: saved authorization credentials remain until disconnected or replaced; meeting records remain as part of the space’s meeting history until manually removed. There is no automatic age-based deletion of meeting records in the current version. To request access, correction or deletion, email the contact address above with your forum account and the meeting concerned, without passwords or authorization tokens. We verify the requester’s authority before acting. Copies in technical logs or backups can remain after a live record is removed; this integration does not control their rotation and does not promise immediate erasure from all backups. We will explain any information that must be retained when responding to a deletion request.<\/p>\n\n\n\n

Questions and changes<\/h2>\n\n\n\n

You can ask the operator about the information held by this integration, corrections, deletion, and any applicable data-protection rights. Choosing not to connect Google does not remove your forum membership. Removing the connection stops future use of the stored authorization; it does not undo an operation already completed. This integration-specific notice does not limit your rights under applicable data-protection law. Material changes to Google-data use require updated disclosures and, where needed, renewed permission before the new use begins.<\/p>\n\n\n\n

About Institute Forum Meetings<\/a> \u00b7 Meeting service terms<\/a> \u00b7 Contact the operator<\/a><\/p>\n\n<\/div>","protected":false},"excerpt":{"rendered":"

How the Institute Forum Meetings integration uses your Google identity, Calendar authorization and meeting information.<\/p>","protected":false},"author":6,"featured_media":0,"parent":0,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"footnotes":""},"class_list":["post-111","page","type-page","status-publish","hentry"],"_links":{"self":[{"href":"https:\/\/forum.instituteofinnertechnology.com\/sv\/wp-json\/wp\/v2\/pages\/111","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/forum.instituteofinnertechnology.com\/sv\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/forum.instituteofinnertechnology.com\/sv\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/forum.instituteofinnertechnology.com\/sv\/wp-json\/wp\/v2\/users\/6"}],"replies":[{"embeddable":true,"href":"https:\/\/forum.instituteofinnertechnology.com\/sv\/wp-json\/wp\/v2\/comments?post=111"}],"version-history":[{"count":7,"href":"https:\/\/forum.instituteofinnertechnology.com\/sv\/wp-json\/wp\/v2\/pages\/111\/revisions"}],"predecessor-version":[{"id":119,"href":"https:\/\/forum.instituteofinnertechnology.com\/sv\/wp-json\/wp\/v2\/pages\/111\/revisions\/119"}],"wp:attachment":[{"href":"https:\/\/forum.instituteofinnertechnology.com\/sv\/wp-json\/wp\/v2\/media?parent=111"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}