Privacy policy

How Meditrust Social handles your data to manage Google reviews and prepare or send posts to Google, Facebook, Instagram and YouTube, depending on the services you connect.

YouTube data: connecting a channel and uploading videos and Shorts

Connecting. Meditrust Social uses YouTube API Services (YouTube Data API v3) when you authorize the connection at Google. The youtube.readonly scope reads the ID and name of the channel you select and checks that the connection still points to that channel. For videos sent from Meditrust Social, it reads the video ID, processing status, visibility and scheduled release time, when present, for your history. Meditrust does not collect your Google password.

Keeping accounts separate. When the app requests openid, Meditrust verifies a signed Google identifier to bind the authorization to one Social account. We retain a one-way fingerprint with the connection and delete it when the connection is erased. The identity token is used only for that check. We do not request your Google email address or profile for this operation.

Uploading. You provide the MP4 file, title, description, category and video settings, including visibility and content declarations. A release time may be recorded if scheduling is available and you choose it. Meditrust checks the file format, duration and resolution. The youtube.upload scope sends the file and settings to YouTube for the selected channel after you confirm them in Meditrust Social.

Storage and access. Meditrust associates the channel and its access and refresh tokens with your Social account. The tokens and the upload resumption reference are encrypted in private storage. MP4 files are stored privately for verification and transfer. Cleanup removes them after transfer or expiration. Your history stores the approved settings, upload references and status information needed for follow-up. YouTube data we use is refreshed or deleted before 30 days.

Recipients and use. YouTube receives the content and settings of the upload you confirmed. Authorized staff and technical providers participate as described below. An AI assistant you authorize can prepare a draft or read its status within its permissions. It does not receive your MP4 files or YouTube tokens. Meditrust uses this data only for the functions you authorize and complies with the Limited Use requirements of the Google API Services User Data Policy.

Revocation and deletion. Disconnect the channel in Connections to stop future uploads from Meditrust and immediately request that Google revoke authorization. You can also revoke access through your Google Account security settings. We delete the related data as soon as possible, within seven days for revocation or deletion requested in Meditrust and within 30 days for revocation at Google. Contact support with questions or deletion requests. Use YouTube Studio to delete an uploaded video or change a release YouTube has already scheduled.

YouTube Terms of Service

Google Privacy Policy

Google API Services User Data Policy

Manage Google Account permissions

Support and deletion requests

Facebook and Instagram: connections and posts

If you enable My Instagram feed, the twelve latest posts from your selected professional account can be displayed on your website through an embed code. Images and thumbnails are loaded from Meta servers, which receive the visitor browser technical information needed to load them. Meditrust temporarily stores captions, links and media addresses. This snapshot stops being served after two hours and is then erased in bounded batches by the scheduled task. Images are not copied to a permanent library. Synchronization requires eligible Social access and a valid Instagram connection. You can disable the feed or replace its public link in this screen. Disconnecting or deselecting the account invalidates its feed links and snapshots.

When you enable the Meta connection, Meditrust stores identifiers and labels of the Facebook Pages and linked professional Instagram accounts you manage, their permissions and the destinations you select. API tokens are encrypted in private storage and are not sent to your AI assistant.

Texts and images you confirm are sent to Meta for immediate publication or at the scheduled time. Instagram retrieves an image through a temporary link; private storage is not opened as a whole. Post identifiers, confirmations and receipts support tracking and duplicate prevention. Private messages, comments, advertising, Reels and stories are outside this connection.

You can disconnect Meta in Meditrust and remove the integration in Facebook settings. Disconnecting stops future sends and removes local tokens; it does not remove posts already sent. Requests to delete Meta-related data follow the Social identity checks and erasure deadlines described below. Images reserved for a schedule are retained through its due time and applicable tracking period. Unused images follow the 24-hour period, terminal media the 7-day period and confirmations the 30-day period.

Meta applies its own policy to data it receives. An uncertain result is not automatically resent and may require checking the relevant network.

Meta Privacy Policy

1. Publisher and scope

Meditrust Social is provided by IHT Consulting. This policy covers the Social workspace, its MCP server and data exchanged with the AI assistants you authorize.

IHT Consulting manages the data needed for your account, billing and service security. For your business鈥檚 Google content and data, you determine the uses and requested actions; Meditrust processes them to provide those functions.

Publisher identity and legal notice

2. Data we use

  • Audience counters measure requested and displayed language, registrations, AI connections and usage. Approximate country is used only when supplied by the AI client. These hints may be missing or inaccurate and do not describe nationality. Counters are retained for 90 days. They contain no IP address, email, prompt, review or publication text. Accounts are distinguished by a technical pseudonym; visits are aggregated without a persistent visitor identifier. Referral attribution remains an unverified hint.
  • Account: first and last name, email address, phone number if you provide it, Meditrust identifier, signup language, access information and the dates of confirmed setup steps to help us support you. Your password is stored as a hash.
  • Connections: Google and MCP authorizations, Google account and profile identifiers, labels, and relationships between a main account and its authorized child accounts. Google credentials are used by the service and are not returned to your AI assistant.
  • Reviews and posts: review text, public author name, ratings, dates, replies, post content, images, schedules and results returned by Google. History is retrieved from Google; Meditrust records the data needed for actions, confirmations and duplicate prevention.
  • Subscription: plan, status, payment references, invoices and the billing country Stripe provides after card confirmation. Stripe processes payments; Social does not store your full payment card number.
  • Support and security: information you provide to support and technical logs needed for operation, diagnosis and abuse prevention.

3. Why we use it

Account and service processing relies on performance of the contractual relationship. Billing also serves legal obligations; security and handling support requests serve our legitimate interests. You choose and can withdraw Google and AI authorizations.

We do not sell your Social data or share your reviews, posts or images with third parties for their marketing.

  • Provide the requested service: sign in, select the right profile, read reviews and posts, reply to reviews, and publish or schedule posts with images.
  • Manage your subscription and billing obligations.
  • Provide support, protect access and prevent duplicate posts.

4. Connecting an AI assistant

When you connect an assistant, Meditrust receives the parameters of its tool calls, such as the selected account, reply or post text, image and publishing time. The integration does not request access to your complete conversation.

To carry out your request, the MCP server returns the relevant data to that assistant: accessible accounts and profiles, reviews, posts, action previews and results. You select the target and approve each reply or post in your AI assistant before it is sent to Google.

The data received by your AI provider is also subject to its privacy policy and your settings with that provider. Revoking the Meditrust connection stops future access; it does not erase data already received by the assistant.

5. Recipients and third parties

Data is accessible to authorized IHT Consulting personnel and providers needed for hosting, storage, security, service emails and payments. It is sent to Google for requested functions and to the AI assistant you connect for authorized tool calls.

Google, Stripe and your AI provider apply their own policies. Depending on the provider, processing may take place outside the European Economic Area; their policies describe the applicable locations and transfer safeguards.

Use of information received from Google APIs is limited to authorized service functions and adheres to the Google API Services User Data Policy, including the Limited Use requirements.

6. Retention and deletion

Deletion at Meditrust does not remove reviews or posts already present on Google or data held by your AI assistant. Contact those providers as well if you want data deleted there. Backup and restoration operations must respect processed deletion requests.

  • Account data and records needed to provide the service are kept while your Meditrust account exists. Canceling MediSocial does not automatically delete that account.
  • After a verified account deletion request, the relevant access is stopped and personal Social data is deleted within 30 days. The affected accounts and data are determined from your request; a matching Google profile does not establish ownership of another account.
  • An uploaded image that is not used can be deleted after 24 hours during daily cleanup. An image associated with a post remains available while the post is scheduled or its outcome is uncertain, then for 7 days after Google confirms a final state.
  • Action confirmation data is kept for 30 days after expiration, then removed during daily cleanup. Expired MCP codes, cursors and tokens are also removed during that cleanup; a revoked authorization stops working immediately.
  • Invoices and accounting records required by law are retained for the applicable statutory period, including ten years for accounting documents. Their retention does not maintain any Social or MCP access.

7. Cookies and access protection

A functional cookie remembers your explicit language choice for 365 days. On the first visit, browser language is used as a hint; your manual choice takes priority.

The Social workspace uses a session cookie for sign-in, form security and language. Connections to the service use HTTPS. Access is checked for the relevant account and profile; MCP authorizations can be revoked from Social.

Measurement preferences let you accept or reject Google Analytics and advertising attribution. Your choice is remembered for 180 days. If you agree, we measure the visit, form start, account creation, email verification, opening Stripe and card confirmation. We send Google technical measurement identifiers, the steps and their dates, without sharing your contact details or card data. If you agree to advertising measurement, we retain the Google Ads hint and campaign number supplied in the link when available. A confirmed card may be attributed to a Google ad. You can change your choice in the Social footer. Meditrust keeps technical data for this journey for up to 66 days.

Avoid including confidential or health data in posts and AI requests. Never send passwords, sign-in codes or tokens to support.

8. Your rights and controls

You can request access, correction, deletion, restriction, portability or object to processing of your data, subject to applicable legal conditions. We may request information needed to verify your identity before processing a request.

For data requests or account deletion, use support or email contact@meditrust.io. Specify the affected accounts. You can also complain to the French data protection authority, CNIL.

Contact Social support

Manage and revoke my AI connections

Manage my Google authorizations

Submit a complaint to CNIL

9. Changes to this policy

The date at the top identifies the current version. Material changes to how we use your data will be communicated through the service or by email. New features remain within granted permissions and the purposes of Social.