Privacy Policy
Tether.82 Last updated: 19 September 2026
Tether.82 is a social media analytics and content tool operated by NO82 SOCIAL WORLD LTD, a company registered in England and Wales (company number 15480675), registered office 20 Wenlock Road, London, England, N1 7GU. In this policy "we", "us" and "our" mean that company.
We are registered with the Information Commissioner's Office under registration number ZC244672.
For anything in this policy, contact info@tether82.com.
1. Two different roles
Tether.82 is used in two ways, and our legal role differs between them.
Where an agency uses Tether.82 for their own clients, that agency decides whose pages are analysed and why. They are the data controller; we are their data processor and act on their instructions. Our processing terms with them are set out in a separate Data Processing Agreement.
Where we use Tether.82 for our own clients, we are the controller, and this policy governs that processing directly.
This policy covers both. Where a section applies to only one, it says so.
2. What we hold
Account data
Email address, hashed password, account settings, and a record of which version of the Terms you accepted and when, for everyone who signs in. This is how you have an account at all. Where you enable two-factor authentication, the secret for it is held by our authentication provider.
Billing data
For paying customers: name, billing address, VAT status and invoice history. Card details are entered directly with Stripe and never reach our systems; we hold only Stripe's reference for your customer record and subscription.
Platform connections
Where you connect a LinkedIn page or ad account directly, the authorisation token LinkedIn issues is stored so the service can retrieve your data without asking you to sign in each time. Tokens are held in a table no application role can read, are used only server-side, and are removed when you disconnect the page or close the account.
Social media page data
For each LinkedIn, Instagram or Facebook page connected to the service, we retrieve and store performance data published by that platform: post text, post links, post images and video thumbnails, impressions, clicks, reactions, comments, shares and follower counts, by date.
This is business page data rather than personal browsing data. We do not receive, and do not ask for, information identifying the individuals who viewed or engaged with a post. Where a post's own text names a person, that text is stored as published.
Material uploaded by a customer
Reports and documents a customer chooses to upload, and images they upload to replace expired artwork.
Working notes
Free-text context we record about an account (its goals, audience and house style) to improve what the tool generates. They are internal working notes about a business account, not about individuals, and are not shown to other customers. If a note contains personal data about you, it is covered by the rights in section 8 and will be disclosed on request.
Account activity log
A record of significant actions on an account: invitations, pages linked, members added or removed, data exports, closure, failed payments and ended subscriptions. Visible to the account holder on their account page.
Prospect audit material
Where we are considering offering Tether.82 to a business, we may capture publicly visible information about that business's own social media presence, being screenshots of its posts and the engagement shown on them, alongside our own notes, to prepare a short assessment we can share with them. This is material we compile ourselves about a prospective customer. It is not connected page data, and it is used only to prepare and offer that assessment.
Technical data
Standard server and security logs generated by hosting a web service.
3. Why, and on what basis
| Purpose | Lawful basis (where we are controller) |
|---|---|
| Providing the service to you | Performance of a contract |
| Keeping accounts secure | Legitimate interests — protecting the service |
| Generating drafts and reports | Performance of a contract |
| Improving the service | Legitimate interests — we assess this does not override your rights |
| Assessing and approaching a prospective customer | Legitimate interests — business development, balanced against the limited, business-facing nature of the material |
| Billing and collecting payment | Performance of a contract |
| Sending emails about your account, billing and service changes | Performance of a contract |
| Sending reminder emails when an account has gone quiet | Legitimate interests — you can stop these with one click |
| Meeting legal or accounting obligations | Legal obligation |
Where we act as a processor for a customer, the lawful basis is theirs to determine, not ours.
We do not sell personal data. We do not use it for advertising. We do not carry out automated decision-making that produces legal or similarly significant effects.
4. Artificial intelligence
Tether.82 uses Anthropic's Claude models to draft post copy and written report sections. To do this, the relevant material — post text, performance figures, report content, and the context notes described above — is sent to Anthropic's API at the moment a draft is generated.
Two things are worth stating plainly:
- Anthropic does not train its models on data submitted through its API by default.
- Generated text is a draft. It is reviewed by a person before it is published anywhere.
5. Who else is involved
We use the sub-processors below. Each publishes its own data protection terms, linked from its name. The current list is always at tether82.com/legal/subprocessors, and we give customers at least 30 days' notice of any change, as set out in the DPA.
| Sub-processor | Purpose | What it can access | Location |
|---|---|---|---|
| Supabase, Inc. | Database, authentication, file storage | Account emails, hashed passwords, all stored page data, uploaded documents and images, platform connection tokens | European Union (eu-west-1) |
| Vercel Inc. | Application hosting and scheduled jobs | Every request made to the service, and the data each request handles while it runs | United States, with a global edge network |
| Anthropic PBC | AI text generation | Post text, performance figures, report content and context notes, at the moment a draft is generated. Not used to train models. | United States |
| Windsor.ai (Onvocado GmbH) | Retrieval of performance data from LinkedIn, Instagram and Facebook | Page performance data for connected pages, and the platform authorisations used to fetch it | Germany (Hetzner), with Cloudflare CDN |
| Stripe Payments Europe, Ltd. | Subscription billing and card payments | Name, email, billing address, card details (never seen by us), VAT status, invoices | Ireland and the United States |
| Resend, Inc. | Transactional email (account, billing and reminder emails) | Recipient email address and the content of each email we send | United States |
| Sentry (Functional Software, Inc.) | Application error monitoring | Error diagnostics, which may include personal data present in an error's context | European Union (EU data region) |
| HubSpot, Inc. | CRM integration. Only used when you choose to connect your own HubSpot account. | Company and deal records from the connected CRM, and the advertising-exposure signals we write back to it | United States, or the European Union where your HubSpot account is EU-hosted |
| Cal.com, Inc. | Booking demo calls from the marketing site | Name, email and any notes a prospect enters when booking a call. Not used for account holders. | United States |
List last changed 26 September 2026. The current list is always at tether82.com/legal/subprocessors.
6. Where data is held
Our database and file storage are hosted by Supabase in the EU (eu-west-1) region. Our hosting, and some of the sub-processors above, operate outside the UK, including in the United States.
Where personal data is transferred outside the UK, that transfer is covered by the UK International Data Transfer Agreement or the EU Standard Contractual Clauses together with the UK Addendum, as provided in each sub-processor's own terms.
7. How long we keep it
- Account data: while the account is open, and for 30 days after it is closed.
- Page and post data: while the page remains connected, and for 30 days after an account is closed.
- Uploaded documents and working notes: until deleted by the customer or by us, and in any event for 30 days after an account is closed.
- Prospect audit material: deleted once the assessment has been shared or the opportunity closes, and in any event within six months of capture.
- Billing records: six years after the transaction, as HMRC requires.
- Logs and records we must keep for other legal reasons: for as long as the relevant law requires.
Thirty days after an account is closed, a scheduled job deletes the account, its stored files and every record attached to it. The activity log keeps a single entry recording that the deletion happened. Backups are overwritten on their own cycle and are not retrieved to satisfy a deletion request.
8. Your rights
Under UK data protection law you may ask us to give you access to your personal data, correct it, delete it, restrict or object to how we use it, or provide it in a portable form. You may also withdraw consent where we rely on consent.
You can download a copy of everything held for your account from your account page at any time, and close the account there too. For anything else, ask at info@tether82.com. We will respond within one month.
If we hold your data as a processor on a customer's behalf — that is, if you are a client of an agency that uses Tether.82 — please raise the request with that agency. We will pass on any such request we receive and assist them in answering it.
If you are unhappy with our response you may complain to the Information Commissioner's Office at ico.org.uk, or on 0303 123 1113.
9. Security
Access to data is enforced at the database level by row-level security, so an account can only read its own records. Customers of Tether.82 cannot see one another's pages, data, or the notes we hold, under any circumstances. Passwords are hashed by our authentication provider and are never visible to us, and you can add two-factor authentication from your account page.
Data is encrypted in transit and at rest by our providers. Credentials that bypass row-level security are held only in server-side jobs and never reach a browser. Significant actions on an account are recorded in its activity log.
No system is perfectly secure. If a breach occurs that is likely to result in a risk to people's rights and freedoms, we will notify the ICO within 72 hours of becoming aware of it, and notify those affected where the law requires.
10. Cookies
The service sets only the cookies it needs to work: the cookies that keep you signed in, a short-lived cookie that protects the connection flows against forgery, and, for our own staff, a cookie recording which customer account they are viewing. None of these is used for advertising or tracking, and we do not use third-party analytics on the service.
11. Changes
We will update this page when the service changes. Where a change materially affects how we handle personal data, we will tell affected customers directly rather than relying on this page being read.