Privacy Policy

Last updated: 2 October 2026

MOOW Journal ("MOOW", "we") is an independent editorial publication about architecture, interiors and objects. This page explains what data moowjournal.com and MOOW's internal publishing system handle. You can reach us at[email protected].

This website

moowjournal.com is a static publication. It has no user accounts, comment system, forms or sign-in, and we do not collect personal information from readers. We do not set advertising or cross-site tracking cookies. Like any website, our hosting and delivery provider (Cloudflare) processes technical request data, such as IP address, browser type and the page requested, in order to deliver the site and keep it secure. If we ever add aggregate, privacy-respecting analytics we will describe it here first.

Our accounts on other platforms

MOOW publishes its own stories to its own accounts on social platforms (currently Instagram, Facebook, Pinterest and YouTube) using each platform's official API. The MOOW account owner grants access once through the platform's standard OAuth consent screen. Through that access, MOOW publishes MOOW's own content to MOOW's own accounts. We do not use these connections to collect data about other users, followers or viewers, and we do not sell, rent or share any platform data with third parties.

Google and YouTube API Services

MOOW operates a single, internal publishing system (the "API Client") that publishes MOOW's own short videos to MOOW's own YouTube channel, @moowjournal. The API Client is used only by MOOW. It is not offered, licensed or made available to any third party, and it does not serve other YouTube channels, creators or end users.

MOOW's use and transfer to any other app of information received from Google APIs will adhere to theGoogle API Services User Data Policy, including the Limited Use requirements. MOOW's use of YouTube API Services is also subject to theYouTube Terms of Serviceand theGoogle Privacy Policy.

Access we request

The API Client requests two OAuth scopes, and only for MOOW's own YouTube channel:

• https://www.googleapis.com/auth/youtube.upload: to upload MOOW's own videos (title, description, tags and the video file) to the @moowjournal channel.
• https://www.googleapis.com/auth/youtube.readonly: to read information about MOOW's own channel and the videos it has uploaded, such as upload status.

What data is accessed and how it is used

The data involved is MOOW's own: the OAuth tokens that authorize the connection, and the identifiers, upload status and aggregate view, like and comment counts of the videos MOOW itself uploads. We use it only to publish MOOW's own stories to YouTube and to confirm that those uploads succeeded. We do not access private data of other YouTube users, we do not use the data for advertising, profiling or data-broker purposes, and we do not transfer it to third parties, except as necessary to operate the service (see "Storage and retention") or to comply with law.

Storage and retention

The OAuth access and refresh tokens are stored server-side in MOOW's own access-restricted database (hosted by Supabase) and are used only by MOOW's publishing system. They are not exposed on this website or to readers. We keep the tokens for as long as the YouTube connection is active and, when the connection is removed, the MOOW account owner deletes them manually (token deletion is not automated). Video identifiers and URLs of our own published videos are kept in our publishing records as part of MOOW's editorial archive.

Authorization and revocation

Access is granted by the MOOW account owner through Google's OAuth consent screen. It can be revoked at any time atmyaccount.google.com/permissions(Google Account security settings, "Third-party apps and services"), or by emailing[email protected]. When access is revoked, the stored tokens stop working and we stop using the connection; the MOOW account owner then deletes the stored tokens manually (token deletion is not automated).

Deletion

You can ask us to delete any data we hold, including stored YouTube tokens and records derived from Google user data, by emailing[email protected]. We will act on the request promptly. Videos that MOOW has published to its YouTube channel are MOOW's own content and can be removed by MOOW from the channel on request.

Pinterest and TikTok

MOOW has applied for API access to Pinterest to publish its own pins to its own account; that access is subject to Pinterest's review. MOOW's TikTok integration is not in production, and MOOW does not publish to TikTok through an API. If either changes, we will update this page before use.

Retention and your choices

We keep only what is needed to publish and archive MOOW's own work. Because we do not collect personal information from readers, there is normally nothing to access or delete; if you believe we hold information about you, write to us and we will respond and, where appropriate, delete it.

Changes

If this policy changes, we will update this page and its "last updated" date.