Privacy Policy
What uplika collects, and what we do with it.
Last updated 2026-11-20
uplika publishes to social channels on your behalf, on instructions from you or from an AI agent you connected. This policy sets out what we receive, what we use it for, and who we pass it to.
We do not do what is not written here. If we ever need your data for a purpose not listed, we change this document first.
Who operates uplika
| Item | Detail |
|---|---|
| Business name | ์ดํ STRING |
| Representative | ํ๋ฏธ์ |
| Business registration number | 226-04-37766 |
| Address | 402-1, 316 Tanjung-ro, Ilsandong-gu, Goyang-si, Gyeonggi-do, Republic of Korea |
| Contact | support@uplika.com |
Throughout this policy, "we" means the business above. It is the entity that decides why and how your personal data is processed.
What we collect
| Item | Category | Why |
|---|---|---|
| Email, name, profile image | Account | Taken at sign-up. From Google or GitHub if you sign up that way, from you if you use email. |
| Password | Account | Email sign-up only. Stored as a hash; we never keep the plaintext. |
| Phone number (sign-ups before 28 September 2026) | Identity | We no longer ask for a phone number at sign-up. Numbers we verified before that date are kept apart from your account and used for nothing. They go when you delete your account. Stored in international format (E.164). Never used for marketing. |
| IP address, browser | Session | Session management and spotting unusual sign-ins. |
| Sign-up country | Account | When you sign up we keep one country code (for example, KR) for where you connected from. Cloudflare estimates it from your IP address, and we do not store the IP address with it. We use it only to count which countries sign-ups come from. |
| Channel access token | Channel | Kept so we can publish on your behalf. Stored encrypted, destroyed when you disconnect the channel. |
| Channel profile | Channel | The username, display name, profile image URL and platform account id of the channel you connected, so the dashboard can show you which account it is posting to. |
| Posts and media you publish | Service | Kept to show your publishing history and why anything failed, along with the post id and permalink the platform returns. Deleting a post from the channel does not delete our record. That is what lets you still see how far it reached, and it goes when you delete your account. Images and videos you attach are deleted automatically 24 hours after the post settles. |
| Posts we open from your channel | Service | When you open one of your existing channel posts by link, we store its text, id and permalink so the reply, metrics and delete features have something to point at. Only for accounts you connected. |
| Automations, contacts and conversations | Service | The comment and DM automations you build on a connected account and their run history, the channel id, username, name and profile photo URL of people who comment on or message that account, and the messages exchanged with them. Kept so automatic replies and the inbox work. When you disconnect the account they are hidden and kept for 30 days, so reconnecting the same account to the same workspace picks them up again. After 30 days they are deleted. |
| Post metrics | Service | Views, likes, replies, reposts, quotes and shares. We ask the channel for them only when you or a connected agent look at that post's metrics, and keep one row per post per day: looking again the same day replaces that day's numbers. We do not collect them on a schedule. The platform does not backfill past numbers, so a trend line only exists for the days the metrics were looked at. |
| API keys | Developer | Only the hash is stored. The plaintext is shown once, at creation. |
| Request logs | Operations | Incident tracing and abuse prevention. Deleted automatically after 7 days. |
| Keyword research records | Service | When you save a keyword research (in the market research screen, or through a connected agent), we keep the keywords you entered, the chosen set and the prompt built from it, so you can come back to it. Deleted with your account. |
| YouTube search history | Service | When you search in the YouTube search research tool (or a connected agent searches for you), we keep the search, its filters, your topic and the public video data YouTube returned for it: title, channel, thumbnail, view and subscriber counts, length and publish date. That is so you can reopen the search. Deleted automatically within 30 days, or at once when you delete your account. |
| Google Analytics connection | Analytics connection | If you connect a GA4 property: the encrypted access and refresh tokens, the property's id and name, the name of the account it sits in, its time zone and currency, and your Google account id (sub). Reports are not stored. The Google Analytics and Google Ads data section below has the detail. |
| Google Ads connection | Ads connection | If you connect a Google Ads account: the encrypted access and refresh tokens, the account's id and name, its currency and time zone, whether it is a test account, the manager account it is reached through, the daily budget cap you set, your Google account id (sub), and a record of what uplika created, changed or removed there. Metrics are not stored. The Google Analytics and Google Ads data section below has the detail. |
| Meta Ads connection | Ads connection | If you connect a Meta ad account: the encrypted access token, the ad account's id and name, its currency, time zone and status, the id of the business it is shared from, whether it is a test account, and the permissions you granted. If you also allow management: the daily budget cap you set and a record of what uplika created, changed or deleted there. Metrics are not stored. The Meta Ads data section below has the detail. |
| Naver search check records | Service | When you check how Naver search shows a keyword or a blog (the blog diagnosis and AI Briefing check in market research's Naver keyword research, or a connected agent), we keep, for each keyword, when it was checked, whether an AI briefing answered it and the public sources it listed (titles, sites and addresses), where blog posts appeared in the search results, and the related questions. For the posts we watch for you, we keep the main keyword and how their place changed. We do not keep the AI briefing's answer text or the search page itself. Kept up to 400 days, or deleted at once when you delete your account. |
| Support messages and attached images | Support | What you send through the Contact us window in the dashboard, with any images, so we can answer it. The page you sent it from and your account email are kept with it. Images are deleted after 90 days. |
| Subscription status | Billing | Whether you subscribe and when it renews. Card details never reach our servers. |
| Analytics cookie | Traffic | Google Analytics sets a cookie (_ga) that tells one visitor apart from another so we can count page views and where visits come from. It does not identify you and we do not store your IP address. It is not set on this page, the terms page, the data deletion page, or the upload page. |
| X credit balance and ledger | Payment | When you use X through uplika: your X credit balance, and an entry for each top-up, refund and credit grant and for each X call made for you. Entries stay as payment records after you delete your account, with your user id removed. |
Who we share with
| Recipient | What | Why |
|---|---|---|
| Google, GitHub | Sign-in | Email is exchanged when you sign up or sign in. |
| Google (Gmail) | Your address is used to send sign-up verification and password reset mail. | |
| Cloudflare | Network, image delivery | Requests to api.uplika.com pass through Cloudflare, which receives your IP and request details and uses them for DDoS protection and rate limiting. Images you attach are delivered through cdn.uplika.com. |
| Backblaze (B2) | Image and backup storage | Images you attach to a post are stored here, because the channel needs a public URL to fetch them from. Images attached to a support message are stored here too. Our database backups are kept here too. Deleted on the schedule below. |
| Google (YouTube Data API) | Search terms | The search terms you enter in the YouTube search research tool are sent to Google's YouTube Data API, which returns public video data: title, channel, thumbnail, view and subscriber counts, length and publish date. No account information goes with them. What comes back is kept for up to 30 days, as described below. |
| Google (Google Analytics Admin API and Data API) | Your report requests for the property you connected | When you connect a GA4 property, or you or your agent ask for a report, the request goes to Google with the Google token you connected, so that Google can answer it. |
| Google (Google Ads API) | Your instructions and report requests for the Google Ads account you connected, the images and YouTube video ids you choose as ad assets, and the sitelink, callout and snippet text and phone number you give for a campaign | When you connect a Google Ads account, or you or your agent ask for a report or a change, the request goes to Google with the Google token you connected, so that Google can carry it out. Images you choose as ad assets go with that request. |
| Meta (Marketing API) | Your instructions and report requests for the Meta ad account you connected | When you connect a Meta ad account, or you or your agent ask for a report or, with management allowed, a change, the request goes to Meta with the Meta token you connected, so that Meta can carry it out. When an ad creative is made from your uplika media, uplika uploads the images to Meta, and Meta fetches the videos from the address uplika gives it. |
| Google (Google Ads API) | Keywords and the country and language you choose | Only when you ask for a search in the Google keywords research tool, on the screen or through a connected agent or API key. We send them to Google's Google Ads API through Uplika's own Google Ads account, which looks up search volume for them. Nothing that identifies you goes with them. The results are kept for 8 days, shared between users and not tied to any account, as described below. |
| Polar | Payments | Your email and payment details are passed on to process subscriptions, X credit purchases and refunds. |
| The channels you connect | Publishing | Post text and media are delivered to Threads and any other channel you connected. This happens on your instruction. |
| Vercel, HostHatch | Hosting | Infrastructure the service runs on. Access logs are kept there. |
| Google (Analytics) | Page views, referrer, device, approximate location | Traffic analysis: which pages are read and where visits come from. Google Signals is switched off, so nothing here is used for ad personalisation or cross-device tracking. Workspace names, upload links and agent authorisation requests are removed from the address before it is sent. |
| Google (Gemini API) | The post text you wrote, reduced copies of images you attached, and the brand voice you saved | Only when you press Generate with AI in the composer. Nothing is sent before that. Google's terms for the API tier we use say whether prompts may be used to improve its models; we link them from the composer. |
| Naver (Search Ad, API HUB) | Search keywords you enter in the composer's keyword card, the market research screen, or through a connected agent or API key | Only when you ask to measure them. Keywords are public search terms, not your posts; the measured numbers are cached for seven days and shared between users. |
| Naver (autocomplete) | Seed keywords an agent or API key asks to expand | Only when a connected agent or an API key calls the keyword expansion, and only if that feature is switched on for the server (it is off by default). Our server sends the seed to Naver's autocomplete and keeps the words that come back for seven days. The dashboard's own expansion runs in your browser instead. |
| Naver (blog RSS) | The blog id you enter for a title check, a blog diagnosis or a blog search visibility check | Only when you ask for a title check, a blog diagnosis or a blog search visibility check, in the market research screen or through a connected agent. That blog may not be yours. If the extension is connected, your browser reads that blog's public feed (the titles, categories, dates and addresses of its latest posts) and uploads it to our server; if there is no extension or it cannot read the feed, our server reads it directly. The server keeps a summary of the feed for 24 hours. A summary your extension read is used only for you; a summary our server read is public data and is not tied to your account. |
| Naver (API HUB blog search) | The topic you or your agent give when looking for neighbor candidates | Only when you ask for neighbor candidates, through a connected agent or the API. Our server asks Naver's blog search for that topic and returns to you, for each blog it finds, the blog address, the blogger's name, and up to three of its posts on that topic (title, address, date). Those are public posts on other people's blogs. We keep none of the results. |
Cookies and how to refuse them
uplika sets two kinds of cookie. The first keeps you signed in and remembers your language and screen preferences (the AI model you picked, notices you dismissed); the service does not work without it. The second is the Google Analytics cookie described above, which only counts visits.
You can refuse the analytics cookie in your browser settings by blocking cookies from google-analytics.com, or by installing Google's opt-out add-on. Refusing it does not limit anything you can do in uplika.
Google's own policy explains what it does with the data it receives.
What an agent is allowed to do
Connecting an AI agent issues that agent an access token. Before it is issued we show you exactly what it covers (read connected accounts, read publishing history, publish) and nothing is issued until you approve.
The agent never receives the channel's own access token. It asks us, and our server is what talks to the channel.
You can revoke an approval at any time from the MCP screen in the dashboard. That agent's token stops working immediately.
The Naver browser extension (Naver Blog and Naver Clip)
Naver Blog has no official publishing API. To publish there, uplika offers a Chrome extension that runs in your own browser and writes the post through Naver's editor while you are logged in to Naver. The extension does only the channel work you asked uplika for: it puts posts you asked uplika to publish on your Naver Blog, does the things a person does around posts when you ask (replying to a comment, liking, adding a neighbor), and, if you have turned on a comment-reply automation, reads that blog's comment management page every five minutes and reports new comments to uplika. Turn the automation off and it stops reading. If you have turned on a neighbor-post comment automation, it reads that account's neighbor feed every thirty minutes and its neighbor list every six hours, reports mutual neighbors' new posts to uplika, and reads each such post's body so that one AI-written comment, following the instructions you set, can be posted on it. Turn that automation off and it stops reading too. When you ask uplika for your Naver drafts, it reads the blog's draft box (titles and saved times) and loads the draft you picked in the editor to publish it as it is or to delete it. When you ask uplika about one of your own posts (to open it, list your posts, or read its comments or view counts), it reads that post's page. When you ask uplika to edit a post you wrote directly in Naver's editor, it opens that post's edit screen and reads its body, category, visibility and tags, so the edit keeps the parts you did not change. When you or your AI agent ask uplika for neighbor candidates, it reads that account's neighbor list (every neighbor, not only mutual ones) and, in extension versions that support it, the list of mutual-neighbor requests the account has sent. When you or your AI agent ask uplika for your neighbors' new posts, it reads the first three pages of that account's neighbor feed, and then the same neighbor lists it reads for neighbor candidates. Within six hours of a neighbor-list read, uplika uses what it already has instead of reading the lists again.
Naver Clip has no official upload API either, so the same extension does that work too. When you connect Naver Clip, it opens Naver Clip Creators (clipcreators.naver.com) in your browser with the Naver account you chose and reads your clip profile (its profile id, clip id, nickname and picture) and Naver Clip's category list. When you ask uplika to post a clip, it fetches the video you uploaded to uplika, uploads it in Naver Clip Creators, fills in the description, hashtags, category and the labels you chose, presses post (or save as draft), and reads your clip list to confirm the clip is there. It runs only in the Naver Clip Creators window it opened for that job, and it does not create a clip profile for you.
The extension never asks for, reads or stores your Naver password, and it never sends your Naver cookies or login session to uplika or anyone else. Publishing happens inside your browser, using the login you already have there. What the extension sends to uplika is the result of the job: the post's Naver id, its address, and whether the images and tags landed. While a comment-reply automation is on, it also sends what it read from the comment management page: comment id, post id, the writer's id and nickname, the text and the time. Those are public comments on your own blog; uplika uses them to post the reply you configured and to keep the writer as a contact. While a neighbor-post comment automation is on, it also sends what it read from the neighbor feed and the neighbor list (the post owner's blog id and nickname, the post id, its title, address, time and visibility) and, for the post it is about to comment on, that post's body. Those are posts your mutual neighbors shared with their neighbors; uplika uses them to write the comment and to record which posts it commented on. When you ask uplika to publish one of your drafts, it also sends that draft's title, body, tags and category; those are your own drafts, and uplika keeps them as the publish record. What it receives from uplika is the post you asked to publish: title, body, images, category and tags. When you ask for neighbor candidates, it sends what those lists show for each blog: its blog id, and for the neighbor list also the nickname, whether it is a mutual neighbor, its latest post date and the date it was added. uplika keeps only the blog id and whether it is a mutual neighbor, with the connected account, to leave out blogs you are already connected to, and replaces them with the next read. When you ask for your neighbors' new posts, it sends what the neighbor feed shows for each post (the post owner's blog id and nickname, the post id, its title, address, time, visibility and whether comments are open) and the neighbor lists as for neighbor candidates. uplika passes the posts back to you or your agent and does not keep them; the extension job that carried them is cleared on the schedule for Naver extension read jobs below.
When you run keyword research in the uplika dashboard, or your AI agent asks uplika to expand seed keywords for a blog post, the extension looks up Naver's search suggestions for those keywords in the background, from your own internet connection. It sends Naver only the keywords you or your agent gave, attaches no cookies, opens no window or tab, and sends the suggestions back to the uplika page or to uplika for you. It uses the Naver permission described below; if the extension is off or that permission is missing, uplika's server looks them up instead, and if that is off too, your browser asks Naver directly as before.
When you check how Naver search shows a keyword or your blog (the blog diagnosis and AI Briefing check in market research's Naver keyword research, or your connected AI agent), the extension reads Naver's public search result pages for those keywords in the background, from your own internet connection, about three seconds apart. It attaches no cookies and opens no window or tab. It sends uplika only the AI briefing part of each page and the addresses of blog posts in the results, not the rest of the page, and uplika reads which posts were listed from that. It uses the same Naver permission as publishing.
When you diagnose a blog, run a title check or check a blog's search visibility (market research's Naver keyword research, or your connected AI agent), the extension reads the public feed (RSS) of the blog you or your agent named, once, in the background, from your own internet connection. That blog may not be yours. It attaches no cookies, opens no window or tab, and uploads the feed it read to uplika's server as is. uplika takes only the post titles, categories, dates and addresses from it, stores none of the rest, and keeps that summary for 24 hours for you only. If there is no extension or it cannot read the feed, uplika's server reads it directly. It uses the same Naver permission as publishing and asks for nothing more.
Naver keeps only one account signed in at a time. So that each workspace publishes as the right account, the extension keeps your Naver sign-ins in this browser's extension storage and puts the right one back before it publishes. It reads and writes Naver's own cookies, only on this computer, and never sends them anywhere. The extension gets the browser permission this needs when it is installed, so a browser where you sign in to uplika later does not ask again. If you use other channels only, the extension never reads or changes your Naver sign-in or cookies. Removing an account from the connection screen, or removing the extension, deletes the saved sign-ins. Treat them as the same level of protection as the cookies your browser already stores: anyone with access to this computer's browser profile could reach them, so do not connect Naver Blog or Naver Clip on a shared machine.
On this computer the extension keeps a pairing token that ties it to your uplika workspace, the workspace name, and the blog id it found. That is stored in the browser's extension storage and nowhere else. Removing the extension deletes it. You can also disconnect a workspace from the extension's popup, or revoke the pairing from the uplika dashboard, and the extension stops receiving jobs at once.
So that you can tell your browsers apart on the connection screen, the extension tells uplika the blog id of any Naver sign-in kept in this browser that has been signed out. It does not send the sign-in or any cookies. And if you press Allow on the extension's browser name page (Chrome's optional "Know your email address" permission), the extension sends uplika the Google email address signed in to that Chrome profile. uplika shows it as that browser's name on your own connection screen only and uses it for nothing else. If you do not allow it, nothing is sent and the browser is named by number. If you take the permission back in Chrome, the extension says so the next time it connects and uplika deletes the address it kept. Deleting your uplika account deletes it too.
While the extension is paired, uplika stores the blog id, the blog's category list, for Naver Clip the clip profile id, clip id, nickname and Naver Clip's category list, and a record of each job (what was requested, what happened, when; for a clip, its video id and number or its draft number). A post you publish through the extension is publishing history, the same as on every other channel, and stays until you delete your account. Job records differ by kind: records of jobs that only read from Naver, and of publish and update jobs, are deleted or cut down to a summary on the schedule below; records of other jobs (replies, likes, neighbor adds, deletions, clip uploads, clip profile checks) are kept until you delete your account.
YouTube and your Google data
uplika uses YouTube API Services. When you connect a YouTube channel, we reach it through the YouTube Data API, and only on your instruction or that of an agent you authorized.
What we hold is listed in the tables above: the channel's access and refresh tokens, its profile and upload playlist id, the videos you publish through us, the comments on the videos you point us at, and the metrics recorded on the days you look at them. We do not sell it and we do not use it for advertising.
The YouTube search in market research uses YouTube API Services too. It never uses your Google account and reads public video data only. The views-to-subscribers ratio and the Short or long-form label it shows are values uplika calculates from YouTube's numbers. They are not YouTube metrics, and the dashboard marks them as uplika's wherever they appear.
Disconnecting the channel in uplika, or deleting the workspace or your account, deletes the stored tokens and asks Google to end our access, unless the same channel is still connected elsewhere in uplika. Separately from that, you can revoke our access from your Google Account at any time, which cuts us off even if you never open uplika again.
Google Analytics and Google Ads data
You can connect one Google Analytics 4 property to a workspace. This connection reads numbers and publishes nothing. It may not be open on your account yet.
What we read: the list of GA4 properties your Google account can view, so that you can pick one, and the reports, realtime figures and dimension and metric names of the property you picked. We read them only on your instruction or that of an agent you authorized. We ask Google for read-only access to Analytics, plus your Google account id, and we change nothing in Google Analytics.
What we store: the access and refresh tokens, encrypted; the property's id and name, the name of the account it sits in, its time zone and currency; and your Google account id (sub). We keep them until you disconnect, or delete the workspace or your account.
What we do not store: the report, realtime and list responses. They are never written to our database. To avoid asking Google the same question twice, a report stays in the server's memory for up to 10 minutes and a list of dimension and metric names for up to 1 hour. Realtime figures are not held at all. Request logs keep the status and the request for 7 days, not the response. While you are picking a property, the tokens are held encrypted and the list of properties (their ids and names) is held unencrypted. Both expire after 30 minutes and are removed within 3 hours.
You can also connect one Google Ads account to a workspace. Unlike the Analytics connection, this one can change things in that account, on your instruction or that of an agent you authorized. It may not be open on your account yet.
What we read from Google Ads: the list of accounts your Google account can open, so that you can pick one; the campaigns, ad groups, ads, keywords, negative keywords, location targeting, bidding strategy and maximum cost per click, ad text and ad assets of the account you picked; their dates, languages, ad schedule, device and network settings, audiences, topics, placements and Performance Max signals; the sitelinks, callouts, structured snippets and call numbers on its campaigns, with Google's review status; a campaign's target cost per conversion and target return on ad spend; the names, size ranges and status of the account's customer lists and custom audiences, so that you or your agent can find one to target (never the people on a list, which Google does not give out); the names, categories, status and last 30 days of conversions of the account's conversion actions (before a Performance Max campaign is created or a campaign moves to bidding for conversions, and when you or your agent ask about the account); the tags of conversion actions you or your agent create; and the metrics for the periods you or your agent ask about. We ask Google for the adwords permission, which covers your whole Google Ads account, plus your Google account id.
What we write to Google Ads: only what you or your agent instruct. That is creating Search, Demand Gen, Display and Performance Max campaigns; adding ad groups (including Display and Demand Gen ad groups), keywords, ads and Performance Max asset groups; creating custom audiences from the words and sites you give; changing names, countries, the maximum cost per click, ad text, keywords, negative keywords and ad assets; changing a campaign's start and end dates, languages, ad schedule, device exclusions, search partners and Display Network; changing an ad group's audience, topic and placement targeting and a Performance Max asset group's audience signal and search themes; adding, changing and removing a campaign's sitelinks, callouts, structured snippets and call number with the text, links and number you give; changing a campaign's bid strategy and target; creating website conversion actions (we do not put the tag on your site); turning campaigns, ad groups and ads on or off; changing a campaign's daily budget; and removing campaigns, ad groups, ads, keywords and asset groups. Google cannot undo a removal. A new campaign is always created paused. Turning ads on and raising a budget work only within a daily budget cap that you set yourself. Google bills your ad spend to your Google Ads account.
When you or your agent use images or YouTube videos in an ad, we send Google the images you chose from your uplika media and the ids of the YouTube videos you named, so that Google can show them as ad assets. Google keeps them in your Google Ads account under your agreement with Google.
What we store for Google Ads: the access and refresh tokens, encrypted; the account's id and name, its currency and time zone, whether it is a test account, the manager account it is reached through, your daily budget cap, and which version of the list of what uplika does in Google Ads you accepted; your Google account id (sub); and a record of what uplika created, changed or removed, meaning each object's name, status and daily budget, and each change with what it changed, its before and after values, who made it and through what. Metrics are not written to our database. Request logs keep the status and the request for 7 days, not the response. While you are picking an account, the tokens are held encrypted and the list of accounts (ids, names, currency, time zone, manager account) is held unencrypted. Both expire after 30 minutes and are removed within 3 hours.
When you disconnect Google Ads, we delete the tokens and keep that record. Disconnecting does not stop ads: ads that are on keep running in Google and keep spending until you turn them off. When you delete the workspace or your account, we delete the record too.
We do not sell this data, do not use it for our own advertising, and do not mix it with another customer's responses. uplika's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
Disconnecting in uplika deletes the stored tokens and asks Google to end our access, unless the same Google account is still connected elsewhere in uplika. Separately from that, you can revoke our access from your Google Account at any time.
Meta Ads data
You can connect one Meta ad account to a workspace through Facebook Login for Business. A connection only reads unless you also allow management, which lets uplika change things in that ad account on your instruction or that of an agent you authorized. It may not be open on your account yet.
What we read: the ad accounts you shared with uplika in Meta's login dialog, so that you can pick one; the name, currency, time zone, status, amount spent and spend cap of the account you picked; its campaigns with their status and budget; and its metrics (impressions, clicks, spend, reach and conversions) for the periods you or your agent ask about. With management allowed, we also read the account's ad sets and ads, to find the level a status or budget change applies to and to see their current name, schedule, targeting and creative before changing them; the objective and special ad categories of a campaign you add to; the Facebook Pages and Instagram accounts you shared, and the ad account's default EU beneficiary and payer when an ad set reaches the EU; and whether a post you choose can be promoted. When you or your agent look up targeting, we read the interests, places and languages Meta matches, the names of the ad account's custom audiences, and Meta's estimate of how many people the targeting reaches, and pass them on without storing them. For the pixels the ad account can use, we read their name, the time of their last event, whether Meta marks them unavailable and the business that owns them, and the number of events each pixel received per day and per event name, web and server apart, which we keep (see below). For the last 7 days, you or your agent can also ask for a pixel's counts grouped by page address, device, browser and similar groupings, as Meta reports them, and we pass them on without storing them. When you or your agent ask for conversions by type, we also read the names of the ad account's custom conversions. Except that uplika reads the pixel list and the daily pixel counts once a day on its own, for every connected Meta ad account, we read all this only on your instruction or that of an agent you authorized. A connection that only reads asks Meta for the ads_read permission alone, and through it we create, change, pause or delete nothing in your ad account.
What we change when you allow management: only what you or your agent instruct. That is turning campaigns, ad sets and ads on or off; changing the daily budget of a campaign or ad set; creating campaigns, ad sets, ad creatives and ads, including an ad from a post published through uplika on a Facebook Page or Instagram account you shared with us; changing the names and schedules of campaigns and ad sets, the targeting of ad sets and the creative of ads; and deleting campaigns, ad sets and ads. A deletion cannot be undone in Meta, and deleting a campaign or ad set deletes everything under it. To make an ad creative from your uplika media, uplika uploads the images to Meta, and for a video gives Meta the file's address so that Meta fetches the video from it. For this we also ask Meta for the ads_management permission, and for pages_show_list, pages_read_engagement and instagram_basic so that we can see the Pages and Instagram accounts you shared. Every ad uplika creates starts paused. uplika never turns an ad on by itself, turns ads on or raises a budget only within a daily budget cap you set yourself, and does not change your spending limits or payment methods. If creating fails partway, uplika tries to delete the paused campaign it had just created, or the ad set it had just added to an existing campaign, and records what could not be deleted. Ad creatives and the images and videos uploaded for them stay in the ad account, and so does an ad's old creative after it is changed. They cannot run or spend by themselves. Meta bills your ad spend to your ad account.
What we store: the access token, encrypted; the ad account's id and name, its currency, time zone and status; the id of the business it is shared from; whether it is a test account; and the permissions you granted. We keep them until you disconnect, or delete the workspace or your account. With management allowed, we also store your daily budget cap and a record of what uplika created, changed or deleted, meaning each object's name, status and daily budget, and each change with its before and after values (such as a name, schedule, targeting, or the creative and the media or post it uses), who made it and through what.
What we store about the pixels of the ad account you connected: for each pixel, the number of events it received per day, per event name (for example PageView), web and server apart. These are counts only. Meta does not give uplika individual events, and uplika receives no visitor, contact or purchase detail from them. We keep the daily counts for 400 days, then delete them, or at once when you disconnect the ad account or delete the workspace or your account.
What we do not store: the metrics and campaign lists Meta returns. They are not written to our database, except the daily pixel counts above; only the objects uplika created, changed or deleted go into the record above. To avoid asking Meta the same question again, a response stays in the server's memory for up to 15 minutes, and the pixel list and the names of custom conversions for up to 30 minutes. If Meta turns requests away for a while, the last response is kept there for up to 24 hours so the dashboard can still show it, marked as not current. Request logs keep the status and the request for 7 days, not the response. While you are picking an ad account, the token is held encrypted and the list of ad accounts (ids, names, currency, time zone, status) is held unencrypted. Both expire after 30 minutes and are removed within 3 hours.
We do not sell this data, do not use it for our own advertising, and do not mix it with another customer's data.
Disconnecting in uplika deletes the stored token and keeps the record of what uplika created, changed or deleted. Disconnecting does not stop ads: ads that are on keep running and keep spending until you turn them off. When you delete the workspace or your account, we delete the record too. To end the permission on Meta's side as well, remove uplika in Meta Business Settings under Integrations, Connected apps. That cuts us off even if you never open uplika again.
TikTok
When you connect a TikTok account, uplika signs you in through TikTok Login Kit and posts through the TikTok Content Posting API, only on your instruction or that of an agent you authorized.
From TikTok we receive and keep the account's id, display name, username and profile picture, and its access and refresh tokens, sealed as described below. We keep the videos and photos you publish through us, the settings you chose for each post (who can see it, whether comments, Duet and Stitch are allowed, and any commercial content disclosure) and the post id TikTok returns. Before each post we ask TikTok what the account can post right now (its visibility options, interaction settings and maximum video length) and show that to you; we do not keep that answer. When you ask for a post's numbers, we read its public view, like, comment and share counts. We do not sell any of it and we do not use it for advertising.
We never post without your instruction, and we never add watermarks, logos or promotional text to your content. Disconnecting the account in uplika deletes the stored tokens. You can also remove uplika's access from the TikTok app at any time.
When you connect a Pinterest account, uplika signs you in through Pinterest and asks only to read your account and boards and to create, read and delete Pins. Pinterest requires its board write permission for creating and deleting a Pin; uplika never creates, renames or deletes your boards. It acts only on your instruction or that of an agent you authorized.
From Pinterest we receive and keep the account's id, username, business name and profile picture, the list of your boards (each board's id, name and whether it is public or secret) and the default board you choose, and the access and refresh tokens, sealed as described below. We keep the images and videos you publish through us, the Pin's title, description, link, alt text and board, and the Pin id Pinterest returns. When you ask for a Pin's numbers, we read its impressions, reactions, comments and saves. We do not sell any of it and we do not use it for advertising.
We never create a Pin without your instruction. Disconnecting the account in uplika deletes the stored tokens. Pinterest does not let apps revoke a person's sign-in themselves, so uplika stays on your list of allowed apps until you remove it in Pinterest Settings, under Security.
X
When you connect an X account, uplika signs you in through X and asks only to read your account and posts, to create and delete posts, to upload media, and to stay connected without asking you to sign in again. It acts only on your instruction or that of an agent you authorized.
From X we receive and keep the account's user id, username, name and profile picture, and its access and refresh tokens, sealed as described below. We keep the posts and media you publish through us and the id X returns for each post uplika creates. We read a post's views, likes, replies, reposts and quotes only after you switch metrics on for that X connection. We do not sell any of it and we do not use it for advertising.
Posting to X through uplika is paid for with X credits that you buy in advance (see the Terms of Service). We keep your X credit balance and a ledger with an entry for each top-up, refund and credit grant, and for each X call made for you, including the account lookup when you connect, which uplika pays for itself. An entry records the amount, the kind of entry or call, the workspace, X account and post it was for, and the payment order. Deleting your uplika account deletes the balance. The ledger entries and the payment order stay as payment records. Your user id is removed from the ledger entries, and the payment order keeps an internal id that no longer leads to any account.
We never post without your instruction. Disconnecting the account in uplika, or deleting the workspace or your account, deletes the stored tokens and asks X to revoke them, unless the same X account is still connected elsewhere in uplika. Removing uplika under Connected apps in your X settings disconnects it on X's side too.
Deleting your account does not end your right to a refund of unused X credits. Within 180 days of the payment date, ask by writing to support@uplika.com from the address you signed up with.
When you connect a LinkedIn profile, uplika signs you in through LinkedIn and asks only for your basic profile (sign-in, name and photo) and for permission to create, edit and delete posts for you. It acts only on your instruction or that of an agent you authorized. uplika connects personal profiles only. It does not ask for your email address, your connections, your messages or company pages.
From LinkedIn we receive and keep your member id, your name and profile photo, and the access token, sealed as described below. LinkedIn does not give uplika a refresh token, so the connection ends after about 60 days and you connect again. We keep the text, images and videos you publish through us, the visibility and link card you choose, and the post id LinkedIn returns. uplika does not read your feed, other people's posts, comments, reactions or post numbers from LinkedIn. We do not sell any of it and we do not use it for advertising.
We never post without your instruction. Disconnecting the profile in uplika deletes the stored token right away and the connection record 30 days later. Records of posts already published, with the name shown on them, stay in your uplika post history. uplika stays on your list of permitted services until you remove it on LinkedIn under Settings & Privacy, Data privacy, Permitted Services.
Connecting through a link someone sent you
An uplika user can send a connection link to someone who has no uplika account, such as a client, so that person connects their own channel account to the sender's workspace from their own device. For most channels, the person who opens the link signs in on the channel's own screen, and uplika never sees their channel password.
Some channels connect with an app password, a bot token or an API key instead of a sign-in screen. For those, the person enters it on the link page. It goes only to uplika, is kept sealed like any channel token, and is never shown again to anyone, including the person who sent the link. Where a channel asks the person to pick a page or board after signing in, the list to pick from is shown only on the link page, not to the sender.
uplika does not ask the person who opens the link to sign up and does not collect their name, email address or other sign-up details. What uplika receives is what any channel connection gives, as described above for connected social accounts: the channel's access token, kept sealed, and the account's public profile.
Before anything is connected, the link page shows who sent the link and which workspace the account will join. Once connected, the account belongs to that workspace, and the user who created the link publishes with it and reads its replies and metrics as with any account they connect themselves.
A link can also connect an analytics or ad account, such as a Google Analytics property, a Google Ads account or a Meta ad account. The person signs in on Google's or Meta's own screen and picks the property or ad account on the link page; the list to pick from is shown only on the link page, not to the sender. Before anything is connected, the link page states what the sender's workspace can do with it. What uplika receives, stores and does with it is the same as for those connections described above, and the connection is made with read access only for Meta ad accounts.
uplika keeps only a hash of the link, not the link itself. A link stops working when it expires or when its sender cancels it. Cancelling a link does not disconnect accounts already connected through it.
To take an account back, ask the sender to disconnect it, or remove uplika's access in the channel's own settings for connected apps. Either way uplika can no longer act on the account, and its records follow the retention table below.
How we protect your data
Everything moves over TLS. uplika.com and api.uplika.com are served over HTTPS only, and requests to the API pass through Cloudflare before they reach the origin server.
Channel access and refresh tokens, including the Google and YouTube tokens described above, are sealed with AES-256-GCM before they are written to the database. Each record carries its own initialization vector and an authentication tag, so a tampered value fails on read instead of passing silently. The key lives in the server's environment and never in the database, so a copy of the database on its own does not yield a usable token.
Anything we never need to read back is stored as a hash rather than as text: your password, your API keys, and the tokens we issue to agents you connect. An API key's plaintext is shown once, at creation, and cannot be retrieved afterwards.
The database is not reachable from the internet. Only the application server connects to it, and administrative access to that server is by SSH key, with password login disabled. Access to production data is limited to the operator named above.
No security measure is absolute. If a breach ever affects your personal data, we notify you and the relevant authority as the law requires.
How long we keep things
| What | How long |
|---|---|
| Account, sessions, workspace, identity records, channel connections, publishing history | Deleted the moment you delete your account |
| Profile of a channel you disconnected (username, display name, profile image URL, account id) | Deleted automatically 30 days after you disconnect, or the moment you delete your account. Access tokens are destroyed when you disconnect. Reconnecting the same account to the same workspace within 30 days picks it up again |
| Automations, contacts, conversations and messages of a channel you disconnected | Deleted automatically 30 days after you disconnect, or the moment you delete your account. Reconnecting the same account to the same workspace within 30 days picks them up again |
| Copy of the account deletion confirmation email (your email address and the deletion time) | Kept in our support mailbox as the record that the deletion happened, like support messages |
| Images and videos attached to a post | Deleted automatically 24 hours after the post settles |
| Uploads never attached to a post | Deleted automatically after 48 hours |
| Images attached to a support message | Deleted automatically after 90 days |
| Posts you deleted from the channel, and the metrics recorded for them | Kept until you delete your account. Deleting a post removes it from the channel, not from your history |
| Request logs | Deleted automatically after 7 days |
| Sign-ups that never finished verification | Deleted automatically after 24 hours |
| Keyword research records | Kept until you delete your account, then deleted immediately |
| YouTube search history | Deleted automatically within 30 days, or at once when you delete your account |
| Google Analytics connection: tokens, property details, Google account id | Until you disconnect, or delete the workspace or your account |
| Google Ads connection: tokens, account details, daily budget cap, Google account id | Until you disconnect, or delete the workspace or your account |
| Record of what uplika created, changed or removed in Google Ads | Kept after you disconnect. Deleted when you delete the workspace or your account |
| Meta Ads connection: token, ad account details, business id, granted permissions, daily budget cap | Until you disconnect, or delete the workspace or your account |
| Record of what uplika created, changed or deleted in Meta Ads | Kept after you disconnect. Deleted when you delete the workspace or your account |
| Meta Ads metrics and campaign lists | Never written to our database. In server memory up to 15 minutes, or up to 24 hours as the last response shown while Meta turns requests away |
| Google Analytics reports and lists | Never written to our database. In server memory: reports up to 10 minutes, lists of dimension and metric names up to 1 hour, realtime figures not at all |
| GA4 properties to pick from while connecting (ids and names) | Not encrypted, expires after 30 minutes, removed within 3 hours |
| Google Ads accounts to pick from while connecting (ids, names, currency, time zone, manager account) | Not encrypted, expires after 30 minutes, removed within 3 hours |
| Meta ad accounts to pick from while connecting (ids, names, currency, time zone, status) | Not encrypted, expires after 30 minutes, removed within 3 hours |
| Naver search check records | Checks and changes kept up to 400 days, the record of each check run 7 days, or deleted at once when you delete your account |
| Public statistics caches (the title check's title summary 24 hours, keyword autocomplete 7 days, keyword measurement history 400 days, YouTube search results 2 days, Google keyword results 8 days) | Not tied to any account; purged on that schedule |
| Blog feed summaries your extension read (blog diagnosis, title check, blog search visibility check) | Used only for the person who asked; deleted automatically after 24 hours |
| Neighbor lists read for neighbor candidates or neighbors' new posts (blog ids and whether each is a mutual neighbor) | Kept with that connected account and replaced by the next read; deleted when you disconnect the account or delete your account |
| Naver extension read jobs (jobs that only read from Naver: a post, a post list, comments, drafts, neighbors, autocomplete, a search page, a blog feed, metrics, categories) | Contents cleared 3 days after the job's deadline, and the record deleted automatically after 8. The deadline is usually a few minutes after the request and never more than 7 days |
| Naver extension publish and update jobs (including the source read in order to edit a post) | 30 days after the job ends only a summary stays (post number, visibility, result and failure reason, image count check, times); the post content sent with the job and its progress log are deleted. The summary is kept until you delete your account. The published post itself stays in your publishing history until then |
| Database backups (a copy of the database that holds the records above; attached files are not in it) | Daily backups are deleted automatically after 30 days, and the first backup of each month after 90 days. They are kept in our backup storage (Backblaze B2); once a backup is confirmed there, we delete the copy on the server. Deleting your account removes your data from the service at once; the copies inside backups already made go when those backups expire |
| Analytics data at Google | 14 months. The _ga cookie itself expires after 2 years |
Where Korean law requires a longer retention period, we follow it: contract and withdrawal records for 5 years, payment records for 5 years, and consumer complaint and dispute records for 3 years. Subscription plans are not charged during the beta, so these records exist only for X credit purchases and refunds.
Your rights
You can ask to see, correct, delete or restrict processing of your data at any time. You can delete your account yourself from the dashboard settings, and if you cannot sign in, follow the steps on the data deletion page.
Children
uplika is not intended for children under 14. We do not knowingly collect their data, and we delete an account as soon as we find one.
Data protection officer
| Item | Detail |
|---|---|
| Officer | ํ๋ฏธ์ |
| support@uplika.com | |
| Phone | 010-8230-5513 |
Write to us about anything concerning your personal data and we answer without delay.
Changes
If this policy changes we announce it inside the service. Last updated 2026-11-20.