Facebook and Instagram: connections and posts
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.
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’s Google content and data, you determine the uses and requested actions; Meditrust processes them to provide those functions.
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, Meditrust identifier, language and access information. 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 and invoices. 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.
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.
Manage and revoke my AI connections
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.