Privacy Policy
Last updated November 16, 2026 (version 2026-11-16.2)
This policy explains what personal information SkeinPost collects, why, who we share it with, and the choices you have. SkeinPost is operated by Bradley Minor, a sole proprietor based in Ontario, Canada ("SkeinPost", "we", "us"). The privacy contact for SkeinPost is hello@skeinpost.com. The mailing address is in the Contact section below. This policy is written for the Personal Information Protection and Electronic Documents Act (PIPEDA) and, where they apply, for privacy laws in the United States, the United Kingdom, the European Economic Area, and Thailand.
1. What we collect
- Account: your email address, a display name taken from that address, the workspaces you belong to, your role, and the workspace name the owner chooses.
- Content: brands, captions, images, videos, schedules, approvals, comments, and notes that you or your team add. Uploaded files are stored on the server disk that hosts SkeinPost, not in a separate file-storage product.
- Connected accounts: the account name, profile photo address, profile link, and the network’s account id, plus whether the connection is active. We do not store your social network passwords. Access tokens are held by Post for Me, not by us. For Bluesky you type an app password (not your main password). We send it to Post for Me to make the connection and we do not store it in our database. For Discord you give us a channel webhook link. We store it encrypted, use it only to post to that channel, and delete it when you disconnect the channel.
- Results: post outcomes and metrics the networks report through Post for Me (such as views, likes, comments, and shares). We do not estimate numbers the network did not send.
- Billing: plan, monthly or yearly interval, subscription status, trial and period dates, and Stripe customer, subscription, and price ids. Card numbers go to Stripe and do not reach our servers.
- Agreement and security records: the time you agreed to the Terms and this policy, the version, and the IP address used. Sign-in and sign-up codes are stored only as hashes, expire in 10 minutes, and work once. We also keep short-lived rate-limit counters in memory, and the host keeps server logs that can include an IP address, a time, and an error.
- People you invite: the email address, role, and brands on an invite. We use that address to send the invite and, if they ask, a sign-in code.
- API keys: the name you give a bot key, and a hash of the key. We show the raw key only when it is created.
- Client links: the name and email of the person a client link is for, entered by the workspace. Their PIN is stored only as a slow, salted hash, and their setup codes only as hashes. For each device they sign in on we keep a hash of the sign-in token, the browser’s user agent, and when it was first and last used. We record wrong PIN or code tries, pauses, and admin actions on the link, with the IP address and time, so the workspace can spot misuse. We never record the PIN itself.
- Referrals: when you open someone’s invite link we keep its code in a cookie on your browser for 60 days, and count the visit. If you sign up, we record which workspace invited yours. For each payment you make, we record the amount and the referral credit it earned, and for your first payment we keep Stripe’s card fingerprint (not the card number) to stop people rewarding themselves. We email the person who invited you when you sign up and when you start paying. We do not tell them your name or email address.
- Unsubscribe records: if you use an unsubscribe link in a marketing or outreach email, we store that email address in lowercase, the reason (unsubscribe), whether you used the page or the one-click link, and the time. We keep this so we do not send you more marketing or outreach email. It does not stop sign-in codes or other messages the Service needs to send.
We do not sell personal information, and we do not use your content or account data to train AI models.
2. Why we use it
- To provide the Service: your calendar, publishing, approvals, results, sign-in codes, and invites.
- To bill you, apply plan limits, and open the Stripe customer portal when you ask.
- To keep accounts secure, prevent abuse, and fix problems.
- To send messages the Service needs: sign-in and sign-up codes, invites a member asked us to send, and notices about your account, billing, or these policies.
- To record and honour an unsubscribe from marketing or outreach email, and to keep that address off later messages of that kind.
- To keep a record of your agreement, and to meet tax, accounting, and legal duties, or to establish or defend a legal claim.
Under PIPEDA, those are the purposes we identify at or before collection. We do not use personal information for a new purpose without telling you and, where the law requires it, getting consent.
3. Consent
You consent to this collection and use when you tick “I agree to the Terms of Service and Privacy Policy” at sign-up, when you accept an invite, or on the agree screen, and when you connect a social account or type an address to invite. You can withdraw consent by asking us to delete your account, as section 10 describes. If you withdraw consent we may not be able to provide the Service, and we may keep what the law requires us to keep. Connecting a network is also consent to that network receiving the post you choose to publish.
4. Legal bases where UK or European law applies
Where the UK GDPR or the EU GDPR applies, we rely on:
- Contract: your account, the workspace, publishing, invites you ask us to send, and billing.
- Legitimate interests: securing the Service, preventing abuse, keeping basic logs, and understanding failures. These interests are limited to running a private scheduling tool, and they do not override your rights.
- Legal obligation: tax and accounting records, and responding to a lawful request.
- Consent: where a law requires it, including marketing or outreach email. We ask before sending that mail where the law requires it, and we keep an unsubscribe record when someone opts out.
5. Who we share it with
We share personal information with the providers that actually run the Service, and only for the purposes above. We do not sell it, and we do not share it for cross-context advertising. We do not use a separate analytics, advertising, or error-tracking product. Uploaded files stay on the server that hosts SkeinPost.
- Railway hosts the application, the SQLite database, and uploaded media on the server disk.
- Post for Me connects social accounts, holds the access tokens, publishes posts, and briefly stores media copies used for publishing.
- The networks you connect: Instagram, Facebook, X, TikTok, TikTok Business, YouTube, LinkedIn, Pinterest, Bluesky, Threads and Discord. Instagram, Facebook, and Threads are Meta services. YouTube is a Google service. TikTok and TikTok Business are TikTok services. Posts to Discord are sent by us directly to Discord, not through Post for Me. Each network receives the content you choose to publish there, under its own terms and privacy policy.
- Stripe takes payment, stores the card, charges renewals, issues receipts, and hosts the customer portal where you cancel or switch between monthly and yearly.
- Resend sends sign-in codes, sign-up codes, workspace invites, and any marketing or outreach email.
We may also disclose information if the law requires it, to protect someone’s safety or our rights, or as part of a merger or sale of the Service (in which case this policy still describes the use, and we will tell you if the operator changes).
6. Social networks, YouTube, TikTok, and Meta
If you connect YouTube, SkeinPost uses YouTube API Services. The YouTube Terms of Service apply, and Google’s privacy policy is at https://policies.google.com/privacy. You can revoke the app’s access in the Google security settings. The permission screen may say Post for Me, which is the app that holds the Google connection. You can also disconnect the channel inside SkeinPost.
SkeinPost’s use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. We use YouTube account and analytics data only to provide and secure the feature you asked for: showing the channel, publishing what you schedule, and showing results. We do not sell it, use it for advertising, or allow humans to read it except as needed to provide the Service, to secure it, to comply with law, or with your permission.
To take down TikTok data: disconnect TikTok or TikTok Business inside SkeinPost, remove SkeinPost or Post for Me from the connected apps in your TikTok settings, and email hello@skeinpost.com to delete the TikTok account details and metrics we still hold. A post already published on TikTok stays there until you delete it on TikTok.
To take down Meta data (Instagram, Facebook, or Threads): disconnect the account inside SkeinPost, remove the app under Facebook Settings, Apps and Websites (and the equivalent Instagram or Threads apps list, if it is shown there), and email hello@skeinpost.com to delete the account details and metrics we still hold. We do not offer an automated Meta data-deletion callback. A post already published on a Meta network stays there until you delete it on that network.
7. Your workspace is private
Brands, posts, and files in a workspace are visible to the people the owner invites, and to a bot key created for that workspace. A platform administrator can open a workspace only to provide support or to investigate abuse, and that access is logged. For content a customer stores about their own clients, the customer decides what is stored and is responsible for having a lawful reason to store it. We process it to provide the Service. If your information sits in a workspace someone else owns, we will pass your request to that owner or help them handle it.
8. Where information is processed
We are based in Ontario, Canada. Railway, Post for Me, Stripe, Resend, and the social networks may process information in the United States and in other countries. Those countries may not give the same privacy protections as your home, and public authorities there may be able to reach the information under local law. Under PIPEDA we remain accountable for personal information handled by these providers for us. Where UK or EU law requires a transfer tool, we rely on the contracts we have with the provider (such as standard contractual clauses, where the provider offers them) or, where that is the available basis, on your consent. You can email us for more detail about a particular provider.
We do not have an office in the United Kingdom or the European Economic Area. You can still use the rights below and complain to a supervisory authority there. If you are in Thailand, cross-border processing is part of providing the Service, and the rights in section 12 include the rights the Personal Data Protection Act gives you.
9. How long we keep it
- Account and workspace content: while the account or workspace is open. If you cancel and do not ask us to delete it, we keep it so you can come back. Publishing stops when the subscription ends. Scheduled posts are returned to drafts when publishing locks. The files stay until you ask us to delete them or until we close the account.
- Billing records and the record of your agreement (time, version, and IP): for as long as Canadian tax rules generally require us to keep them, which is six years after the end of the tax year they relate to, and longer if a dispute or audit is still open.
- Sign-in and sign-up codes: until they expire (10 minutes) or are used, and only as hashes.
- Client links: the person’s name, email, PIN hash, device records, and security records stay until the link is turned off (device records end at once) or the brand is deleted. A device left unused for 400 days is signed out.
- Invites: until they are accepted, revoked, or expire (14 days), and then as part of the workspace until that workspace is deleted.
- Referral records: as part of the workspace until it, or the workspace that invited it, is deleted.
- Unsubscribe records: for as long as SkeinPost might send marketing or outreach email, so a later message of that kind is not sent to that address. Deleting the record would remove the only note that the address opted out. Sign-in codes and other service email are not affected.
- Server logs: for the host’s ordinary operations. We do not keep a separate log archive. Rate-limit counters stay in memory for a short window and are not a database of your activity.
- After we delete something, a disk snapshot kept by the host may still hold a copy until the host overwrites it. We do not use those snapshots as a customer backup, and we cannot promise to restore content from them. Post for Me and the networks may keep their own copies under their policies until you disconnect or delete the post there.
10. Deleting your information
There is no delete-account button in the app. Email hello@skeinpost.com from the account address and say whether you want the workspace deleted, your user record deleted, or both. We may need to confirm it is you. We will delete the workspace content we hold (brands, posts, uploaded media, connected-account records, invites, and API keys) and, if you are not a member of another workspace, the user record, within 30 days. We will still keep billing and agreement records for the period in section 9, an unsubscribe record so marketing or outreach email does not start again, and anything a law or an open claim requires.
Disconnect social accounts in the app first if you want Post for Me to drop the connection. Deleting our records does not delete a post that is already live on a network. If you only belong to someone else’s workspace, we will remove you from it. Content in that workspace belongs to the workspace, and we will pass a deletion request about that content to the owner.
You can also revoke a network’s access on the network itself. For Google, use the Google security settings. For TikTok and Meta, use the steps in section 6, then email us if you also want the copy we hold deleted.
11. Security and breaches
We use HTTPS, store sign-in codes and session tokens only as hashes, and keep each workspace’s data separate. Administrator access to another workspace is limited and logged. No system is perfectly secure. If a breach of security safeguards creates a real risk of significant harm, we will notify the Office of the Privacy Commissioner of Canada and the affected people as soon as feasible, and we will keep a record of the breach, as PIPEDA requires. Where the UK or EU GDPR requires it, we will notify the supervisory authority within 72 hours of becoming aware of a breach that meets that duty, and we will notify you when the risk to you is high. Where Thailand’s Personal Data Protection Act requires notice to the Personal Data Protection Committee or to you, we will give that notice.
12. Your rights
Email hello@skeinpost.com to use a right. We will respond within 30 days, or any longer time the law allows and that we tell you about, and we may need to confirm your identity. We will not discriminate against you for asking.
- Canada (PIPEDA): you can ask for access to the personal information we hold about you, ask us to correct it, and challenge our compliance with this policy. You can also complain to the Office of the Privacy Commissioner of Canada (priv.gc.ca).
- United States, including California: you can ask to know, correct, or delete personal information, and to receive a copy. We do not sell personal information and we do not share it for cross-context behavioral advertising. Those rights, where a state law gives them, are not limited to California.
- United Kingdom and EEA: you can ask for access, correction, erasure, restriction, and a portable copy, and you can object to processing based on legitimate interests. You can withdraw consent where we rely on consent. You can complain to the UK Information Commissioner’s Office (ico.org.uk) or to the supervisory authority where you live. We have not appointed a UK or EU representative. You can still reach us at the email above.
- Thailand: where the Personal Data Protection Act applies, you can ask for access, correction, erasure, and a copy, you can object or ask us to stop, and you can withdraw consent. You can complain to the Personal Data Protection Committee.
Some of these rights have exceptions, for example where we must keep a tax record or where fulfilling a request would reveal someone else’s information. There is no self-serve profile editor for your email address. Ask us and we will correct information that is wrong, or tell you if we need the workspace owner to do it.
13. Cookies and on-device storage
We use only cookies needed to run the Service. We do not use advertising or analytics cookies.
- Session cookie (
sp_session): keeps you signed in for 30 days. It is HttpOnly and SameSite Lax, and it is Secure when the site is served over HTTPS. Sign-out deletes it. - Message cookie (
sp_flash): carries a one-time on-screen message across a redirect, for about a minute. The page can read it so it can show the message and delete it. - Connection cookie (
sp_connect): remembers a social-account connection that is in progress, so the account is filed under the right brand. It is HttpOnly, SameSite Lax, and signed. - Client link cookie (
bp_client): keeps the person a client link is for signed in on that device after they enter their PIN. It is sent only to that one link’s pages, holds a random token, lasts 400 days and renews on each visit. It is HttpOnly, SameSite Lax, and Secure over HTTPS. Logging out, or the workspace signing the link out, ends it. - Invite cookies (
sp_refandsp_ref_hint): set only when you open someone’s invite link.sp_refholds the invite code so the right person gets credit if you sign up. It is HttpOnly and SameSite Lax.sp_ref_hintholds no code; the page reads it to show the friend offer. Both last 60 days and are deleted when you sign up. - Sidebar cookie (
sp_sidebar): remembers whether the sidebar is open or collapsed on this browser. The page can read and update it. It is SameSite Lax, lasts a year, and holds only the word open or collapsed. It is Secure when the site is served over HTTPS.
The browser also stores which brand menus you collapsed (sp_brand_nav_collapsed in local storage on your device). That is not a cookie and it is not sent to us with each request. We do not track you across other sites, so a Do Not Track signal does not change what these cookies do.
14. Email
The Service sends service email: sign-in codes, sign-up codes, client link setup codes (only when the person on the link asks for one), a workspace invite when a member enters an address, and notices about your account, billing, or these policies. Those are not marketing. We do not add invite addresses to a marketing list. An invite is one message, plus a sign-in code if that person opens the link and asks for one. If you were not expecting an invite, ignore it.
Marketing or outreach email, when we send it, asks for express consent first where the law requires that. Each of those messages names SkeinPost, includes hello@skeinpost.com and our mailing address, and includes an unsubscribe link. The link opens a page where one button records the request at once. Mail programs can also unsubscribe in one step (a one-click request). We record it immediately, which is inside the 10 business days Canada’s anti-spam law (CASL) allows. You can also email hello@skeinpost.com to tell us not to send marketing or outreach email. Service messages about your account and security, including sign-in codes, do not have an unsubscribe, because the Service cannot sign you in without them, and an unsubscribe record does not block them.
15. Children
The Service is not for anyone under 18, and we do not knowingly collect personal information from children. If we learn an account is used by someone under 18, we will delete it.
16. Changes
We will post updates on this page and change the date and version above. For a material change we will tell you by email or in the app at least 14 days before it takes effect, and we will ask you to agree again. The version stored with your agreement is 2026-11-16.2 until we change it.
17. Contact
Privacy requests, access and correction requests, deletion requests, and copyright notices all go to hello@skeinpost.com, the privacy contact for SkeinPost. Mail: 1108 - 250 Consumers Road #193, North York, ON M2J 4V6, Canada. Phone: +1 289-932-5752.
You can also complain to the Office of the Privacy Commissioner of Canada, to a UK or EEA supervisory authority, to a US state attorney general where a state privacy law gives you that right, or to the Personal Data Protection Committee in Thailand.