Skip to content

Plano Base Redes

Privacy policy of the social media app

The Plano Base social media app ("the app") is the internal tool that the staff of Plano Base Arquitectos S.A.S. use to schedule and publish content on the studio's own Instagram, Facebook, Threads, TikTok, LinkedIn, X and YouTube accounts. This policy explains what data the app receives from those platforms, what it uses them for, where it stores them, for how long and how to ask for them to be deleted. It complements the studio's personal data policy (planobase.co/en/politica-de-datos), which governs anything not covered here. This English text is a courtesy translation: the binding document is the Spanish one.

Effective date: 17 November 2026

Who is responsible for your data

The Plano Base social media app belongs to Plano Base Arquitectos S.A.S., a company domiciled in Cali, Colombia, which is the data controller for the data described here.

  • NIT (tax ID): 901603373-9.
  • Address: Calle 18 # 61-29, Cali, Valle del Cauca, Colombia.
  • Email: proyectos@planobase.co
  • Phone: +57 315 952 6281

Requests, queries and complaints about these data are handled by the Projects Office, at proyectos@planobase.co.

Who uses the app

Today it is used only by studio staff with named access, to publish on the accounts and Pages of Plano Base. The app is not open to the public and is not offered to third parties. If it is ever opened to other people or companies, this policy will be updated before they can connect their accounts.

What data it receives from each platform

When an authorized person connects an account, the platform asks for their permission on its own screen and gives the app an access token. With it, the app reads what it needs to know which account it is publishing to and to run the studio's inbox (the comments and messages its accounts receive and the insights of its posts):

  • Instagram: the ID and username of the professional account; the comments on its posts, with the commenter's username; the insights of each post and of the account (reach, views, likes, comments, saves, shares); and the direct messages the account receives and sends.
  • Facebook: the ID and name of each Page the person manages and can create content on, and that Page's access token; the comments and reactions on its posts, with the commenter's public name; the insights of the Page and of each post (reach, views, reactions, clicks); and the Page's Messenger messages.
  • Threads: the ID and username of the account; the replies to its posts, with the replier's username; and each post's insights (views, likes, replies).
  • TikTok: the account ID (open_id), its display name and username; before each post, the privacy options the account allows; and the insights of the account (followers, likes, video count) and of its public videos (views, likes, comments, shares).
  • YouTube: the channel's ID and name, and permission to upload videos to that channel. Channel statistics (subscribers, views and number of videos) and each video's statistics (views, likes and comments) are read on demand to show them in the dashboard; no copy is kept. Only data from the studio's own channel is read or uploaded.
  • LinkedIn: the ID and name of each company Page the person administers, and the comments and reactions on its posts, with the commenter's public name.
  • X: the ID, name and username of the account.

For each post it also stores the text, the images or video, the date and time, the platform, the result (published or failed) and the ID or link the platform returns. For each person using the app it stores their studio email, to know who scheduled or approved each post.

About other people, the app only keeps what they themselves wrote to the studio's accounts (comments, replies and messages) and their public name, so the studio can answer them. It does not build follower profiles, does not read follower lists or private data and never receives the password of any account. If it ever asks for another permission, this policy will say so first.

YouTube API Services

This app uses YouTube API Services to upload the videos you schedule to the studio's channel and to show you that channel's figures. By connecting the channel, you also agree to the YouTube Terms of Service (https://www.youtube.com/t/terms). Google handles your account information under the Google Privacy Policy (https://www.google.com/policies/privacy).

Plano Base Redes' use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. We do not share the data we receive from YouTube with third parties or use it for advertising.

You can revoke Plano Base Redes' access to the channel at any time: with "Disconnect" in the dashboard, or from your Google Account security page (https://security.google.com/settings/security/permissions). With "Disconnect", we delete the permission and the stored channel data at once. If you revoke access from Google, we delete them within 30 days. If you ask us to delete them, we do so within 7 days. Deleting this data does not affect what YouTube stores in your account.

What it uses them for

  • Showing studio staff which accounts are connected.
  • Publishing, at the scheduled time, the content the studio approved, on the chosen account and platform.
  • Knowing whether each post went out, retrying if the platform failed and keeping its link.
  • Showing studio staff, in one place, how each post is doing (its insights) and the comments and messages their accounts receive, and answering them from there.
  • Renewing each account's token before it expires, so that scheduled posts are not lost.

Platform data are not used for advertising, are not sold, are not shared with third parties and are not used to train artificial intelligence models.

Where they are stored and who else handles them

Platform tokens are stored encrypted (256-bit AES-GCM) with a key known only to the server. These providers handle them on the studio's behalf, without using them for their own purposes:

  • Cloudflare, Inc., processing in the United States and other countries: the app server, its database, image and video storage and the publishing queue.
  • Vercel Inc. and Supabase Inc., processing in the United States: the site panel where studio staff schedule and review the calendar, and its sign-in.

Instagram, Facebook and Threads (Meta Platforms), TikTok, LinkedIn, X and YouTube (Google) receive what the studio publishes because the studio instructs it. They are not processors of Plano Base: each handles it under its own policy.

Colombia's data protection authority, the Superintendencia de Industria y Comercio, lists the United States among the countries with an adequate level of personal data protection (Circular Externa 005 de 2017).

How long it keeps them

  • Platform tokens: while the account stays connected. They stop working if the platform revokes them or if the app's access is removed from the platform, and they are deleted when you ask.
  • Account data and post history: while they are needed to run the studio's calendar, and they are deleted when you ask.
  • Comments, replies, messages and insights: up to 12 months after they are received, to attend to whoever wrote; they are deleted sooner if you ask.

How to ask for deletion

The full instructions are at planobase.co/en/app-de-redes/eliminar-datos. In short: remove the app's access from the platform's settings and write to proyectos@planobase.co with the subject "Delete my data from the social media app". We handle it within fifteen business days at most.

Your rights

As the data subject you have the rights in article 8 of Ley 1581 de 2012 (Colombia's data protection law): to access, update, correct and delete your data, to ask for proof of your consent, to know how they were used, to withdraw consent and to complain to the Superintendencia de Industria y Comercio. They are exercised as the "How to exercise them" section of the studio's general policy explains, with the same time limits.

Changes to this policy

If it changes, we will publish the new version here with its number and date. If the change affects the data the app receives from the platforms or what it uses them for, it is published before it applies.

Effective date

  • This version takes effect on: 17 November 2026. Version 1.1.