← Back to Tether.82

For IT, security and data protection

Security and data

How Tether.82 connects to your pages, what it holds, where that data lives, who can see it, and how you get it out or deleted. Everything here is also in the Privacy Policy and the Data Processing Agreement. This page puts it in the order a buyer asks.

How we connect

Tether.82 reads page data through the platforms' own interfaces. A page admin authorises the connection by signing in to LinkedIn and choosing the page, the same consent screen any LinkedIn app shows. For Instagram and Facebook, and for some LinkedIn pages, the retrieval runs through Windsor.ai, a data connector that holds the platform authorisation on our behalf.

  • No browser extension. Nothing is installed on anyone's computer.
  • No scraping. If a platform does not publish a figure through its interface, we do not have it.
  • Read-only. Tether.82 never posts, edits, comments, follows or messages on your behalf, and never writes to your CRM.
  • Page-level only. We receive what the platform reports about the page and its posts, never who viewed or engaged with a post as an individual.
  • Connections can be revoked at any time from the account page, or from LinkedIn's own permitted services settings. The stored authorisation is deleted when a page is disconnected.

What we hold

Account
Email address, a hashed password we cannot read, settings, and which version of the Terms was accepted.
Page data
Post text, links and images, impressions, clicks, reactions, comments, shares and follower counts by date, for each connected page.
Ads data
Where an ad account is connected: campaign spend and results, and which companies and job functions the ads reached, as LinkedIn reports them in aggregate.
CRM data
Only if you connect HubSpot or import a file: company names, websites, owners, deal names, amounts and stages. Nothing is written back.
Billing
Name, billing address, VAT status and invoice history. Card details go directly to Stripe and never reach us.
Not held
Personal profile data of individuals, follower lists, viewer identities, direct messages, or anything a page admin cannot already see in the platform's own analytics.

Where it lives

The database and file storage are hosted by Supabase in the European Union (eu-west-1). The application runs on Vercel, which operates from the United States with a global edge network. Data is encrypted in transit with TLS and at rest by those providers.

Where data leaves the UK, the transfer is covered by the UK International Data Transfer Agreement or the EU Standard Contractual Clauses with the UK Addendum, through each provider's own terms. The full list of third parties, what each can see and where it runs, is at /legal/subprocessors (last changed 26 September 2026). Customers get 30 days' notice before anything is added to it.

  • Supabase, Inc. · Database, authentication, file storage · European Union (eu-west-1)
  • Vercel Inc. · Application hosting and scheduled jobs · United States, with a global edge network
  • Anthropic PBC · AI text generation · United States
  • Windsor.ai (Onvocado GmbH) · Retrieval of performance data from LinkedIn, Instagram and Facebook · Germany (Hetzner), with Cloudflare CDN
  • Stripe Payments Europe, Ltd. · Subscription billing and card payments · Ireland and the United States
  • Resend, Inc. · Transactional email (account, billing and reminder emails) · United States
  • Sentry (Functional Software, Inc.) · Application error monitoring · European Union (EU data region)
  • HubSpot, Inc. · CRM integration. Only used when you choose to connect your own HubSpot account · United States, or the European Union where your HubSpot account is EU-hosted
  • Cal.com, Inc. · Booking demo calls from the marketing site · United States

Who can see it

  • Row-level security is enforced in the database on every table holding customer data. An account can read only its own records. One customer cannot see another's pages, data, reports or notes under any circumstances.
  • Credentials that bypass row-level security exist only in server-side code and scheduled jobs, in one module, and are never reachable from a browser request.
  • Platform and CRM authorisation tokens are held in tables with no read policy for any application role. Not even a signed-in account holder can read them back.
  • Two-factor authentication is available to every account from the account page. Agency accounts can invite team members with their own logins rather than sharing a password.
  • Significant actions on an account (invitations, pages linked, members added or removed, exports, closure) are written to an append-only activity log visible on the account page.
  • Our own staff access to customer data is limited to supporting the account, and the notes we keep about an account are never shown to that customer or any other.

How AI is used

Report commentary, post drafts and page analysis are generated with Anthropic's Claude models. What is sent is the page's own post text, performance figures and any context notes you have added, at the moment a draft is generated. Under Anthropic's commercial terms this data is not used to train models.

Every figure in a report is computed by Tether.82 from the stored data first; the model is given the figures and asked to explain them, and it is never asked to produce a number itself. Each report keeps the figures its commentary was written from, so any sentence can be checked against them.

How long we keep it

While open
Page and post data stays for as long as the page is connected, so year-on-year comparisons work.
On closure
Thirty days after an account is closed, a scheduled job deletes the account, its files and every record attached to it. One log line records that the deletion happened.
Uploads
Staging uploads (draft assets, audit screenshots) are swept six months after upload by a scheduled job.
Billing
Accounting records are kept six years, as HMRC requires.
Getting it out
Every account can download everything held for it from the account page at any time, as a JSON file, with no request needed. Closure is on the same page.

Compliance

Registration
NO82 SOCIAL WORLD LTD is registered with the Information Commissioner's Office, registration number ZC244672.
Processor terms
A Data Processing Agreement under Article 28 UK GDPR forms part of the Terms and is published at /legal/dpa. No separate signature needed; a countersigned copy is available on request.
Breach notice
Customers are told within 48 hours of us becoming aware of a breach affecting their data. The ICO is notified within 72 hours where the law requires.
Data subject requests
Answered within one month. Where we hold data as a processor for an agency, the request goes to that agency and we assist.
Audit
The DPA provides for audit on reasonable notice. A written record of processing is kept and produced to the ICO on request.

What we do not have

Tether.82 is built and run by a small company. We do not hold SOC 2 or ISO 27001 certification, and we would rather say so than imply otherwise. What we offer instead is the specific list above, an answer to any security questionnaire within five working days, and a conversation with the person who wrote the code.

Questions, questionnaires and requests for a signed DPA: info@tether82.com.