This policy covers only the Facebook, Instagram, Threads, TikTok, LinkedIn, YouTube, Bluesky and X accounts an organization connects to IGF Works Marketing, and the posts it publishes through them.
IGF Works Marketing lets an organization connect its own Facebook Page, its linked Instagram professional account, its Threads account, its TikTok account, the LinkedIn Pages it administers, its YouTube channel, its Bluesky account, and, if it chooses, its X account, so its staff can write, schedule and publish posts from one place.
What we receive. When someone at an organization connects an account, the platform asks them to approve access. They sign in on the platform's own page, and we never see the password (Bluesky works differently, see below). We then receive:
- for Facebook and Instagram: the name and ID of the Pages they manage, the linked Instagram account's username and ID, an access token that lets us publish to the Page and Instagram account they choose, and the ID Facebook gives our app for the person who signed in (an app-scoped user ID);
- for X: the account's username and ID, and access and refresh tokens that let us publish posts and upload images.
- for Threads: the account's username and ID, and an access token that lets us publish posts, images and videos to it.
- for TikTok: the account's display name and TikTok ID (open ID), and access and refresh tokens that let us send videos to the account's TikTok inbox as drafts (or, once enabled, publish them with the privacy and interaction settings you choose for each post).
- for LinkedIn: the name and ID of each LinkedIn Page you administer and choose to connect, the LinkedIn member ID of the person who signed in, and access and refresh tokens that let us publish posts as that Page.
- for YouTube: the name and ID of the YouTube channel you choose, and access and refresh tokens that let us upload videos to it. We do not read your other videos, comments or analytics.
- for Bluesky: your handle and account ID (DID), and a session token from the app password you enter. We use the app password once to sign in and never store it.
We keep only the Pages and accounts they choose. The rest of the list is deleted when they finish choosing, or shortly after the sign-in expires, 15 minutes after it starts. We use the app-scoped user ID to remove our app's access when they disconnect, and to find their accounts when Facebook tells us they removed our app.
X is optional and paid by the organization. X charges for every post sent to it, so X stays off for every organization until one of its administrators turns it on in Social settings and agrees that the organization pays. The organization pays X directly through its own X developer account, and we pay none of it. For X we also store the organization's own X app client ID and client secret (the secret is encrypted and never shown again after it's saved), the monthly spending limit the organization sets, a record of who turned X on or off and when along with the statement they accepted, and the estimated cost of each post and image sent to X, which we use to stop posting once the organization reaches its limit.
YouTube API Services. Our YouTube feature uses YouTube API Services. By connecting a YouTube channel you agree to be bound by the YouTube Terms of Service (https://www.youtube.com/t/terms). Google's Privacy Policy (https://policies.google.com/privacy) applies to the information Google receives. You can revoke our access at any time from your Google Account's security settings (https://security.google.com/settings/security/permissions), and by disconnecting the channel in the Hub.
We also keep what the organization's staff write and schedule in the Hub: post text, images, links, and the time each post went out, with the platform's link to it.
How we use it. Only to publish the posts the organization's staff create or approve, at the time they choose, to show them the result, and to remove access or delete data when asked. We do not read anyone's feed, messages, followers or friends. We do not post anything the organization did not write or approve. We do not sell this information or use it for advertising.
Tracked links. A post can include a short link to the organization's campaign or grant page. We count clicks on it. To count each visitor about once, we keep one-way codes made from the visitor's network address and browser for 2 days, then delete them. We never store the address itself, and the click count does not say who clicked. If someone gives a gift after following the link, we note which link it came from next to the gift.
Storage and security. Access tokens are encrypted. Only the system uses them, to publish and to keep or remove access. Staff cannot view them.
Security log. Each organization's security log records who connected, reconnected or disconnected an account and when, with the account's name. When an account is connected, the log also keeps its platform ID. Entries about sending posts name the account, and when a post is published, the entry keeps the platform's ID for that post. The log cannot be edited, so these entries stay after an account is disconnected or deleted, for as long as the organization's records are kept.
How long we keep it. For every platform (Facebook, Instagram, Threads, TikTok, LinkedIn, YouTube, Bluesky and X), an account's tokens are deleted as soon as the organization disconnects it. They are also deleted automatically when Facebook (for Facebook and Instagram), Threads or TikTok tells us the person who connected it removed our app; X, LinkedIn, YouTube and Bluesky do not tell us, so for them the organization disconnects the account or emails us. Posts and their history stay with the organization's records until the organization asks us by email to delete them; we do that within 30 days. Images are deleted 30 days after a post is published or canceled; its text and results stay. Copies in backups are gone within 30 days after any deletion. When you disconnect a TikTok account, we ask TikTok to cancel our access and delete the stored tokens. When you disconnect an X account, we ask X the same. For Facebook and Instagram we ask Facebook, unless another connected account still uses the same sign-in. Threads does not let apps do this, so we show you how to remove our access in Threads. The organization's X app keys are deleted when an administrator turns X off; the cost records for X stay with the organization's records. When you disconnect a LinkedIn Page, YouTube channel or Bluesky account, we delete the stored tokens and ask the platform to cancel our access (for LinkedIn and YouTube, if another connected Page or channel shares the same sign-in, we cancel it when the last one is disconnected; for Bluesky, we end the session at Bluesky; delete the app password in Bluesky as well). We keep a record of the disconnected account (its name and ID, and for LinkedIn the member ID of the person who signed in) and the audit log entries, so your organization's post history stays readable. To have that record deleted, contact us.
Sharing. We share post content only with the platform it is published to, at the organization's request. Facebook, Instagram and Threads are operated by Meta Platforms, Inc., X by X Corp., TikTok by TikTok Pte. Ltd. or its regional affiliate, LinkedIn by LinkedIn Corporation (LinkedIn Ireland Unlimited Company in the EEA, UK and Switzerland), YouTube by Google LLC, and Bluesky by Bluesky Social, PBC. Their own privacy policies apply to content published there.
If an organization turns on AI helpers, the text a staff member asks for and the organization's own program and funding-round information are sent to Anthropic, PBC to draft a post or research grants. Applicant, donor and recipient information is never sent. Anthropic processes it under its commercial terms and does not use it to train its models. AI drafts are saved for a person to review; nothing is posted without them.
Your choices. An organization can disconnect an account at any time under Social → Accounts. A person can also remove our access from the platform's own settings (Facebook: Settings → Business integrations; Threads: Settings → Account → Website permissions; TikTok: Settings and privacy → Security → Manage app permissions; X: Settings → Security and account access → Apps and sessions; LinkedIn: Settings → Data privacy → Permitted services; Google: Google Account → Security → Third-party apps with account access; Bluesky: Settings → Privacy and security → App passwords). When someone removes our app on Facebook, Threads or TikTok, the platform tells us, and we delete what we stored for their accounts automatically. See “Deleting your social data” for how to have the data removed.
Contact: [email protected].
This policy covers only the Facebook, Instagram, Threads, TikTok, LinkedIn, YouTube, Bluesky and X accounts an organization connects to IGF Works Marketing, and the posts it publishes through them.
IGF Works Marketing lets an organization connect its own Facebook Page, its linked Instagram professional account, its Threads account, its TikTok account, the LinkedIn Pages it administers, its YouTube channel, its Bluesky account, and, if it chooses, its X account, so its staff can write, schedule and publish posts from one place.
What we receive. When someone at an organization connects an account, the platform asks them to approve access. They sign in on the platform's own page, and we never see the password (Bluesky works differently, see below). We then receive:
We keep only the Pages and accounts they choose. The rest of the list is deleted when they finish choosing, or shortly after the sign-in expires, 15 minutes after it starts. We use the app-scoped user ID to remove our app's access when they disconnect, and to find their accounts when Facebook tells us they removed our app.
X is optional and paid by the organization. X charges for every post sent to it, so X stays off for every organization until one of its administrators turns it on in Social settings and agrees that the organization pays. The organization pays X directly through its own X developer account, and we pay none of it. For X we also store the organization's own X app client ID and client secret (the secret is encrypted and never shown again after it's saved), the monthly spending limit the organization sets, a record of who turned X on or off and when along with the statement they accepted, and the estimated cost of each post and image sent to X, which we use to stop posting once the organization reaches its limit.
YouTube API Services. Our YouTube feature uses YouTube API Services. By connecting a YouTube channel you agree to be bound by the YouTube Terms of Service (https://www.youtube.com/t/terms). Google's Privacy Policy (https://policies.google.com/privacy) applies to the information Google receives. You can revoke our access at any time from your Google Account's security settings (https://security.google.com/settings/security/permissions), and by disconnecting the channel in the Hub.
We also keep what the organization's staff write and schedule in the Hub: post text, images, links, and the time each post went out, with the platform's link to it.
How we use it. Only to publish the posts the organization's staff create or approve, at the time they choose, to show them the result, and to remove access or delete data when asked. We do not read anyone's feed, messages, followers or friends. We do not post anything the organization did not write or approve. We do not sell this information or use it for advertising.
Tracked links. A post can include a short link to the organization's campaign or grant page. We count clicks on it. To count each visitor about once, we keep one-way codes made from the visitor's network address and browser for 2 days, then delete them. We never store the address itself, and the click count does not say who clicked. If someone gives a gift after following the link, we note which link it came from next to the gift.
Storage and security. Access tokens are encrypted. Only the system uses them, to publish and to keep or remove access. Staff cannot view them.
Security log. Each organization's security log records who connected, reconnected or disconnected an account and when, with the account's name. When an account is connected, the log also keeps its platform ID. Entries about sending posts name the account, and when a post is published, the entry keeps the platform's ID for that post. The log cannot be edited, so these entries stay after an account is disconnected or deleted, for as long as the organization's records are kept.
How long we keep it. For every platform (Facebook, Instagram, Threads, TikTok, LinkedIn, YouTube, Bluesky and X), an account's tokens are deleted as soon as the organization disconnects it. They are also deleted automatically when Facebook (for Facebook and Instagram), Threads or TikTok tells us the person who connected it removed our app; X, LinkedIn, YouTube and Bluesky do not tell us, so for them the organization disconnects the account or emails us. Posts and their history stay with the organization's records until the organization asks us by email to delete them; we do that within 30 days. Images are deleted 30 days after a post is published or canceled; its text and results stay. Copies in backups are gone within 30 days after any deletion. When you disconnect a TikTok account, we ask TikTok to cancel our access and delete the stored tokens. When you disconnect an X account, we ask X the same. For Facebook and Instagram we ask Facebook, unless another connected account still uses the same sign-in. Threads does not let apps do this, so we show you how to remove our access in Threads. The organization's X app keys are deleted when an administrator turns X off; the cost records for X stay with the organization's records. When you disconnect a LinkedIn Page, YouTube channel or Bluesky account, we delete the stored tokens and ask the platform to cancel our access (for LinkedIn and YouTube, if another connected Page or channel shares the same sign-in, we cancel it when the last one is disconnected; for Bluesky, we end the session at Bluesky; delete the app password in Bluesky as well). We keep a record of the disconnected account (its name and ID, and for LinkedIn the member ID of the person who signed in) and the audit log entries, so your organization's post history stays readable. To have that record deleted, contact us.
Sharing. We share post content only with the platform it is published to, at the organization's request. Facebook, Instagram and Threads are operated by Meta Platforms, Inc., X by X Corp., TikTok by TikTok Pte. Ltd. or its regional affiliate, LinkedIn by LinkedIn Corporation (LinkedIn Ireland Unlimited Company in the EEA, UK and Switzerland), YouTube by Google LLC, and Bluesky by Bluesky Social, PBC. Their own privacy policies apply to content published there.
If an organization turns on AI helpers, the text a staff member asks for and the organization's own program and funding-round information are sent to Anthropic, PBC to draft a post or research grants. Applicant, donor and recipient information is never sent. Anthropic processes it under its commercial terms and does not use it to train its models. AI drafts are saved for a person to review; nothing is posted without them.
Your choices. An organization can disconnect an account at any time under Social → Accounts. A person can also remove our access from the platform's own settings (Facebook: Settings → Business integrations; Threads: Settings → Account → Website permissions; TikTok: Settings and privacy → Security → Manage app permissions; X: Settings → Security and account access → Apps and sessions; LinkedIn: Settings → Data privacy → Permitted services; Google: Google Account → Security → Third-party apps with account access; Bluesky: Settings → Privacy and security → App passwords). When someone removes our app on Facebook, Threads or TikTok, the platform tells us, and we delete what we stored for their accounts automatically. See “Deleting your social data” for how to have the data removed.
Contact: [email protected].