Menu
FeaturesHow it worksPricingAboutBlogContact
Join the waitlist

Privacy Policy

Last updated: 2 October 2026

Okashare is a publishing and advertising console. You connect social media and ad accounts you own; Okashare publishes the posts you approve, shows you how your posts and ads perform, and makes the ad changes you confirm. Okashare is operated by The Livingstone Solution LLC in the United States ("we"). This policy explains what Okashare stores and why, how it is protected, how long it is kept, and how to have it deleted. It applies to oka-share.com and the Okashare service.

1. What we collect

  • Your login. Your email address, your name if you give it, a hash of your password (never the password itself), and the browser each session was signed in from.
  • The waitlist. If you join it: your email address, the page you joined from, the site that referred you (its address only, such as google.com) and any campaign tags in the link you followed. If you fill in the optional second step, also your name, company or channel, what describes you (as many as fit), the platforms you post on, how many accounts you run, and your mobile number with whether, and when, you agreed to receive texts.
  • Visits to oka-share.com. For each page viewed on the public site: the page, the referring site's address (not the full link), campaign tags in the link, the device type, browser and operating system, and the time zone your browser reports. There is no cookie and we never store your IP address; your IP address and browser details are combined with a random value that changes every day and is deleted after two days, which lets us count how many different people visited on a day without being able to recognise anyone, or the same person on another day. Nothing is sent when your browser asks not to be tracked (Global Privacy Control or Do Not Track), and nothing is recorded while you are signed in.
  • Connected social accounts. For each Instagram, TikTok or YouTube account you connect: the account ID, username and display name the platform returns, and the access and refresh tokens it issues. For Instagram, Okashare reads the Facebook Pages you chose to share only to find the Instagram account linked to each one; it does not keep them.
  • What Okashare reads from those accounts. Your accounts' posts and their numbers (likes, comments, views, reach, shares and saves), the follower and reach history, and the numbers for the posts Okashare published. If you use the comment inbox, also the comments on your posts, with each commenter's username, and the replies you write or approve.
  • Your posts. The caption, the media you upload, the settings you chose (for TikTok: the audience, the interaction settings and the commercial content disclosure), who approved the post and when, and the status and links the platform returns.
  • Connected ad accounts. For each ad account you connect, such as a Meta ad account: its ID, name, currency and time zone; its campaigns (name, objective, status and budget); their results (spend, impressions, clicks and conversions); the access token; and the changes you propose and confirm.
  • Diagnostics. The server's access logs (IP address, time and the address requested), rate-limit counters kept by IP address, and a record of each request made to your workspace's API: the route, the result and the key used, without your IP address.

2. How we use it

Only to run the service for you: publishing and scheduling the posts you create, keeping your connections alive, reading the numbers for your accounts, posts and campaigns, showing them to you with alerts when something looks wrong, posting the comment replies you approve, and carrying out the ad changes you confirm.

The waitlist is used to send you your invite and news about the launch, by email, and by text only if you agreed to receive texts; the optional details help us decide who to invite first. Visit counts and waitlist sources are used only as totals, to see which pages and which sites bring people to Okashare.

Nothing changes on your accounts unless someone in your workspace asked for it. A post is published only after a person created and approved it, or scheduled it through a rule they set up. A reply is posted only after a person approved it. A campaign is paused, resumed, given a new daily budget or created (always paused) only after a person confirmed that exact change.

We do not sell personal data. We do not use your content, audience data or ad data for our own advertising or to target anyone, and we do not use it to train AI models. Before a post is published, its text and media may be checked by a service provider acting for us, which receives them only for that check. If we add AI-written reply drafts, we will update this policy before turning them on. A workspace's data is shown only to that workspace and, for a client workspace, to the agency workspace that manages it.

3. Where it lives and how it is protected

Okashare runs on a server hosted by Hostinger in the United States, keeps its database with Amazon Web Services in the United States, and stores uploaded media and encrypted backups with Cloudflare. They process data only to run Okashare, under our instructions.

Access tokens are encrypted at rest (AES-256-GCM) in a database only the application can reach. Uploaded media is stored at an unguessable public address, because the platforms fetch it from there to publish it. The database is backed up every night, and each backup is encrypted before it is stored. All traffic uses HTTPS. Sessions are cookie-based and expire.

4. Platform data

Data received from Meta (Instagram and Meta ads), TikTok and Google (YouTube and Google Ads) is used only for the features you use, under each platform's developer terms. Okashare's use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

Okashare uses YouTube API Services. When you connect a YouTube channel, Okashare uses them to upload the videos you approve, to read your channel's and videos' statistics, and, if you use the comment inbox, to read the comments on your videos and, once you allow replying, post the replies you approve. What Okashare reads from YouTube is refreshed or deleted within 30 days. If you remove Okashare's access in your Google Account, Okashare deletes what it stored from your channel within 7 days. Google's own handling of your information is described in the Google Privacy Policy. You can remove Okashare's access to your YouTube account at any time, either in Okashare (Accounts, then Disconnect, which also deletes what Okashare stored, as described in section 6) or in your Google Account's security settings.

Okashare never posts, comments, follows or messages on your behalf except to publish the posts and replies you approved, and never changes an ad account except to carry out a change you confirmed.

5. Who else sees it

The platforms you connect, when you publish to them or change your ads. The service providers named above, who process data on our behalf. In an agency workspace, the agency sees the client workspaces it manages. No one else, unless the law requires it.

If a public authority asks us for personal data, we check that the request is lawful before answering, disclose only the minimum the request requires, and keep a record of the request and of our response.

6. Keeping and deleting your data

You can remove your data yourself at any time, or ask us to.

  • Disconnect a social account (Accounts, then Disconnect on the account). Okashare deletes its tokens at once, together with everything it read from the account: its posts and their numbers, the follower and reach history, the comments and reply drafts, and the numbers for posts Okashare published. TikTok and YouTube are also asked to revoke Okashare's access. For Instagram, remove Okashare from Meta as well in Facebook Settings, Business integrations. Okashare keeps only the account's ID and username on the posts it already published, so your history stays readable, until you delete the workspace.
  • Disconnect an ad account (Ads, then Accounts, then Disconnect). For a Meta ad account, Okashare asks Meta to remove its ads permissions. Okashare deletes the token and the campaigns and results it synced. The record of requests described below, which includes the changes you confirmed, stays until it expires.
  • Delete a workspace (the workspace menu, then Delete workspace; owners only). Everything stored for the workspace is deleted, including the media files you uploaded. A workspace that manages client workspaces must delete those first.
  • Delete your Okashare account. Email oliyaddinku.od@gmail.com from the address you signed up with, with the subject "Delete my Okashare account". We confirm by reply and delete everything within 30 days. Copies in our encrypted backups and in our database provider's short-term recovery history expire within 30 days after that.
  • A single uploaded file stays in your workspace's media library until you delete the workspace; to remove one sooner, email us. The waitlist: email us to be removed, and everything you gave us with it is deleted. To stop texts, reply STOP to any of them.
  • Posts already published on a platform stay on that platform; delete them there.

How long the rest is kept:

  • Server access logs: up to 90 days.
  • Rate-limit counters (IP addresses): 2 days.
  • The record of requests to your workspace's API, shown under Developer, Audit log: 13 months.
  • Sessions: deleted 30 days after they expire or you sign out.
  • Page views on oka-share.com: 13 months. The daily random value behind the visitor count: 2 days.
  • The waitlist: until you ask to be removed.
  • YouTube videos and comments Okashare read: 30 days unless refreshed. YouTube statistics: deleted once your channel's access has not been confirmed for 30 days.
  • Encrypted backups: up to 30 days, then deleted. Anything you delete leaves the backups within those 30 days.
  • Everything else: until you disconnect the account, delete the workspace, or ask us to delete it.

7. Your rights

You can ask for a copy of your data or its correction, ask us to delete it, or object to how we use it, by emailing oliyaddinku.od@gmail.com. We answer within 30 days.

8. Cookies

Okashare sets one cookie: the session that keeps you signed in. There are no advertising or tracking cookies on the site or in the console. While a tab is open, the public site remembers in that tab (session storage, cleared when the tab closes) the site and campaign link you arrived from, so that joining the waitlist a few pages later still records where you came from.

9. Children

Okashare is a business tool and is not meant for anyone under 16.

10. Changes

If this policy changes, the date at the top changes with it, and material changes are announced in the console.

11. Contact

The Livingstone Solution LLC operates Okashare. Questions about this policy or your data: oliyaddinku.od@gmail.com. See also the Terms of Service.