Privacy policy

Your account

• Name, email address and, if you add one, a profile picture.
• Sign-in details: a hashed password if you set one; passkeys (only the public key and a label naming the browser and system); the two-step sign-in secret and backup codes, stored encrypted; your Google account ID if you link Google. Sign-in codes we email you are stored only as a hash and expire after 10 minutes.
• If you sign in with Google, we receive your name, your email address and whether Google has verified it. We don't receive or keep its access tokens.
• Settings such as language, time format, notification choices and your email unsubscribe choice.

Sessions and security

• For each signed-in session: IP address, browser user agent and last activity time, so you can see and end your sessions in Profile and security.
• Our web server keeps access logs (IP address, browser, page requested, time) for security and fixing faults.
• When something in Refract breaks, an error report goes to Sentry: what failed (the page or job, the error and the code that raised it), your browser and system, and the page address with any keys or tokens in it hidden. Reports aren't linked to your account and don't include your IP address, cookies or the forms you send, though an error message can now and then quote a value it failed on. When the error happens in your browser, your browser sends the report itself, so Sentry sees your IP address on that connection; it is set not to store it.
• When our staff act in the admin area, we log what they did, with their IP address and browser.

Your organization and billing

• Organization name, plan, billing interval, credits and their history, and team members' roles and workspace access.
• Payments are taken by Stripe through Link. Stripe collects your card or other payment method, billing address and tax ID on its own pages; we never see your full card number. We keep the Stripe customer ID and subscription status, and Stripe gets your organization's name and the email address of its first admin.

What you create

• Posts, their versions for each network, schedules, comments, approval decisions and the history of changes.
• Images, videos and files you upload or import, with their details (size, dimensions, alt text).
• Workspace settings, brand details (name, logo, colour) and white-label domain settings.

Connected social accounts. See Connected social accounts.

WordPress sites. See WordPress sites.

Clients and approvers. When a workspace sends a client an approval link, we store the client's name, their email address if one is entered, their decision and any message. When a client connects their accounts through a connect link, the same data as any connected account is stored, in the workspace that sent the link.

AI features. Studio stores your image description, the reference images you picked and the images made. For Assist, we store which action you ran, its credit cost and token counts, not the text sent or returned. See AI providers.

Help. Your questions, Help's answers, what Help checked in your workspace to answer, which user guide pages it cited, your Did this solve it? feedback, and each answer's token counts and cost. The conversation text is stored encrypted and only you can read it: not your teammates, and not your workspace's admins. If you select Send to a person, the Refract team gets the conversation, what Help checked, the page you were on, your note and technical details (your workspace and user IDs, plan, browser, system, app version). See AI providers.

Integrations you add. Google Drive, Dropbox, Slack and Bitly: the access details each needs (stored encrypted) and the account name or email it belongs to. Refract only opens files you pick, posts the notifications you chose to Slack, and shortens the links you post through Bitly.

Developer tools. API token names and the last four characters (the token itself is stored only as a hash), the AI agents you've approved and their access, your webhook endpoints, and a log of webhook deliveries.

Short links. Refract's own short links count clicks. They don't set cookies or store who clicked.

How Refract is used. We look at how Refract is used, to see what works and what to improve, with PostHog:

• On our public pages (the refract.social website, including the free tools, guides and comparisons, plus the user guide and sign-in), your browser sends PostHog a pageview: the page's address without its query (only campaign tags like utm_source stay), the site that sent you there, your browser, system and screen size, and when you leave the page. It also sends how fast the page loaded and responded (web vitals), with the same address. On a free tool, it also sends which tool and network you used, once, the first time you use it, and when you select its sign-up button; never what you type or the image you add, which stay in your browser. No cookies or browser storage are used. PostHog tells visits apart for one day with a hash of your IP address and browser, made with a key it replaces every day; it doesn't keep the IP address, and it can't link visits to an account. The request goes through refract.social, so your browser doesn't contact PostHog directly.
• On the same pages, PostHog also records each visit, so we can see where a page confuses people: what the page shows and how you move, click, scroll and type on it, your browser, system and screen size, and the messages the page writes to the browser's console. What you type is hidden in the recording, and so are the email address the sign-in steps show and the one you leave on a network's waitlist; a free tool's text box, count and preview are left out of the recording altogether. Nothing is stored in your browser for it: a recording ends when you close or reload the page, and it isn't linked to the pageviews or to an account. It stops when you go into the app, so nothing inside the app is recorded. It goes through refract.social too.
• Inside the app, our server tells PostHog when an account does certain things: signs up, signs in, creates a workspace, connects a network, schedules or publishes a post, invites a teammate, changes plan, buys credits or uses an AI feature. Each event carries your account's and organization's IDs and details such as which networks, how many accounts or which plan; PostHog also keeps your organization's plan, billing interval, trial and beta status, and, with your account's ID, your plan, sign-up date and whether you're in the beta. When you sign up, our server also tells PostHog the site that sent you to refract.social, the first page you opened and its campaign tags, which it noted on our server (in your session, not your browser) when you arrived; PostHog keeps them with your account's ID. Never names, email addresses, post text, files or IP addresses. The app's own pages send nothing from your browser.

Email with us. If you write to us, we keep the conversation to help you.

Network waitlists. When you ask for an email when a network opens, we keep your email address, the network and when you ticked the box agreeing to that email. We send one email when the network opens, and nothing else. We delete your address 30 days after that email; until then, write to privacy@refract.social to be taken off the waitlist.

We don't collect sensitive categories of data on purpose. Don't put them in posts unless you need to.

When you connect an account you sign in on the network's own page and choose which permissions to grant. Refract stores the account's ID, handle, display name and profile picture link, the access tokens (encrypted), and details needed to post, such as your Pages, boards, playlists or company pages. We use this data only to do what you ask in Refract.

When you disconnect an account, Refract deletes its access tokens and any other credentials it kept for it straight away. The ID, handle, display name and picture link stay so your published posts keep their history; connecting the same account again stores new tokens. YouTube is different: disconnecting a channel also revokes Refract's access with Google and deletes the channel's YouTube data (see Google API Services). If a network signs Refract out, the tokens are kept until you reconnect the account, which replaces them, or disconnect it. Deleting a workspace keeps its accounts' tokens for the 30 days it can be restored, then deletes them with it.

Network	What Refract uses the access for
Instagram	Through Facebook Login: publishing posts, reels, stories and carousels; posting your first comment; reading view, reach and interaction counts for analytics
Facebook Pages	Listing your Pages, publishing posts and videos, posting your first comment, editing and removing posts you change or remove in Refract, reading post and Page statistics
Threads	Publishing posts and reading their statistics
TikTok	Reading your profile and follower counts, publishing videos and photos, listing your videos to match statistics
YouTube	Uploading videos and Shorts, adding them to your playlists, editing and removing videos you change or remove in Refract, reading your channel and video statistics
X	Reading your profile, publishing posts with media, editing and removing posts you change or remove in Refract, reading post statistics
Pinterest	Listing your boards, creating Pins, reading Pin statistics
Bluesky	Publishing and removing posts with an app password you create (stored encrypted)
Mastodon	Publishing, editing and removing posts on your server, and reading your profile
Telegram	Posting, editing and removing messages in channels where you've made Refract's bot an admin
Discord	A webhook for the one channel you choose, stored encrypted. Posting, editing and removing messages in that channel. It can't read your messages or your Discord login
Slack	The bot token from your Slack connection, stored encrypted, and the channels you pick. Posting, editing and removing messages, and the files Refract uploaded. It can't read your messages
Tumblr	Access tokens, stored encrypted, and your blogs' names. Publishing, editing and removing posts; reading notes counts
Pixelfed	Like Mastodon: publishing, editing and removing posts on your server, and reading your profile and post counts
DEV	The API key you create, stored encrypted. Publishing, editing and unpublishing articles; reading view, reaction and comment counts

For every network, Refract stores the access tokens or keys above, your account names, the ids of the posts it made and their numbers.

We read only counts (such as views, likes, comments, shares, followers and clicks), not other people's messages, comments or profiles. We don't use data from networks for advertising, don't sell it, don't use it to train AI, and don't combine it across customers. Refract's use and transfer of information received from Google APIs follows the Google API Services User Data Policy, including the Limited Use requirements (see Google API Services).

How Refract uses YouTube API Services, what it keeps from YouTube and how to delete it are in Google API Services.

When you connect a WordPress site through the Refract for WordPress plugin, the site gives Refract its name and address, the address of its REST API, its WordPress and plugin versions, its language and time zone, and a signing secret it made. Refract stores the secret encrypted and uses it to sign what it sends to the site and to check what the site sends back. Refract also records whether the site connected through your Refract sign-in or through an API token, so it can end that access when the site is removed. The site becomes an account in your workspace, with its address as the handle and its name as the display name.

What the site sends to Refract, and when:

• When a blog post is sent (when it's published, if the plugin is set to send automatically, or when someone selects Send to Refract in the editor): the post's title, excerpt, text without its formatting, link, up to 10 of its images with their alt text, and the accounts chosen for it. Refract fills in a note from it and keeps the note, the blog post's title, link and ID on your site, and the images in your workspace's media library. It doesn't keep the post's full text. When the blog post changes, the site sends it again so the note stays up to date.
• When someone opens the Refract panel in the post editor: the post's ID in Refract, to show its versions.

What Refract sends to the site:

• When the site connects, and when someone writes a post for the site in Refract: a request for the site's categories, up to 200 of its tags, its default category, whether Refract may publish or only send drafts, and the display name of the person on the site that Refract publishes as. Refract keeps the answer for 10 minutes.
• When you publish to the site from Refract: the post's title, text, excerpt, categories, tags and links to its images, which the site downloads into its own media library.
• About blog posts that came from the site: when their versions are ready, approved, scheduled, published or failed, with the versions' text, the links to the published posts and their short links.

Disconnecting the site, in Accounts or in the plugin's settings, ends its access to Refract at once and deletes the signing secret; the address Refract sends updates to is removed within a few minutes. The plugin's own data on your site (its settings, activity log and secret) is covered by your site's own privacy policy, and the plugin suggests text for it.

Purpose	Data	Legal basis (GDPR)
Running your account, workspaces and team	Account, organization, content	Contract
Publishing, scheduling and analytics on the networks and WordPress sites you connect	Connected accounts and sites, content	Contract
Writing social posts from the blog posts your WordPress site sends	The blog post's title, excerpt, text, link and images	Contract
AI writing and images you ask for	The text, description and images for that action	Contract
Help: answering your questions about using Refract	Your question and the conversation so far, the page you're on, your workspace setup and its recent errors	Contract
Billing, credits and invoices (through Stripe)	Organization, billing	Contract; legal obligation for tax and accounting records
Emails you need: sign-in codes, invitations, approvals, failed posts, billing and security notices	Email, name	Contract
Product news emails	Email, name	Legitimate interest in telling customers about Refract; unsubscribe any time with the link in each one
The one email when a network you asked about opens	Email, the network, when you agreed	Consent, which you give by ticking the box; withdraw it by writing to privacy@refract.social
Keeping Refract and your account secure: sessions, logs, rate limits, abuse prevention	Sessions, logs	Legitimate interest in a safe service
Finding and fixing faults	Error reports	Legitimate interest in a service that works
Understanding how Refract is used, to improve it	Pageviews and recordings of the public pages, usage events (see above)	Legitimate interest in improving Refract; you can object at privacy@refract.social
Support	What you send us	Contract, or legitimate interest in answering you
Meeting legal duties and defending claims	What's needed	Legal obligation; legitimate interest

For data in a business's workspace, the business decides the purpose and legal basis; we follow its instructions.

We don't use automated decision-making that has legal or similarly significant effects on you.

AI features run only when someone in your organization uses them.

• Assist (writing help) sends the text you're working on and your instruction to Anthropic, which runs Claude. We don't keep that text.
• Versions from a note, including notes made from blog posts your WordPress site sends, send the note, the network's rules and your voice settings to Anthropic, which runs Claude, to write each version.
• Help sends your question, the conversation so far, the page you're on and what Help looks up in your workspace (for example a failed post's publish log) to Anthropic, which runs Claude. To search the user guide, the search words Help chooses are sent to OpenAI to match them to guide sections. Help never sends passwords, sign-in codes, API keys or payment details.
• Studio (images) sends your description and any reference images to fal.ai. fal runs some models itself and passes others to the company that makes them (for example OpenAI, Google, Black Forest Labs, ByteDance, Recraft, Ideogram and Alibaba). The images made are stored in your workspace's library.
• Your own keys. If your organization adds its own OpenAI, Anthropic, Google Gemini or fal key, requests that use it go to that provider under your organization's own agreement with it.

We don't use your content to train AI models. The providers handle the data under their API terms for business customers.

We don't sell your personal data, and we don't share it for cross-context behavioural advertising. We share it only with the service providers below, who process it for us, and with the services you ask us to send it to (the networks, WordPress sites, integrations, webhooks and agents you connect).

Provider	What for	Where
Hetzner Online	Servers and database	Helsinki, Finland
Backblaze	Media files and backups	Amsterdam, Netherlands (EU Central)
Cloudflare	DNS and forwarding email sent to our addresses	Global network; Cloudflare, Inc. is in the US
Resend	Sending email	United States
Stripe (Link)	Payments, tax, receipts; merchant of record	United States and EU
Anthropic	Assist (AI writing) and Help	United States
OpenAI	Help (searching the user guide)	United States
fal.ai, and the model makers it passes requests to	Studio (AI images)	United States and other countries
Sentry	Error reports	Germany (EU); Functional Software, Inc. (Sentry) is in the US
PostHog	Counting and recording visits to our public pages, and counting how Refract is used	United States
Google Fonts	Fonts in our emails, loaded by some mail apps when you open them	Google, global

Stripe acts as the seller of your purchase and handles payment data under its own privacy policy too.

We may also disclose data when the law requires it, to protect people's safety or our rights, or to a buyer if the business is sold, who would be bound by this policy.

Your data is stored in the EU, except the pageviews, recordings and usage events PostHog keeps, which it stores in the United States. Some providers above are in the United States or elsewhere. Where personal data from the EU, the EEA, the UK or Switzerland goes to a country without an adequacy decision, we rely on the European Commission's Standard Contractual Clauses (and the UK addendum) in our agreements with those providers, or on the provider's certification under the EU–US Data Privacy Framework where it has one. Anpsthemes LLC itself is in the US: our access to the data is covered by the same safeguards in our Data processing agreement. Ask us for a copy of the relevant safeguards at privacy@refract.social.

• The database and app run on servers at Hetzner in Helsinki, Finland.
• Media files and database backups are stored with Backblaze in its EU Central region (Amsterdam, Netherlands), in private storage. Media is served only through short-lived signed links.
• The database and files are backed up every night (and before each release) to Backblaze over an encrypted connection. Backups are kept for about 30 days.

Data	How long
Your account	Until you delete it. Deleting it removes your sign-in methods, memberships, API tokens, notifications and sessions at once; posts you wrote stay in their workspace without your name.
Workspaces and everything in them (posts, media files, connected accounts, approvals)	Until the workspace is deleted. A deleted workspace can be restored for 30 days, then it's permanently deleted. Its YouTube channels are disconnected and their YouTube data deleted at once (see Google API Services).
Posts and files you delete inside a workspace	Hidden at once and permanently deleted 30 days later: posts with their versions, history and approvals, files from storage. A file that a post you haven't deleted still uses is kept until that post is deleted too. Posts already published stay on the networks, and Refract's short links in them keep working: each link's target URL and click count stay until the workspace is deleted. Ask us to erase them sooner.
Disconnected social accounts	Access tokens and other credentials are deleted at once. The ID, handle, name and picture link are kept so published posts keep their history, and the account is restored if you connect it again (with new tokens). Deleted with the workspace, or sooner if you ask. A YouTube channel's data is deleted when you disconnect it, see Google API Services.
Organization, billing and credit history	While the organization exists, and afterwards as long as tax and accounting law requires.
Studio descriptions and images	Images stay in the library until deleted; the request records stay with the organization's credit history.
Assist text	Not kept.
Help conversations	Encrypted. Deleted at once when you delete one in History, and automatically 90 days after its last message. Records of each answer without any text (which checks it ran, token counts, cost, feedback) stay for measuring Help.
Conversations you send to the Refract team	Kept with our support records while we answer you and afterwards; ask us to delete them.
Sessions	Expire after 2 hours without activity, or up to 400 days with the "remember me" cookie; ending them in Profile and security removes them.
Sign-in codes	Usable for 10 minutes; kept only as a hash, and deleted a day after they expire.
API tokens	Deleted a day after they're revoked, or 30 days after they expire.
Webhook delivery logs	7 days.
Records of blog posts a WordPress site sent, kept so a retry never makes a second post	30 days.
A WordPress site's categories, tags and "publish as" name	10 minutes, in Refract's cache.
Unfinished bulk imports	7 days.
Client approval links	Work for 14 days or until the post's time; the decision stays with the post.
Network waitlist addresses	Until the network opens and we've sent its one email, then 30 days more, then deleted. Write to privacy@refract.social to be removed sooner.
Server access logs	Rotated by size, normally within days.
Backups	About 30 days.
Error reports	Deleted by Sentry after 90 days at most.
Pageviews and usage events	Deleted by PostHog after 7 years.
Recordings of visits to the public pages	Deleted by PostHog after 30 days.
Emails we've sent	Resend keeps sending logs under its own retention.

Depending on where you live (including under the GDPR, the UK GDPR and US state laws such as the CCPA), you have the right to:

• see the personal data we hold about you and get a copy, in a portable format;
• correct it (most of it you can edit yourself in Refract);
• have it deleted;
• restrict or object to our use of it, including objecting to product news emails at any time;
• withdraw consent where we rely on it;
• not be treated differently for using these rights.

How to use them. Email privacy@refract.social from the address on your account, or tell us how we can confirm it's you. We answer within one month (45 days for US state law requests), and we'll tell you if we need longer. An authorised agent can ask for you with your written permission. It's free, unless a request is clearly unfounded or excessive.

Complaints. If you're in the EU, EEA or UK, you can complain to the data protection authority where you live or work, or where you think the problem happened (in the UK, the Information Commissioner's Office). We'd like the chance to fix it first, so please write to us too.

• Disconnect a social account: in Refract, Accounts, then Disconnect on the account. Scheduled posts stop going to it (a post with no other account moves to drafts), and Refract deletes its access tokens at once. Nothing changes on the network. For a YouTube channel, Refract also revokes its access with Google and deletes the channel's YouTube data (see Google API Services).
• Disconnect a WordPress site: in Refract, Accounts, then Disconnect on the site, or Disconnect in Refract › Settings on your site. Refract ends the site's access and deletes its signing secret at once. Posts already sent stay in Refract until you delete them. Deleting the plugin from your site also deletes its data there and tries to disconnect the site.
• Remove Refract's access on the network. After that, Refract can no longer use the account.
  • Facebook and Instagram: go to Settings & privacy, Settings, Apps and websites (or Business integrations), and remove Refract.
  • Google and YouTube: remove Refract at myaccount.google.com/permissions.
  • TikTok, LinkedIn, X and Pinterest: remove Refract on the "apps" page in their settings.
  • Discord: open the channel's settings, then Integrations, and delete Refract's webhook.
  • Slack: remove the Refract app in your Slack workspace's app settings.
  • Tumblr: go to Account settings, then Apps, and remove Refract.
  • Pixelfed: revoke Refract in your server's app settings, or change your password.
  • DEV: revoke the key in Settings, Extensions.
• Delete posts and files: delete them in Posts or in the media library. They're hidden at once and permanently deleted 30 days later; a file stays while a post you haven't deleted uses it. Posts already published stay on the networks until you delete them there.
• Delete a workspace: Settings, Workspace, Delete. It's permanently deleted, with its connected accounts, posts and files, 30 days later. Its YouTube channels are disconnected at once: Refract revokes its access with Google and deletes their YouTube data straight away.
• Delete your account: Profile and security, Delete account. If you're the only admin of an organization, make someone else admin first, or ask us to close the organization.
• Ask us to delete anything: email privacy@refract.social, saying which account or network data you want deleted (for example "delete all data from my Facebook Page X"). We'll confirm when it's done, within 30 days (within 7 days for YouTube data).

Refract's use and transfer to any other app of information received from Google APIs (YouTube, Google Business Profile, Google Drive and Sign in with Google) will adhere to the Google API Services User Data Policy, including the Limited Use requirements. In particular:

• we use Google user data only to provide the features you use in Refract: uploading and managing your videos, posting to your Business Profile, importing files you pick from Drive, and signing you in;
• we don't transfer it to others except to provide those features, for security, to comply with the law, or as part of a sale of the business;
• we don't use it for advertising, and we don't sell it;
• no person reads it unless you ask us to (for support), it's needed for security or the law, or it's been made anonymous for running the service;
• we don't use it to develop, improve or train AI or machine-learning models.

YouTube API Services. Refract uses YouTube API Services. When you connect a YouTube channel, Refract uses them to show which channel you connected, upload the videos and Shorts you publish or schedule (with the title, description, privacy, tags and other settings you choose), add them to the playlist you pick, edit or remove them when you do that in Refract, and show your channel's and your videos' statistics. By using Refract's YouTube features, you agree to be bound by the YouTube Terms of Service. Google's handling of your data is covered by the Google Privacy Policy.

What Refract accesses and stores through YouTube API Services:

• Your channel: its ID, name, handle and picture.
• Access: the access and refresh tokens Google gives Refract when you allow it, stored encrypted. Refract never sees your Google password.
• Your playlists: their names and IDs, read when you pick a playlist and kept for 5 minutes.
• Your videos: the ID and link of each video Refract uploads, and whether YouTube has finished processing it. Everything else about a video (the file, title, description, tags, thumbnail and captions) is what you add in Refract.
• Statistics: your channel's views, subscribers and number of videos, read every hour while the channel is connected, and each video's views, likes and comments, read every hour for 30 days after it's published.

How Refract uses, processes and shares it:

• Use: only to do what you ask in Refract: connect the channel, publish, edit and remove your videos, and show you their statistics.
• Inside Refract: shown only to the members of the workspace where the channel is connected. Refract's team looks at it only if you ask us for help, or when security or the law requires it.
• Outside Refract: sent to Google to carry out what you ask, and stored and processed for us by the providers in Who we share it with (the servers and database at Hetzner, files and backups at Backblaze), under contracts that let them use it only to run Refract. We don't sell it, use it for advertising, combine it with other customers' data, or use it to train AI.
• No ads: Refract doesn't show ads, and doesn't let third parties serve content or ads in it.
• Cookies: Refract stores cookies on your device to keep you signed in and remember your settings. See the Cookie policy.

How long Refract keeps it, and how to delete it:

• While the channel is connected: Refract refreshes the statistics every hour, which also confirms its access still works, and checks every week that your videos still exist on YouTube. When a video is deleted on YouTube, or you remove it in Refract, Refract deletes its statistics, ID and link.
• When you disconnect the channel in Refract (Accounts, then Disconnect), or delete the workspace it's in: Refract revokes its access with Google at once and deletes the channel's YouTube data: the tokens, the statistics, the videos' IDs and links, and the channel's ID, name, handle and picture. Your posts stay in Refract with their text and media.
• When Refract loses access: you can remove Refract's access at any time on Google's security settings page, security.google.com/settings/security/permissions. Refract notices within an hour and shows the channel as signed out. If Refract can't use the channel for 6 days, whatever the reason, it disconnects it and deletes its YouTube data as above, unless you connect it again first.
• On request: email privacy@refract.social and we'll delete your YouTube data within 7 days.
• On YouTube: deleting data in Refract doesn't delete anything on YouTube. To delete a video on YouTube, remove it in Refract while the channel is connected, or delete it in YouTube.
• Backups: copies in our encrypted backups are deleted when those backups expire, after about 30 days.

Questions or complaints about how Refract handles your YouTube data: write to privacy@refract.social (see Contact).

You can remove Refract's access at any time at myaccount.google.com/permissions. See also the YouTube Terms of Service and the Google Privacy Policy.

Refract is for businesses and people aged 18 or older. We don't knowingly collect data from children. If you think a child has given us personal data, write to privacy@refract.social and we'll delete it.

• All traffic to Refract is encrypted with HTTPS.
• Social network tokens, WordPress sites' signing secrets, integration credentials, two-step sign-in secrets and other secrets are encrypted in the database.
• Passwords are stored only as hashes; API tokens and sign-in codes only as hashes.
• Sign-in supports passkeys and two-step sign-in.
• Roles limit what each team member, API token and agent can see and do.
• Media files are in private storage, reached only through short-lived signed links.
• Rate limits protect sign-in, the API and other entry points; staff actions in the admin area are logged.

No system is perfectly secure. If a breach affects your personal data, we'll tell you and the authorities as the law requires.

Refract uses only the cookies it needs to work, plus one to remember your light or dark theme. There are no analytics, advertising or tracking cookies. Details are in our Cookie policy.

In the last 12 months we've collected these categories of personal information: identifiers (name, email, IP address, account IDs), commercial information (plan and purchases), internet activity (sessions and logs), and the content and files you put into Refract. We collect them for the purposes in How we use your data, and disclose them only to the service providers in Who we share it with and the services you connect. We don't sell personal information, don't share it for cross-context behavioural advertising, and don't use sensitive personal information to infer things about you. You have the rights in Your rights.

When we change this policy we update the date at the top. For material changes we'll email the admins of each organization at least 30 days before they take effect.

• Privacy and data requests: privacy@refract.social
• Legal notices: legal@refract.social
• Everything else: support@refract.social

Post: Anpsthemes LLC · 30 N Gould St Ste N, Sheridan, WY 82801, USA.