Privacy Policy · Cloutware

This policy takes effect on 13 November 2026. You agree to it, together with the Terms of Service, by ticking the box on the sign-up form before you can use any feature of Cloutware.

Who is responsible for your data

Cloutware is run by Cloutware LLC, a Wyoming limited liability company (Wyoming filing ID 2025-001627371). Cloutware LLC is the controller of your personal data under the EU and UK General Data Protection Regulation (GDPR).

Address: 30 North Gould Street, Suite R, Sheridan, WY 82801, United States
Email for privacy questions, requests and complaints: support@cloutware.io
Phone: +1 805 225 6604

You must be 18 or older to use Cloutware.

The short version

Cloutware does not sell personal data and does not use it for advertising.
Cloutware does not use any platform data or Google user data to train AI models, its own or anyone else's.
Cloutware sets one cookie, the sign-in session cookie. It uses no advertising cookies, no analytics cookies and no third-party trackers.
No third party serves content or advertisements in Cloutware.
Platform access tokens are encrypted at rest and are never shown to you or returned through Cloutware's API.
Cloutware posts only when you act, at a time you scheduled, or through a trigger you turned on.
You can delete your account at any time. Everything listed in this policy is deleted within 7 calendar days, apart from the short list of records in How long data is kept.
Cloutware uses YouTube API Services. The YouTube section below explains what that means for you.

What Cloutware collects

Your Cloutware account

Your email address, your name, and whether you have verified your email address.
Your password. The sign-in library stores it only as a salted hash. Nobody at Cloutware can read your password.
Your role (user or admin).
The date, time and version of the Terms of Service and Privacy Policy you accepted.

Sign-in sessions

When you sign in, Cloutware creates a session and records its token, your IP address, your browser's user agent and the expiry time. A session lasts 60 days and extends each time you use Cloutware. Signing out ends it.

Connected social accounts

For each account you connect, Cloutware stores:

The platform's id for the account, its display name, username and avatar URL.
The scopes or permissions you granted.
The credential that lets Cloutware post for you: an OAuth access token and refresh token, or, on platforms that use them, an app password, bot token, webhook URL or API key. Also the times these expire.
Settings for that connection, such as the address of your Mastodon server.

Credentials are encrypted at rest with AES-256-GCM. They are never shown back to you and never returned through Cloutware's API.

Content you create

Post text, the time you schedule it for, and per-platform options such as privacy level, title, made-for-kids setting and disclosures.
Media files you upload. They are stored in Cloudflare R2 and served from a separate media domain through links that cannot be guessed, so each platform can fetch them. Every file is deleted 7 days after upload or 48 hours after the last delivery to a platform, whichever comes first.
The result from each platform: its id for the post, the post URL, the status, and any error code.

The cross-post trigger (optional)

If you turn it on, Cloutware reads your own most recent post on Instagram, a Facebook Page or Threads through that platform's official API, so you can send it to your other connected accounts. Cloutware never posts to TikTok, YouTube or Pinterest from a trigger unless you confirm that specific post. The trigger stays off until you turn it on, and you can turn it off at any time.

Abuse prevention

One-way hashes of post text and media, used to block identical content being sent to many unrelated accounts. A hash cannot be turned back into your text or media.
Counters per connected account that pace how many posts are published per hour and per day.
An audit log of who scheduled or published what, when, to which account, and from which IP address.

Developer API and webhooks

API keys you create. Each key is shown to you once and then stored only as a hash. A key can post only to accounts its owner connected.
The webhook URLs you configure. Cloutware sends post status events to those URLs and nowhere else.

Email

Cloutware sends email through Resend: address verification, password reset, reminders to reconnect an account, and notices about the service. Cloutware sends marketing email only if you opt in. If you email support@cloutware.io, Cloutware keeps your message to answer it.

How Cloutware uses your data, and the legal basis

Cloutware uses your data only for the purposes below. The last column gives the legal basis under the GDPR.

Purpose	Data used	Legal basis
Create and run your account, sign you in, keep you signed in	Account details, password hash, sessions	Performance of the contract with you (Article 6(1)(b))
Connect your social accounts and publish what you ask, when you ask	Connected account details, credentials, posts, media, per-platform results	Performance of the contract (Article 6(1)(b))
Read your latest Instagram, Facebook Page or Threads post for the cross-post trigger	That post's id, text, media and link	Performance of the contract, for a feature you turned on (Article 6(1)(b))
Send account and service email	Email address, name	Performance of the contract (Article 6(1)(b))
Send marketing email	Email address, name	Your consent, which you can withdraw at any time (Article 6(1)(a))
Prevent spam and abuse, pace posting, keep accounts and platforms safe, find and fix errors	Content hashes, pacing counters, audit log, IP address, user agent, error reports	Legitimate interests (Article 6(1)(f)): keeping Cloutware secure, stopping spam, and meeting the rules of the platforms you post to
Meet legal duties: copyright notices, reports of child sexual abuse material, valid legal process	Only the data the duty covers	Legal obligation (Article 6(1)(c))

Cloutware does not use your data for any other purpose. In particular, it does not build advertising profiles, does not sell or rent data, and does not use platform data or Google user data to train AI models.

Connected platforms: rules that apply to all of them

Cloutware asks each platform only for the permissions listed below for that platform.
Cloutware uses platform data only to show you which account is connected, to publish what you ask, and to show you the result.
Cloutware posts only on your explicit action, at a time you scheduled, or through a trigger you set.
Cloutware adds no branding, watermark, logo or promotional text to your content.
You can disconnect any account in the dashboard. Cloutware then calls the platform's revoke endpoint where one exists, deletes the credential at once, and deletes the rest of the cached platform data within 7 calendar days.
If a platform refuses to refresh a token, Cloutware treats that as a disconnect and deletes the data in the same way.
Disconnecting or deleting data in Cloutware does not delete posts already published on a platform. Delete those on the platform itself.

All platform data is stored in Cloutware's database in the United States. Platform names are trademarks of their owners. Cloutware is independent and is not endorsed by any of them.

YouTube and Google user data

Cloutware uses YouTube API Services. When you connect a YouTube channel, your use of Cloutware's YouTube features is also covered by the YouTube Terms of Service at https://www.youtube.com/t/terms and the Google Privacy Policy at http://www.google.com/policies/privacy.

Permissions Cloutware asks for: youtube.upload (upload videos to your channel) and youtube.readonly (read your channel's name and the processing status of videos you uploaded through Cloutware).
Data obtained: Your channel id, channel name, handle and avatar URL; OAuth access and refresh tokens and their expiry times; for each video you upload through Cloutware, its video id, URL, upload and processing status, and any error YouTube returns.
Purpose: To show which channel is connected, to upload the videos you choose with the title, description, privacy setting and made-for-kids setting you choose, at the time you choose, and to show you whether each upload succeeded.
Storage: In Cloutware's database (Neon, in the AWS us-east-1 region of the United States). Secrets are encrypted with AES-256-GCM.
Retention: Cloutware refreshes or deletes stored YouTube data at least every 30 days. It deletes all YouTube data within 7 calendar days after you disconnect the channel in Cloutware or ask for deletion, and within 30 days after you revoke access on Google's side.
Sharing: Sent only to YouTube, and processed by the service providers listed in this policy so Cloutware can run. Never sold, never transferred to advertising platforms, data brokers or information resellers, never used for advertising, never used to train AI models.
Revoke: Disconnect the channel in the Cloutware dashboard: Cloutware revokes the token with Google at once. You can also revoke Cloutware's access via the Google security settings page at https://security.google.com/settings/security/permissions.

Limited Use

Cloutware's use of information received from Google APIs will adhere to Google API Services User Data Policy, including the Limited Use requirements.

In practice this means:

Cloutware uses Google user data only to provide the upload and status features you see in the dashboard and the API.
Cloutware does not sell Google user data and does not transfer it to advertising platforms, data brokers or information resellers.
Cloutware does not use Google user data for serving ads, including retargeting, personalised or interest-based advertising.
Cloutware does not use Google user data to determine credit-worthiness or for lending.
Cloutware does not use Google user data to train or improve AI or machine learning models.
People at Cloutware do not read your Google user data unless you ask them to in a support request, it is necessary for security (for example, investigating abuse or a bug), or the law requires it.
If Cloutware ever wants to use Google user data in a new way, it will tell you and ask you to accept an updated privacy policy first.

In addition to deleting data through Cloutware, you can revoke Cloutware's access to your data at any time via the Google security settings page at https://security.google.com/settings/security/permissions. Deleting data stored by Cloutware does not affect data stored by YouTube. To delete a video from YouTube, use YouTube itself.

Questions or complaints about how Cloutware handles YouTube or Google user data go to support@cloutware.io.

Instagram, Facebook Pages and Threads

These three platforms are run by Meta. This section explains what Platform Data from Meta Cloutware processes, how, why, and how you can ask for it to be deleted. Cloutware reads your own posts only if you turn on the cross-post trigger.

Instagram

Permissions: instagram_business_basic and instagram_business_content_publish.
Data obtained: Your Instagram professional account id, username, name, profile picture URL and account type; access tokens and their expiry; for each post published through Cloutware, its media id, permalink and status. If you turn on the cross-post trigger: the id, caption, media, type, link and time of your most recent post.
How and why: Cloutware uses the profile to show which account is connected, uses the publishing permission to post the photos, videos and captions you choose, and, only with the trigger on, reads your latest post so you can send it to your other accounts.
Storage: In Cloutware's database (Neon, in the AWS us-east-1 region of the United States). Secrets are encrypted with AES-256-GCM.
Retention: Kept while the account stays connected. On disconnect, the token or secret is deleted at once and the rest within 7 calendar days. Media read for the trigger follows the media rule: deleted 7 days after upload or 48 hours after the last delivery to a platform, whichever comes first.
Sharing: Sent only to that platform, and processed by the service providers listed in this policy so Cloutware can run. Never sold, never used for advertising.
Revoke: Disconnect in the Cloutware dashboard, or remove Cloutware in Instagram under Settings, then Website permissions, then Apps and websites (https://www.instagram.com/accounts/manage_access/).

Facebook Pages

Permissions: pages_show_list, pages_read_engagement, pages_manage_posts and business_management.
Data obtained: Your Facebook user id; the list of Pages you manage, including Pages managed through a business portfolio; for each Page you connect, its id, name, picture URL and Page access token; for each post published through Cloutware, its post id, URL and status. If you turn on the cross-post trigger: the id, text, media, link and time of the Page's most recent post.
How and why: Cloutware lists your Pages so you can choose which to connect, publishes the posts you choose to those Pages, reads Page details to show which Page is connected, and, only with the trigger on, reads the Page's latest post so you can send it to your other accounts.
Storage: In Cloutware's database (Neon, in the AWS us-east-1 region of the United States). Secrets are encrypted with AES-256-GCM.
Retention: Kept while the account stays connected. On disconnect, the token or secret is deleted at once and the rest within 7 calendar days. Media read for the trigger is deleted 7 days after upload or 48 hours after the last delivery to a platform, whichever comes first.
Sharing: Sent only to that platform, and processed by the service providers listed in this policy so Cloutware can run. Never sold, never used for advertising.
Revoke: Disconnect in the Cloutware dashboard, or remove Cloutware in Facebook under Settings and privacy, then Settings, then Business integrations (https://www.facebook.com/settings?tab=business_tools).

Threads

Permissions: threads_basic and threads_content_publish.
Data obtained: Your Threads user id, username, name and profile picture URL; access tokens and their expiry; for each post published through Cloutware, its id, permalink and status. If you turn on the cross-post trigger: the id, text, media, link and time of your most recent post.
How and why: Cloutware uses the profile to show which account is connected, publishes the posts you choose, and, only with the trigger on, reads your latest post so you can send it to your other accounts.
Storage: In Cloutware's database (Neon, in the AWS us-east-1 region of the United States). Secrets are encrypted with AES-256-GCM.
Retention: Kept while the account stays connected. On disconnect, the token or secret is deleted at once and the rest within 7 calendar days. Media read for the trigger is deleted 7 days after upload or 48 hours after the last delivery to a platform, whichever comes first.
Sharing: Sent only to that platform, and processed by the service providers listed in this policy so Cloutware can run. Never sold, never used for advertising.
Revoke: Disconnect in the Cloutware dashboard, or remove Cloutware in Threads under Settings, then Account, then Website permissions.

How to ask for deletion of Meta data. Disconnect the account or delete your Cloutware account at /dashboard/settings, email support@cloutware.io, or remove Cloutware in your Facebook, Instagram or Threads settings and ask Meta to send a deletion request. Cloutware deletes the data within 7 calendar days. For requests that come through Meta, Cloutware gives you a confirmation code and a status page. Every route is open to every user. The details are on the Data Deletion page.

TikTok

Permissions: user.info.basic and video.publish.
Data obtained: Your TikTok account id (open_id), display name and avatar URL; access and refresh tokens and their expiry; at posting time, the creator settings TikTok returns (such as the privacy levels and interaction settings open to you and the longest video you can post), which Cloutware reads fresh each time and does not keep; for each post, TikTok's publish id and status.
Purpose: To show which account is connected and to post the videos and photos you choose, with the title, privacy level, interaction settings and disclosures you select on the post screen. Nothing is sent to TikTok until you confirm that post.
Storage: In Cloutware's database (Neon, in the AWS us-east-1 region of the United States). Secrets are encrypted with AES-256-GCM.
Retention: Kept while the account stays connected. On disconnect, the token or secret is deleted at once and the rest within 7 calendar days.
Sharing: Sent only to TikTok, and processed by the service providers named below so Cloutware can run.
Revoke: Disconnect in the Cloutware dashboard: Cloutware revokes the token with TikTok. You can also remove Cloutware in the TikTok app under Settings and privacy, then Security and permissions, then Apps and services permissions.

Cloutware's commitments for TikTok data, including data about people in the United States:

Cloutware uses TikTok data only to provide the posting service described above.
Cloutware does not sell TikTok data.
Cloutware does not use or disclose TikTok data for cross-context behavioural advertising.
Cloutware's service providers that process TikTok data are Vercel, Neon, Cloudflare, Trigger.dev, Resend and Sentry, all in the United States. Their roles are in Who receives your data.
Cloutware never shares your TikTok personal data with anyone else without your consent.

Permissions: pins:write, boards:read and user_accounts:read.
Data obtained: Your Pinterest user id, username and profile image URL; access and refresh tokens and their expiry; for each Pin you create through Cloutware, the id of the board you picked, the Pin id, URL and status. Your board list is fetched live from Pinterest each time you pick a board and is not stored.
Purpose: To show which account is connected, to let you pick a board, and to create the Pins you choose. You choose every Pin. A trigger never creates a Pin unless you confirm that Pin.
Storage: In Cloutware's database (Neon, in the AWS us-east-1 region of the United States). Secrets are encrypted with AES-256-GCM.
Retention: Kept while the account stays connected. On disconnect, the token or secret is deleted at once and the rest within 7 calendar days.
Sharing: Sent only to that platform, and processed by the service providers listed in this policy so Cloutware can run. Never sold, never used for advertising.
Revoke: Disconnect in the Cloutware dashboard, or remove Cloutware from the apps listed in your Pinterest security settings (https://www.pinterest.com/settings/security).

Permissions: openid, profile, email and w_member_social, for your personal profile.
Data obtained: Your LinkedIn member id, name and profile picture URL; access tokens and their expiry; for each post, its id, URL and status. LinkedIn also returns your email address with the sign-in permissions. Cloutware does not store it and does not use it.
Purpose: To show which profile is connected and to publish the posts you choose to your LinkedIn profile.
Storage: In Cloutware's database (Neon, in the AWS us-east-1 region of the United States). Secrets are encrypted with AES-256-GCM.
Retention: Kept while the account stays connected. On disconnect, the token or secret is deleted at once and the rest within 7 calendar days.
Sharing: Sent only to that platform, and processed by the service providers listed in this policy so Cloutware can run. Never sold, never used for advertising.
Revoke: Disconnect in the Cloutware dashboard, or remove Cloutware in LinkedIn under Settings, then Data privacy, then Permitted services (https://www.linkedin.com/mypreferences/d/permitted-services).

Bluesky, Mastodon, Telegram, Discord, Dev.to and WordPress

On these platforms you create the credential yourself and paste it into Cloutware. The same storage, retention and sharing rules apply to all six:

Storage: In Cloutware's database (Neon, in the AWS us-east-1 region of the United States). Secrets are encrypted with AES-256-GCM.
Retention: Kept while the account stays connected. On disconnect, the token or secret is deleted at once and the rest within 7 calendar days.
Sharing: Sent only to that platform, and processed by the service providers listed in this policy so Cloutware can run. Never sold, never used for advertising.

Bluesky

Access: An app password you create in Bluesky. It can post for you but cannot change your account password or settings.
Data obtained: Your handle, account id (DID), display name and avatar URL; the app password and the session tokens Bluesky returns; for each post, its id, URL and status.
Purpose: To publish the posts, images and videos you choose.
Revoke: Disconnect in the Cloutware dashboard, and delete the app password in Bluesky under Settings, then Privacy and security, then App passwords (https://bsky.app/settings/app-passwords).

Mastodon and compatible servers (GoToSocial, Pleroma, Akkoma)

Access: Cloutware registers with the server you name and asks to read your account profile and to publish posts and media (on Mastodon, the scopes read:accounts, write:statuses and write:media; compatible servers show their equivalent).
Data obtained: Your server address, account id, username, display name and avatar URL; the access token; for each post, its id, URL and status.
Purpose: To publish the posts and media you choose on your server.
Revoke: Disconnect in the Cloutware dashboard: Cloutware revokes the token with your server. You can also remove Cloutware from the authorized apps list in your server's account settings (on Mastodon, Preferences, then Account, then Authorized apps).

Access: A bot token for your own bot, created with BotFather, and the channel where you made that bot an admin.
Data obtained: The bot token, the bot's username, the channel id and title; for each message, its id, link and status.
Purpose: To post the messages and media you choose to that channel.
Revoke: Disconnect in the Cloutware dashboard, then remove the bot from the channel's admins or revoke its token with BotFather.

Discord

Access: A webhook URL you create for one channel.
Data obtained: The webhook URL, which contains a secret, and the webhook, channel and server names Discord returns; for each message, its id and status.
Purpose: To post the messages and media you choose to that channel.
Revoke: Disconnect in the Cloutware dashboard, then delete the webhook in Discord under Server settings, then Integrations, then Webhooks.

Dev.to

Access: An API key you create in your Dev.to settings.
Data obtained: Your username, name and profile image URL; the API key; for each article, its id, URL and status.
Purpose: To publish the articles you choose, as published or as drafts, as you choose.
Revoke: Disconnect in the Cloutware dashboard, then revoke the key in Dev.to under Settings, then Extensions (https://dev.to/settings/extensions).

WordPress (self-hosted)

Access: Your site address, your WordPress username and an application password you create on your site.
Data obtained: The site address, username, display name and avatar URL; the application password; for each post, its id, URL and status.
Purpose: To create the posts and upload the media you choose on your site.
Revoke: Disconnect in the Cloutware dashboard, then revoke the application password on your site under Users, then Profile, then Application Passwords.

Cloutware shares personal data only in these cases:

The platforms you post to. Cloutware sends each platform the content and settings you chose for it, using the credential you gave for that account.
Webhook URLs you configure. Cloutware sends post status events there.
Service providers. These companies run parts of Cloutware for Cloutware LLC, under contract, and use the data only to provide their service to Cloutware. All of them process data in the United States.

Provider	What it does for Cloutware	Data it processes	Location
Vercel	Hosts the website, dashboard and API	Every request to Cloutware, including your IP address and browser user agent	United States (us-east)
Neon	Postgres database	Everything stored in your account, with credentials encrypted	United States (AWS us-east-1)
Cloudflare	DNS, and R2 storage for uploaded media	Your media files and the requests platforms make to fetch them	United States
Trigger.dev	Background jobs that publish posts and process uploads	The post, media and credential needed for each job, while the job runs	United States
Resend	Sends Cloutware's email	Your email address, name and the message	United States
Zoho Mail	Hosts the support@cloutware.io mailbox	Emails you send to Cloutware and our replies, including your email address and anything you include	United States
Sentry	Error monitoring	Error reports, which can include your user id, IP address, browser user agent and the request that failed	United States

The law. Cloutware discloses data when a valid legal process requires it, and reports apparent child sexual abuse material to the National Center for Missing & Exploited Children, as US law requires.
A sale or merger of the business. If Cloutware LLC is merged or sold, Cloutware will tell you first. Google user data moves to a new owner only after you give explicit prior consent.

Cloutware does not sell personal data, does not share it for advertising, and does not give it to data brokers.

Cookies and device storage

Cloutware sets one cookie: the session cookie that keeps you signed in. It is essential, marked HttpOnly so page scripts cannot read it, and lasts as long as your session (60 days, extended each time you use Cloutware). Cloutware uses no advertising cookies, no analytics cookies and no third-party trackers, and no third party places cookies through Cloutware. Because the only cookie is essential, there is no cookie banner.

How long data is kept

Data	Kept until
Account details and acceptance record	You delete your account. Then deleted within 7 calendar days
Sessions	You sign out, or 60 days pass without use
Platform credentials	You disconnect the account, delete your Cloutware account, or a refresh fails. Then deleted at once
Other connected-account data	Disconnect or account deletion. Then deleted within 7 calendar days. YouTube data is refreshed or deleted at least every 30 days
Posts and per-platform results	You delete the post or your account
Uploaded media	7 days after upload or 48 hours after the last delivery to a platform, whichever comes first
Content hashes for duplicate blocking	30 days after the post they came from
Pacing counters	The end of the hour or 24-hour window they count
Audit log	12 months after each entry, including after account deletion, to investigate abuse and answer platform and legal requests
API key hashes and webhook settings	You revoke the key, remove the webhook, or delete your account
Emails you send to support	24 months after your request is closed
Record of a deletion request: confirmation code, dates and status	12 months, to show that the deletion was done
Copyright notices and counter-notices	3 years, to apply the repeat-infringer policy and answer legal claims
Database restore history	Up to 7 days after the data was deleted from the live database
Material reported to the CyberTipline	1 year after the report, as 18 U.S.C. 2258A(h) requires, or longer if law enforcement asks

If a law or a valid legal hold requires Cloutware to keep specific data longer, Cloutware keeps only that data, only for that time, and keeps a record of the requirement.

Security

All traffic to and from Cloutware uses HTTPS (TLS).
Platform credentials are encrypted at rest with AES-256-GCM.
Passwords are stored as salted hashes. API keys are stored as hashes.
Media links cannot be guessed, and media is deleted on the schedule above.
Access to production data is limited to the people who run Cloutware, and only for the reasons in this policy.
If a security breach affects your personal data, Cloutware tells you by email without undue delay.

Deleting your data

Delete your account at /dashboard/settings, disconnect a single account in the dashboard, or email support@cloutware.io. Cloutware revokes platform access first, then deletes your account, connected accounts, credentials, posts and media within 7 calendar days. The Data Deletion page has every step, what is kept and why, and how you get confirmation.

International transfers

Cloutware LLC is based in the United States, and Cloutware stores and processes all data in the United States. If you use Cloutware from the European Union, the United Kingdom, Switzerland or elsewhere, your data is transferred to the United States so Cloutware can provide the service you signed up for. Cloutware's service providers process it under data processing terms that include the European Commission's Standard Contractual Clauses or the EU-U.S. Data Privacy Framework. You can ask support@cloutware.io for details of these safeguards.

Your rights

Wherever you live, you can ask Cloutware to:

give you a copy of your personal data (access), including in a portable, machine-readable form;
correct data that is wrong;
delete your data;
restrict or object to processing based on legitimate interests;
withdraw consent to marketing email at any time, without affecting earlier processing.

Most of this you can do yourself in the dashboard. Otherwise email support@cloutware.io from your account's address. Cloutware answers within 30 days. If it cannot tell that a request comes from you, it asks you to confirm your identity first. If you are in the EU or UK, you also have the right to complain to your local data protection authority (in the UK, the Information Commissioner's Office).

Automated decisions. Duplicate-content blocking and posting pace limits run automatically. They can hold or block a post, but they have no legal or similarly significant effect on you. If you think one was wrong, email support@cloutware.io and a person will review it.

California privacy rights

This section applies to California residents and gives the disclosures required by the California Consumer Privacy Act (CCPA), as amended. In the last 12 months Cloutware collected these categories of personal information:

Identifiers: name, email address, IP address, account ids on the platforms you connect.
Account log-in credentials: your email address and password (stored as a hash), and platform credentials (encrypted).
Internet or other electronic network activity: session records, browser user agent, and the audit log of your posting actions.
The content you create: post text and media.

Sources: you, your browser, and the platforms you connect. Purposes: the ones listed in How Cloutware uses your data. Cloutware discloses these categories for business purposes only to the service providers listed above and to the platforms you direct it to post to. Retention is in How long data is kept.

Cloutware does not sell personal information and does not share it for cross-context behavioural advertising, and has not done so in the last 12 months. It has no actual knowledge of selling or sharing the personal information of anyone under 16.
Cloutware uses log-in credentials only to sign you in and to post for you, so the right to limit their use has nothing further to limit.
You have the right to know what personal information Cloutware holds about you, to have it deleted, to have it corrected, and not to be treated differently for using these rights.
To use these rights, email support@cloutware.io or use the dashboard. Cloutware confirms your request within 10 business days and answers within 45 days. It verifies your identity by checking that the request comes from your account's email address. An authorised agent can act for you with your signed permission.

Age

Cloutware is for people aged 18 or older. It does not knowingly collect personal data from anyone younger. If Cloutware learns that an account belongs to someone under 18, it closes the account and deletes its data within 7 calendar days. If you believe this has happened, email support@cloutware.io.

Changes to this policy

The date at the top of this page shows when the policy last changed. Before a material change takes effect, Cloutware emails you and shows a notice in the dashboard. Before Cloutware uses any data in a way this policy does not describe, it asks you to accept the updated policy first.

Contact

Questions, requests and complaints about privacy go to:

Cloutware LLC
30 North Gould Street, Suite R, Sheridan, WY 82801, United States
Email: support@cloutware.io
Phone: +1 805 225 6604