Skip to content
Programmable
Get started

Privacy Policy

Programmable, LLC · Programmable Social · last updated October 18, 2026

1. Who we are, and our two roles

Programmable Social is run by Programmable, LLC, 3607 10th St NW, Washington, DC 20010, USA. Write to [email protected] about anything here.

Programmable Social helps people who sell on LinkedIn, Reddit, X, Instagram and TikTok (the “platforms”) keep up with their conversations: it keeps the conversations their own Chrome extension captures, drafts replies, comments and first messages in the sender's voice, and lets a person approve them. The Service itself never sends anything on any platform. Messages and comments are sent, if at all, by the extension in the sender's own browser, signed in as them, and only when the account has turned that platform and sending on.

  • For people an account talks to on any of the platforms (“contacts”), the account is in charge of your data (the “controller”): it decides who to contact and why. We handle the data for it (as its “processor” or “service provider”), under our Data Processing Addendum. The do-not-contact list is the exception: we keep it ourselves, for everyone's protection (section 2).
  • For account holders and their teams, and for visitors to our site, we are the controller.

This policy describes what the Service does with personal data in both roles. An account may use contacts' data in further ways under its own privacy notice.

2. If an account talks to you on one of the platforms

What we keep

  • What's on your profile on that platform that the account's team could see: your name, headline or bio, company, your handle, and your profile, conversation and post addresses (URLs).
  • The text of your conversation with the account's sender (a direct message thread, or comments on a post), as their extension captured it while they had it open on the platform: each message, who sent it, and when. The extension sees only what the signed-in sender can see.
  • Optionally, a screenshot of a captured message, kept as evidence of what it said. Screenshots are deleted after 30 days; the text stays.
  • Drafts written for you, what was actually sent, and its status; meetings booked with you, and a brief prepared for them.
  • If the account imported you from a file or added you by hand: whatever it gave (usually name, company and profile address).
  • If you were found by Scout (a search for reporters and podcast hosts posting publicly on LinkedIn or Reddit about a topic): your public name, headline, outlet, the address and an excerpt of the public post, and why it matched. Scout contacts no one; the account reviews what it found.

Drafting with AI

To draft a reply or a first message, the account's own AI provider (Anthropic or OpenAI, on the account's own key and under the account's own agreement with it) receives what the draft needs: the conversation, your profile details above, and the account's description of its offer and of its sender. We don't use your data to train AI models, and nor may the account through us.

The do-not-contact list

If you ask an account, or us, not to be contacted, your profile address on that platform (or your handle) goes on a do-not-contact list that covers every account on the Service. Before any draft is written or any message sent, for any account, the list is checked; if the check can't be made, nothing is sent. We keep only what is needed to recognise you (the profile address or handle and forms of it, and a reason). The list is kept even after the account that added you is deleted, so that you are never contacted through the Service again. Ask [email protected] if you want to be added, or removed.

None of this is used to make decisions about you

Accounts agree not to use the Service to judge anyone's eligibility for credit, employment, insurance or housing.

Why we process it (legal bases)

On the account's behalf, to help it keep up with conversations you are part of: the account's basis is usually its legitimate interest in business contact, balanced by your right to object, which the do-not-contact list makes simple. On our own account, we keep the do-not-contact list because honouring objections is a legal obligation and in your interest, and we keep records that keep the Service secure (our legitimate interest).

3. If you have an account, or work on an account's team

  • Account: your name, email address and sign-in identity (from the shared Programmable sign-in), your organisation's name, your team and their roles, and which version of the Terms you accepted and when.
  • Senders: for each person drafts are written as, their name, role, profile address (such as their LinkedIn address), the profile PDF the account uploaded, and the description of their voice drawn from it. Upload a sender's profile only with their agreement.
  • What you set up: workspaces (your offer, motions, segments and channel rules), proof, experiments, sequences, and your send switches. Your AI key and other connected services' keys are stored encrypted, used only on our server, never shown back and never written to logs. Extension and API keys are stored only as a hash.
  • Activity: an audit log of changes in your account (who, what, when); the extension's runs (what it captured and sent, and errors); and warnings the extension saw on a platform (“safety events”), so the account can slow down or stop.
  • Billing: when paid plans are on, Stripe handles payment and holds the card details; we keep the Stripe customer reference and your plan.

We use this to provide the Service under our Terms (performing our contract), keep it secure and improve it (legitimate interest), and meet legal obligations such as tax records.

4. Visiting our pages

We don't use advertising or analytics trackers, or third-party cookies that follow you around the web. To protect the Service, Cloudflare (our network provider) and our servers handle the technical data every web request carries (IP address, browser and device type, the page asked for), and we hold IP addresses briefly to limit abuse. See Cookies.

5. Who receives personal data

  • The account and its team: on the dashboard, in its exports, and through the extension of each team member.
  • Services the account connects, under the account's own agreements with them: its AI provider (Anthropic or OpenAI) for drafting, programmable.info for company and person research if connected, and its own webhook endpoint or HubSpot if it turns those on (replies and booked meetings, with the contact's details).
  • The platforms (LinkedIn, Reddit, X, Instagram and TikTok) receive what the sender's own extension sends from the sender's own browser, as with any message they type. The Service sends nothing to any platform.
  • Our service providers, who process data only on our instructions: hosting, network and email providers, listed in the DPA, and, for accounts on paid plans, Stripe, which takes payment and holds card details. Stripe never receives contacts' data.
  • Authorities, if the law requires it; and a successor, if our business is sold or merged, on terms that keep this policy's protections.

We don't sell personal data or share it for cross-context behavioural advertising, and we don't use anyone's data to train AI models.

6. Where it is stored

Our servers are in the United States (Virginia). If you are in the European Economic Area, the United Kingdom or Switzerland, transfers to us and our providers rely on the European Commission's Standard Contractual Clauses (and the UK Addendum), or on the provider's certification under the EU-US Data Privacy Framework where it has one. Ask us for a copy of the safeguards.

7. How long we keep it

  • Contacts, conversations, drafts, meetings and senders: until the account deletes them or closes. A closed account is deleted, with everything in it, 30 days after it was closed.
  • Screenshots of captured messages: 30 days.
  • Webhook deliveries (which carry a contact's details): 30 days after they are delivered or given up on.
  • Background job records, and the autopilot and Scout ledgers that enforce their caps: 90 days.
  • Extension runs and platform safety events: 180 days.
  • Records of email we send: 13 months.
  • The do-not-contact list: for as long as the Service runs, so it keeps being honoured, including after the account that added an entry is deleted (the entry then belongs to no account).
  • Rate-limit records with IP addresses: until their window ends, at most a day.
  • Accounts and their audit log: while the account exists.
  • Database backups are kept for 14 days, so deleted data leaves them within about 15 days.

8. How we protect it

Encryption in transit (TLS) everywhere; AI keys, connected services' keys and webhook secrets encrypted at rest and never logged; extension, API and invitation keys stored only as hashes; every query scoped to one account; outbound requests to addresses an account gives us checked so they can't reach private networks; and access to production limited to the people who run it. No system is perfectly secure. If a breach affects your data, we will tell the people we must, without undue delay.

9. Your rights

Depending on where you live (for example under the GDPR, the UK GDPR, or Californian and other US state laws), you can ask to access your data, correct it, delete it, receive a copy to take elsewhere, restrict or object to its use, and withdraw consent you gave. We won't treat you differently for using these rights.

  • Contacts: write to the person who messaged you, or to [email protected]. Where the account is the controller, we pass your request to it and help it answer. If you object to being contacted, we add you to the do-not-contact list ourselves, straight away.
  • Account holders and visitors: write to [email protected]. We answer within one month (45 days under US state laws), and may need to confirm it's you first. You may use an authorised agent.

If you are in the EEA or the UK and unhappy with how your data is handled, you can complain to your data protection authority. We would like the chance to put it right first.

10. Children

The Service is not meant for anyone under 16, and we don't knowingly collect their data. If you think we hold a child's data, write to us and we will delete it.

11. Changes

If we change this policy, we will update the date at the top. If the change is material, we will also tell account owners by email or in the dashboard before it takes effect.