Privacy Policy
How information is accessed and used with consent.
Last updated: 2026-10-18
1. Scope
Tainery Postiz (‘service’) is a privately hosted tool that lets authorized users manage, schedule and publish content to their social accounts. This notice covers information handled by the application and this public website.
2. Operator responsible for privacy and manual erasure
The Tainery operator personally serves as the person responsible for privacy and data-erasure requests. The operator manually receives requests, tracks deadlines, removes affected live data and backups, and verifies erasure and restored data. Lack of automation does not extend any deadline or waive these responsibilities. For data access, correction, deletion and revocation inquiries, contact keipodbeats@gmail.com.
3. Information accessed
Depending on consented OAuth scopes, the service may handle Google identity information (email and display name), YouTube channel IDs, metadata, video publishing status and analytics, and Instagram/Threads account identifiers, profiles and publishing results. Internally it handles drafts, uploaded media, schedules, status records, logs and administrative login sessions. Social account passwords are not requested for storage.
4. Purposes
These data support authorized account connection, channel listing, content and media management, user-directed uploading, editing, scheduling, publishing and analytics, troubleshooting and security. Google user data are not sold, used for ad targeting or used to train general-purpose AI models.
5. Google API user data and Limited Use
Data obtained via Google APIs are used exclusively for user-authorized YouTube channel management, publishing and requested analytics. They are not sold or disclosed to third-party advertisers. Operation is subject to the Google API Services User Data Policy, including its Limited Use requirements.
6. Storage and security
OAuth access/refresh tokens, account records and publishing content may be stored in the private service infrastructure. Communications use HTTPS, databases are not directly exposed to the internet, and administrative access is controlled. Absolute security cannot be guaranteed.
7. Third parties
To carry out user-authorized actions, the service uses YouTube API Services and communicates with Google/YouTube and Meta/Instagram/Threads APIs. Cloudflare provides network transport and protection. For information about Google's processing of data, see the Google Privacy Policy. Those providers apply their own privacy notices.
8. Deletion requests and account deletion: seven days from receipt
If a user requests deletion of data obtained using YouTube API Services or deletion of their Tainery Postiz account, the clock starts on the date the request is received, not when an operator later reviews it. We commit to deleting the associated authorized data, including affected backups, as soon as possible and no later than seven calendar days from receipt. The Tainery operator personally performs and verifies deletion of live records and affected backups within seven calendar days from receipt, including by manual procedures where automation is unavailable. Send requests to keipodbeats@gmail.com. Removing data stored by Tainery Postiz does not remove videos or other information hosted by YouTube; users must manage deletion of YouTube-hosted content separately on YouTube.
9. Removing a channel from Postiz is not Google OAuth revocation
The current ‘Remove from Postiz (not revoke)’ action removes a channel from the management list and may affect its scheduled posts; it does not immediately revoke Google OAuth tokens or erase the associated data or backups. An in-app automatic Google token revocation and verified data-erasure workflow has not yet been implemented or validated. To revoke access now, use Google Account Permissions to revoke Tainery Postiz directly. The Tainery operator manually handles credential and stored-data removal requests, but the email-based process is not an instant in-app token revocation mechanism. Submit a separate stored-data deletion request to keipodbeats@gmail.com. If an in-app revocation mechanism is introduced, it will be implemented and verified to revoke the corresponding token programmatically immediately at the time of revocation and erase authorized data and affected backups within seven calendar days of that event. Do not regard the current channel-list removal control as completed authorization withdrawal.
10. Revocation in Google Security Settings: 30 days from revocation
If a user revokes access directly through Google Security Settings or Google Account Permissions, the service must periodically revalidate authorization, stop accessing the revoked data, and delete associated API Data as soon as possible and no later than 30 calendar days from the date that revocation occurred in Google settings. The Tainery operator is responsible for manually checking and deleting affected API data and backups, even if revocation is discovered later; the original revocation date remains the deadline's starting point.
11. Backups and prevention of reintroduced deleted data
Ordinary database and media snapshots are created daily, and files older than five days are removed in a daily sweep (normally rotating out within about six days). Ordinary backup expiry alone does not guarantee the applicable user-deletion deadline. When deletion or revocation occurs, the Tainery operator personally identifies and manually purges affected backups or replaces them with verified cleansed backups, within the same applicable deletion deadline. If restoring an earlier backup, the operator must reapply all recorded deletion and revocation requests and verify erasure before re-enabling access to the affected data. Any statutory retention exception is limited to what applicable law requires.
12. Cookies and automation
The management app uses session information and security logs. This public website does not load third-party advertising or visitor-tracking JavaScript. Approved publishing schedules and MCP tools act within the scope of users’ grants.
13. Updates
Material changes will be reflected on this page. Effective and last updated: 2026-10-18.