USING MEME PUBLISHER

Terms of use

Effective date: 27 October 2026

These terms cover Meme Publisher (Terenval Meme Publisher), its optional server worker and this website, provided by the Terenval project. Contact: agataromansky@gmail.com.

1. Review before use

Read these terms and the Privacy policy before using the application. Version 0.3.0 requires explicit acceptance of the current documents before opening the desktop workspace or processing its queue. The documents are available in the app even offline. Use only accounts you own or are authorised to manage. If you do not accept these terms and the privacy practices, do not connect an account or publish through the application.

2. Platform terms

Meme Publisher uses YouTube API Services. By using its YouTube features, you agree to be bound by the YouTube Terms of Service. Your use must also comply with YouTube's applicable policies, account restrictions and API requirements. Optional Instagram features require an eligible professional account and compliance with the Instagram Terms of Use and applicable Meta policies. Meme Publisher is independent of Google, YouTube and Meta; none endorses this application.

3. Your content and permissions

You retain your rights to your content. You instruct the application to process, store and transmit your selected files and metadata only as needed for the features you use. You are responsible for rights to clips, audio, images, likenesses and trademarks, and for required licences, consent, attribution, paid-promotion and synthetic-media disclosures. The application does not grant rights to third-party material or guarantee that an edit qualifies as fair use.

4. Review publishing instructions

Review the connected channel, exported video, title, description, audience declarations, visibility, date and timezone before starting a queue. YouTube jobs use your choice of Private, Unlisted or Public; existing jobs keep their recorded visibility and channel when settings change. Instagram publishing through the current integration is public. A running publisher may send approved jobs automatically at their scheduled time.

5. Operation and interruptions

Publishing requires a working connection, valid authorisation, available quota and an eligible account. Desktop publishing needs the PC awake; server publishing needs a separately configured running worker. Only one publisher should own a workspace queue. API changes, expired grants, platform processing, outages and moderation may delay or block publication. Check remote status before retrying an uncertain upload to avoid duplicates.

6. Account control and deletion

You may stop the publisher and disconnect an account. Revoke Google access through Google Account connections. Disconnecting does not delete already published content; use the platform's own controls. See the data deletion instructions for local and server copies.

7. Responsible use

Do not use the application for unlawful content, infringement, spam, impersonation, harassment, misleading engagement or circumvention of platform restrictions. Protect credentials and public media links. The software does not guarantee views, monetisation, reach or permanent API availability. Creator messages and links in exported videos do not change these requirements.

8. Availability and changes

The application is in a limited rollout and may change as platform requirements evolve. These terms do not promise continuous service or a particular publication outcome. Nothing here limits rights or obligations that cannot be excluded by applicable law. Material changes to these terms will be reflected on this page with a new effective date.

9. Contact

For support, access or privacy requests, email agataromansky@gmail.com. Provide the app version and a description of the issue, with passwords, tokens and private account information removed.