Beacon
Privacy notice
How Beacon handles personal data, who is responsible for it, and the choices you have. Written to be read, with the detail you would expect from a product built for regulated firms.
Version 1.0. Last updated 19 October 2026.
1. Who we are
Beacon is operated by PTR Consulting Ltd, trading as PinpointProof, a company registered in Northern Ireland under company number NI064282, with its registered office at 6th Floor, East Tower, Lanyon Plaza, 8 Lanyon Place, Belfast, BT1 3LP. PinpointProof and Beacon are trading names of PTR Consulting Ltd. We are registered with the UK Information Commissioner's Office under number [ICO registration number].
Beacon is a content and demand generation platform. A customer sets up a workspace, connects its own channels, and uses Beacon to research topics, draft and approve content, publish it, and track the results. Each workspace's data is held separately from every other workspace.
2. Two roles, explained plainly
Beacon holds data in two different capacities, and your rights route differently depending on which applies.
| Where the data sits | Our role | Whose notice applies |
|---|---|---|
| Account and usage data for people who sign in to Beacon (any workspace) | Controller | This notice |
| Data in the PinpointProof house workspace: our own prospects, contacts, partners and content | Controller | This notice |
| Data a customer loads into its own workspace: its prospects, contacts, accounts, content and connected channels | Processor, acting on the customer's instructions | The customer's own privacy notice. Our obligations to the customer are set out in the data processing agreement. |
| Visitors to a public share page, proposal, portal or tracked link | Processor for the customer who shared it; controller for pages shared by PinpointProof | The sharing customer's notice, or this one |
If you have received an email, a proposal or a content link from one of our customers and want to know how your data is used, the customer is the right first contact. We will also help, and we pass any request we receive to the customer the same working day.
3. The personal data we hold as controller
People who sign in to Beacon
- Name, work email address and the workspace or workspaces you belong to, with your role in each.
- Sign-in records: the time of each sign-in, the code or link used, and the IP address and browser the request came from.
- What you do in Beacon: content you draft, approve, schedule or publish; comments, requests and ratings you leave; settings you change. Each action is recorded with your name and the time, so a workspace has an evidenced record of who approved what.
- Questions you ask the in-app assistant (Ask Beacon) and the answers given, kept so the help improves and so a workspace can review what was asked.
- A LinkedIn connection, if you connect one: the LinkedIn member or Page identifier, the Page name, and an access token held encrypted on our servers. We never see or store your LinkedIn password.
Prospects and contacts in the PinpointProof house workspace
Where PinpointProof uses Beacon for its own marketing, we hold business contact data about people at firms we may be able to help:
- Name, job title, employer, work email and LinkedIn profile URL.
- Public professional activity, such as a post or comment on LinkedIn, a conference appearance or a published article, where it tells us a topic is relevant to that person.
- Signals that a firm may be considering a change, drawn from public sources such as regulatory publications, job adverts and press.
- Our interactions with the person: emails sent and replies received, meetings held, proposals shared, and notes made by our team.
- Engagement with content we have shared: whether a tracked link was opened, and from which campaign.
This data comes from the person directly, from their public professional profile, from public company and regulatory sources, and from introductions made by partners. We do not buy marketing lists and we do not combine data from data brokers.
Visitors to public pages and tracked links
When a tracked link is opened we record the time, the campaign it belonged to, the destination, and a truncated IP address and browser type. This tells the sharing workspace which content is useful. We do not use this to build a profile of a visitor across other websites.
4. Why we use it, and the lawful basis
| Purpose | Lawful basis |
|---|---|
| Running your Beacon account, signing you in, and providing the features your workspace has enabled | Performance of a contract with you or your organisation |
| Keeping an evidenced record of approvals and publishing decisions | Legitimate interests: ours and the workspace's, in showing what was published and who approved it |
| Sending service email: sign-in codes, invitations, approval requests, weekly digests, notices of change | Performance of a contract; legitimate interests for service notices |
| Researching and contacting people at firms we may be able to help, and sharing relevant content with them | Legitimate interests in promoting our services to business contacts, balanced against their interests, with a clear way to opt out in every message |
| Improving Beacon, including reviewing assistant questions and feature requests | Legitimate interests in running a useful, reliable product |
| Securing the service and investigating misuse | Legitimate interests; compliance with legal obligations |
| Meeting legal, accounting and regulatory duties | Legal obligation |
Where we rely on legitimate interests we have recorded a balancing assessment, and we will share a summary of it on request. We do not use personal data for automated decisions that have a legal or similarly significant effect on anyone.
5. How Beacon uses AI
Beacon uses large language models to draft content, summarise findings, suggest topics and answer questions in the app. When it does so, the text of the brief or question, and any workspace facts needed to answer it, are sent to the model provider over an encrypted connection. Our agreements with Anthropic and OpenAI prevent them using this data to train their models. Nothing Beacon drafts is published without a person in the workspace approving it first.
Beacon does not use AI to score or rank individual people, and it does not generate content about a named individual without that person's details having been provided by the workspace.
6. Who we share data with
We share personal data only with the providers that run parts of the service for us, each under a written contract, and with the channels a workspace chooses to publish to.
| Provider | What they do for us | Where |
|---|---|---|
| Supabase Inc. | Database, authentication, file storage and scheduled jobs for the Beacon application. | Hosted in the EU (AWS eu-west-1, Ireland). |
| Vercel Inc. | Hosting of the Beacon web application and its server routes. | Serverless functions run in Dublin (dub1); the edge network serves static assets worldwide. |
| Resend Inc. | Delivery of transactional email: sign-in codes, invitations, approvals, digests and notifications. | United States. |
| Anthropic PBC | Drafting, summarising and checking content and briefs on request (large language model API). | United States. |
| OpenAI, L.L.C. | Generating illustrations for posts when the image feature is used (image model API). | United States. |
| LinkedIn Ireland Unlimited Company | Publishing to LinkedIn Pages a workspace has connected, and reading that Page's post analytics, through the LinkedIn API. | Ireland and United States. |
The current list, with the transfer safeguard for each, is kept at /legal/subprocessors. We will also disclose personal data where the law requires it, for example to a regulator or a court, and we will tell the affected workspace where we are permitted to.
We do not sell personal data and we do not share it with advertisers.
7. International transfers
Beacon's database and files are hosted in Ireland. Some providers process data in the United States. For those transfers we rely on the UK International Data Transfer Addendum to the EU Standard Contractual Clauses, and where a provider is certified under the UK Extension to the EU-US Data Privacy Framework, on that certification as well.
8. How long we keep it
- Account data: for as long as your workspace is active, then 90 days to allow for reactivation, then deleted or anonymised.
- Approval and publishing records: for the life of the workspace, because they are the evidence that content went through the approval gate. On closure the workspace can export them; we delete our copy 90 days after closure unless a legal hold applies.
- Sign-in and security logs: 12 months.
- House prospect and contact records: reviewed every 12 months. A person we have had no contact with for 24 months is archived and their details suppressed from further outreach. Anyone who asks us to stop hearing from us is added to a suppression list so we do not contact them again.
- Tracked link events: 24 months, then aggregated.
- Assistant questions: 24 months.
Beacon archives rather than deletes within a live workspace, so that a record of past decisions stays intact. Archiving removes a record from everyday views; it does not stop you exercising your right to erasure, which we honour by deleting or irreversibly anonymising the personal data concerned.
9. Cookies and local storage
Beacon sets only the cookies it needs to keep you signed in. They are strictly necessary, so no consent banner appears. Your browser also stores a few preferences locally (such as which workspace you last opened and which panels are collapsed). We do not run advertising or third-party analytics cookies in the Beacon application.
10. Keeping data safe
- Every record is tagged with its workspace, and database rules enforce that one workspace can never read another's data. We test this isolation automatically before each release.
- Data is encrypted in transit and at rest. Secrets and API keys are held only on our servers, never in the browser.
- Sign-in uses a one-time emailed code; Beacon holds no passwords.
- Access to production systems is limited to named people with multi-factor authentication, and is logged.
- Changes to the data model are reviewed and tested before release, and records are archived rather than deleted so history can be restored.
If we become aware of a personal data breach that is likely to affect you, we will tell the affected workspace without undue delay and in any case within 48 hours of confirming it, and we will notify the ICO where the law requires.
11. Your rights
Under UK and EU data protection law you can ask us to:
- Tell you what personal data we hold about you and give you a copy.
- Correct anything that is inaccurate or incomplete.
- Delete your personal data, where we have no overriding reason to keep it.
- Restrict how we use it, or object to our use of it, including objecting to marketing at any time.
- Provide the data you gave us in a portable format.
- Withdraw consent, where consent was the basis we relied on.
To exercise any of these, email privacy@pinpointproof.com. We respond within one month. If the data sits in a customer's workspace we will pass your request to that customer and support them in answering it. Every marketing email we send carries an unsubscribe link, and replying with "stop" works too.
You can also complain to the Information Commissioner's Office at ico.org.uk or on 0303 123 1113, or to the supervisory authority in the EU country where you live or work. We would welcome the chance to put things right first.
12. Changes to this notice
We update this notice when the service or the law changes. The version and date sit at the top. For a material change we tell workspace owners by email at least 14 days before it takes effect.