Terms of Use
Effective from
1. The service and its operator
These terms govern use of the Media.InvaLife website (media.invalife.org) and the Media.InvaLife Newsroom editorial platform (newsroom.media.invalife.org), including available content preparation and social account connection features.
The service is operated by Public Association INODA “InvaLife”, 38 Tekstilshchikov St., Tiraspol. These terms apply to website visitors and editorial platform users in relation to the features they use.
2. Access and accounts
Public website materials can be read without an editorial account. Creating, editing and publishing materials is available to authorized users according to their roles and permissions.
Users must protect their access credentials, avoid sharing them with unauthorized persons and notify the editorial team of suspected unauthorized access. Users may connect only accounts they own or are authorized to manage.
3. Use of published materials
Rights in texts, photographs, videos, illustrations and other materials remain with their respective rights holders. Displaying material on the website does not transfer exclusive rights to a visitor.
Materials may be used within applicable law, the rights holder’s conditions and any permissions granted. When quoting, identify the author where stated and credit Media.InvaLife with a link to the original. Obtain prior permission where the intended use requires the rights holder’s consent.
4. Materials submitted to the editorial team
Anyone submitting text or images for publication must hold the necessary rights and have a valid basis for disclosing the information and personal data they contain.
Submitting material specifically for publication grants the editorial team non-exclusive permission to store, edit, translate, format and publish it on the website and agreed channels to the extent needed for that purpose, unless otherwise agreed separately. Exclusive rights are not transferred. The editorial team may request evidence of rights, make agreed changes or decline publication.
5. Social networks and TikTok
An authorized user may connect a supported social network through that platform’s authorization process. TikTok connections use Login Kit; user.info.basic identifies the connected account, while video.publish is used to send photo posts through Content Posting API / Direct Post. Feature availability depends on granted permissions and TikTok restrictions.
The selected images, title, description and other necessary parameters are transmitted to the social network for publication. Before sending, users must check the content, destination account and visibility settings, and meet the platform’s requirements for consent to transmission.
If automatic export after website publication is enabled, materials are sent to selected networks according to saved settings. This mode may be used only within the relevant platform’s permissions and rules; the general switch does not replace separate confirmation where a platform requires it. Connecting an integration does not guarantee platform approval of the app, acceptance of a particular post or public visibility.
6. Managing connections and posts
An authorized user may stop automatic sending in the Newsroom “Social networks” settings and exclude a network from exports. App authorization can also be revoked in the connected social network’s account settings. Users may contact the editorial team about disconnecting accounts and deleting data.
Editing or deleting a website article, or disconnecting an account, does not automatically edit or remove posts already transmitted to a social network. Such posts must be managed separately using that platform’s tools.
7. AI tools and editorial review
AI tools assist with texts, translations, descriptions and illustrations, but may produce factual, linguistic or other errors. Before publication, users must review the output, sources, rights and the accuracy of images. An authorized editor makes the final decision to publish an article.
Website materials are informational and do not replace individual medical, legal or other professional advice.
8. Acceptable use
Unauthorized access to accounts or data, interference with the service, malicious code, spam, impersonation, copyright infringement and disclosure of information without a lawful basis are prohibited.
Where a violation or security threat is identified, the editorial team may restrict the affected functions or access and investigate. Editorial decisions and user actions are recorded to the extent supported by the service’s implemented logs.
9. Privacy
Visitor data processing and cookie use are described in the separate Privacy Policy and Cookie Policy linked below.
When social accounts are connected, the service processes connection information provided by the platform, including account identifiers and names, and access tokens within granted permissions. Tokens are used on the server to operate the integration. The social network processes content transmitted to it under its own terms and privacy policy. Data-related requests can be sent to stat@media.invalife.org.
10. Availability and limitations
Some features depend on servers, third-party services, limits and permissions. Technical interruptions, delays, rejected requests or a need to authorize again may occur. If sending fails, check the task’s status before retrying to avoid duplicate posts.
The service does not guarantee a particular number of views, reach, continuous availability of third-party platforms or error-free automated results. These terms do not exclude liability that cannot be limited under applicable law or override mandatory user rights.
11. Changes and contact
The current terms are published on this page with their effective date. Changes apply to subsequent use and do not retroactively alter rights already granted. Actions requiring separate consent must obtain that consent separately.
Editorial contact and questions about these terms: info@media.invalife.org. Personal data and requests to disconnect associated data: stat@media.invalife.org. Postal address: 38 Tekstilshchikov St., Tiraspol.
