These terms describe the current YennayApps Social Publisher workflow and do not claim a TikTok endorsement, partnership or capability that has not been enabled.
1. Scope of the service
YennayApps Social Publisher helps authorised users review prepared social content, manage configured destinations and, where the required platform permission is available, submit operator-approved content to a connected platform.
The public YennayApps product pages are separate from the authenticated operator application. Publishing access remains controlled even though the product, privacy, terms, support and reviewer information are public.
2. Authorised connected-account use
You may connect, select or manage only social-media accounts that you own or are authorised to manage. You are responsible for ensuring that the correct TikTok account is authorised and selected for each submission.
You must comply with TikTok's rules, terms, developer requirements and applicable law when using the TikTok integration.
3. Operator responsibility for content
The operator is responsible for the content they review and approve, including captions, images, videos, rights, claims, links and destination selection. Prepared or AI-assisted content must be reviewed before submission.
YennayApps does not guarantee that prepared content is accurate, lawful, complete, suitable for a particular audience or accepted by a third-party platform.
4. TikTok draft delivery and publication status
The current production TikTok workflow is draft delivery. Approved content is sent through TikTok's Content Posting API to the authorised creator's TikTok draft workflow so the creator can continue editing and posting in TikTok.
Draft delivery is not successful publication. A successful upload or draft result does not mean that the content has been publicly posted on TikTok.
Direct Post is not currently enabled. Direct publishing would be a separate capability subject to separate product acceptance, TikTok permissions, review and platform requirements.
5. Third-party platform requirements
TikTok and other connected services are third-party platforms. Their APIs, permissions, limits, review processes, availability and policies can change independently of YennayApps.
Nothing on this site represents YennayApps as an official TikTok partner or as holding an approval that has not been independently granted.
6. Security, misuse and suspension
You must not expose credentials or tokens, access accounts without authority, bypass platform controls, distribute unlawful or malicious content, impersonate others or deliberately cause unauthorised submissions.
YennayApps may suspend or restrict operational access where reasonably necessary to protect connected accounts, the service, third-party platforms or users, or to respond to suspected misuse or security risk.
7. Account disconnect and revocation
An authorised operator may disconnect a stored TikTok connection through the authenticated Publishing > Connections area. Reconnecting requires the TikTok OAuth flow again.
A TikTok account holder may also revoke YennayApps authorisation using TikTok's own account or application controls where available. Revocation can prevent the affected workflow from operating.
8. Service availability and platform processing
YennayApps cannot guarantee uninterrupted access to a third-party platform, successful media transfer, draft creation, inbox delivery, continued API availability or any later publication action performed in TikTok.
Platform processing can fail, be delayed or be rejected for reasons outside YennayApps' control. Operators should review the resulting status and complete any required TikTok-side actions.
9. Data and privacy
Connected-account identity, OAuth credentials, draft media and operational records are handled as described in the YennayApps Social Publisher Privacy Policy. Data-disconnection and deletion guidance is available on the data deletion page.
10. Support and contact
The public Support page provides an externally reachable contact form without operator login. Accepted requests receive a public reference. Email is required for the current support-team reply path and as the durable acknowledgement fallback. WhatsApp may be offered only for the automated receipt acknowledgement when the server-side provider and approved acknowledgement template are configured.
Current support-team replies are sent by email. Submitting a support request does not guarantee immediate provider delivery or a particular response time. Do not include passwords, OAuth tokens, client secrets, signing secrets or authentication codes in a support request.
11. Changes to these Terms
These Terms may be updated when the service, confirmed legal information, platform permissions or support arrangements change. The date above will be updated for material changes.