Legal

Privacy policy

ParkourFlux is operated by a single individual. The publishing tool described on this site is used only to post ParkourFlux's own videos to ParkourFlux's own accounts. It has no other users.

Last updated: August 6, 2026

Who this covers

This policy covers the ParkourFlux website and the in-house publishing tool that uploads our videos to our own social accounts. There is no sign-up, no account system, and no way for another person to connect an account to the tool.

Data we collect from visitors to this site

None. This site is a set of static pages. It sets no cookies, runs no analytics, embeds no third-party trackers, and has no contact form. Our hosting provider may keep standard server request logs, which we do not access for any purpose beyond availability.

Data the publishing tool handles

• Authorisation tokens for the social accounts we own — YouTube, Instagram and TikTok. These are stored locally on the operator's own machine, excluded from version control, and transmitted only to the platform that issued them.
• Our own published content — the videos, captions and titles we produce, plus a local log of what was posted and when.
• Aggregate performance figures for our own accounts — view and subscriber counts retrieved from the platforms, used to decide what to make next.

Data we do not collect

• No personal data about viewers, followers or other creators.
• No content belonging to anyone else is read, downloaded or stored.
• No data is sold, shared, or passed to third parties.
• No advertising or cross-site tracking of any kind.

Where data is stored

On a single machine operated by us. There is no hosted database and no server that accepts connections from the public. Credentials are held in local files that are not published, not committed to source control, and not backed up to any shared location.

Third-party platforms

Publishing necessarily sends our videos and their captions to the platforms we post on — YouTube, Instagram and TikTok. Their own privacy policies govern what they do with that content once published. We also use a text-generation and a speech-synthesis provider to draft and narrate our scripts; only our own draft text is sent to them.

Revoking access

Because the tool acts only on accounts we own, revocation is something we perform ourselves through each platform's app-permissions screen. Doing so immediately invalidates the stored token.

Changes

If this policy changes, the updated version will be posted here with a new revision date.

Contact

Questions about this policy: mindcraftkrish.patel@gmail.com