Platform Integrations
We publish across several platforms and use their official developer APIs to do it. This page states plainly what each integration does, what data it touches, and what it never touches.
TikTok
Purpose. Publishing our own educational videos to our own TikTok account, and reading the performance of those videos so we know which lessons are useful.
What the integration accesses: basic information about our own account (open ID, display name, avatar); the ability to upload and publish a video to that account; statistics for videos we published.
What it never does: read other users' private data, post to accounts that are not ours, or access the TikTok inbox of any third party.
Storage. The access token for our own account and a log of our own posts. Tokens are stored outside public code and are revoked when no longer needed.
Meta — Instagram and Threads
Purpose. Publishing our own posts, carousels and reels to our own Instagram professional account and our own Threads profile, replying to comments on our own posts, and reading insights for our own content.
What the integration accesses: profile information of our own accounts; media we publish; insights and metrics of our own posts; public comments and mentions left on our own content, so that we can reply.
What it never does: serve or manage Instagram accounts belonging to other people, scrape follower lists, or build advertising profiles.
Comments and messages. If you comment on our post or message us, we see what the platform shows us — your public username, your message, its timestamp — and we use it to reply and to moderate our own channel. You can ask us to delete it at any time: see Data Deletion.
Google — YouTube
Purpose. Uploading our own long-form and short-form lessons to our own YouTube channel, scheduling their publication, and reading the analytics of our own channel.
What the integration accesses: our own channel details and the ability to upload, schedule and manage our own videos; analytics for our own content.
What it never does: access other channels, read viewers' personal data, or use Google user data for advertising or profiling.
Google user data. The only Google account involved is our own. Its authorisation token is stored securely, used exclusively for the publishing purposes described above, never sold or transferred, and revoked on request or when the integration is retired.
Telegram
Purpose. Delivering our free daily brief and managing access to our paid channel.
What we hold: your Telegram user ID and public username as the channel operator, plus a subscription record (status and dates) if you purchased access. Payments are processed by a third-party provider — we never receive card numbers, bank credentials or wallet keys.
Data retention and deletion
Access tokens live until they expire or are revoked. Metrics of our own content are kept up to 24 months. Correspondence is kept up to 24 months after the last message. Subscription records are kept as required by accounting rules.
You can ask us to delete anything we hold about you at any time — the process, and how long it takes, is on the Data Deletion page. The full legal detail is in our Privacy Policy.
Security
Credentials and tokens are kept outside of published code in access-controlled storage, and access is limited to the operator. If we ever suspect a token has been exposed, we rotate it immediately.