Beacon
Data processing agreement
Our commitments to you as the processor of the personal data in your Beacon workspace. This agreement forms part of the terms of service and applies to every customer workspace.
Version 1.0. Last updated 19 October 2026.
1. Parties and scope
This agreement is between the customer that owns a Beacon workspace (the "controller", "you") and PTR Consulting Ltd, trading as PinpointProof, company number NI064282, registered office 6th Floor, East Tower, Lanyon Plaza, 8 Lanyon Place, Belfast, BT1 3LP (the "processor", "we"). It covers all personal data that you or your users load into your workspace, or that Beacon collects on your behalf, ("customer personal data"). It is written to meet Article 28 of the UK GDPR and the EU GDPR, and the terms used have the meanings given there.
For the personal data we hold in our own right, such as the accounts of people who sign in, our privacy notice applies and we act as controller.
2. Details of the processing
| Item | Description |
|---|---|
| Subject matter | Provision of the Beacon platform to the controller: topic research, content drafting and approval, publishing to connected channels, sharing of proposals and portals, engagement tracking, and management of target accounts and contacts. |
| Duration | The term of the controller's agreement with us, plus the export and deletion period in clause 10. |
| Nature and purpose | Hosting, storing, organising, retrieving, drafting from, transmitting to connected channels, and reporting on customer personal data, solely to provide the service the controller has configured. |
| Categories of data subject | The controller's prospects, clients, partners and other business contacts; people at target accounts; the controller's own staff and contractors who use Beacon; visitors to pages or links the controller shares. |
| Categories of personal data | Names, job titles, employers, work contact details, LinkedIn profile URLs and public professional activity; notes and interaction history recorded by the controller; engagement events (link opens, page views); content that mentions individuals; user account data. |
| Special category data | None is intended. The controller agrees not to load special category or criminal offence data into Beacon. |
3. Our instructions
- We process customer personal data only on your documented instructions. Your instructions are these terms, the settings and actions you take in the workspace, and any written instruction you give us.
- If the law requires us to process in another way we tell you before doing so, unless the law prevents us.
- If we believe an instruction breaks data protection law we tell you promptly and may pause that instruction until it is resolved.
- We do not use customer personal data for our own purposes. Aggregated, anonymised service statistics are not customer personal data.
4. Our people
Only people who need access to provide or support the service have it. Each is bound by a written confidentiality obligation and has been trained on data protection. Access to production systems is individual, uses multi-factor authentication, and is logged.
5. Security measures
We maintain the following measures and will not reduce them during the term.
Separation
- Every record carries its workspace identifier, and database row-level security enforces that a user or job sees only its own workspace's data.
- An automated isolation test runs before each release and fails the release if one workspace can read another's data.
Encryption and secrets
- Data is encrypted in transit (TLS 1.2 or higher) and at rest (AES-256) at our hosting provider.
- API keys, channel tokens and service credentials are held only on our servers, never in the browser or in the codebase.
Access and authentication
- Users sign in with a single-use emailed code; Beacon stores no passwords.
- Workspace owners control membership and roles. Beacon records who approved, scheduled and published each item and when.
Change and recovery
- Schema and code changes are reviewed and pass automated checks before release.
- Records are archived rather than deleted inside a live workspace, so history can be restored.
- The database is backed up daily by our hosting provider with point-in-time recovery; backups stay in the same region as the live data.
Monitoring
- Server logs, job runs and failed sign-ins are monitored. Security advisories from our hosting provider are reviewed as they are raised.
6. Helping you with data subject requests
If a data subject contacts us about data in your workspace we tell you within two working days and do not respond on the substance unless you ask us to. Beacon lets you find, export, correct, archive and anonymise a person's records yourself; where you need us to do it, we act on your instruction within five working days at no charge for reasonable volumes.
7. Sub-processors
You authorise us to use the sub-processors listed below and at /legal/subprocessors. Each is bound by a written contract with data protection obligations at least as protective as this agreement, and we remain responsible to you for their performance.
| Sub-processor | Purpose | Location and safeguard |
|---|---|---|
| Supabase Inc. | Database, authentication, file storage and scheduled jobs for the Beacon application. | Hosted in the EU (AWS eu-west-1, Ireland). Data at rest stays in the EU. Supabase support access from outside the UK and EU is covered by the EU Standard Contractual Clauses and the UK Addendum. |
| 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. EU Standard Contractual Clauses and the UK Addendum. |
| Resend Inc. | Delivery of transactional email: sign-in codes, invitations, approvals, digests and notifications. | United States. EU Standard Contractual Clauses and the UK Addendum. |
| Anthropic PBC | Drafting, summarising and checking content and briefs on request (large language model API). | United States. EU Standard Contractual Clauses and the UK Addendum. API inputs and outputs are not used to train Anthropic's models. |
| OpenAI, L.L.C. | Generating illustrations for posts when the image feature is used (image model API). | United States. EU Standard Contractual Clauses and the UK Addendum. API inputs and outputs are not used to train OpenAI's models. |
| 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. LinkedIn acts as an independent controller under its own terms once content is published. Transfers inside LinkedIn are governed by LinkedIn's own safeguards. |
Before adding or replacing a sub-processor we email workspace owners at least 30 days in advance. If you have a reasonable objection on data protection grounds, tell us within that period and we will work with you on an alternative; if none is practical you may end the affected service and we refund any prepaid fees for the unused period.
8. International transfers
Customer personal data is stored in Ireland. Where a sub-processor processes data outside the UK or the EEA, we rely on the EU Standard Contractual Clauses with the UK International Data Transfer Addendum, or on the sub-processor's certification under the EU-US Data Privacy Framework and its UK Extension, together with a transfer risk assessment. We will provide copies of the relevant safeguards on request.
9. Personal data breaches
- We tell you without undue delay, and in any case within 48 hours, after becoming aware of a personal data breach affecting customer personal data.
- The notice describes what happened, the data and people likely affected, the steps we have taken, and a named contact. We update you as we learn more.
- We help you meet your own notification duties to the ICO or another supervisory authority and to data subjects, and we do not notify them about your data ourselves unless the law requires it.
10. Return and deletion
At the end of the agreement you have 30 days to export your workspace data in a machine-readable format through the app or by asking us. We then delete customer personal data from live systems within 90 days and from backups on their normal rotation (no longer than 35 days after that), unless the law requires us to keep specific records, in which case we keep only those and only for as long as required. On request we confirm deletion in writing.
11. Information and audit
We give you the information you reasonably need to show that this agreement is being met: this document, our sub-processor list, a summary of our security measures, and the results of our isolation tests. Once in any 12 months, or after a breach, you or an independent auditor you appoint may audit our compliance on 30 days' notice, during business hours, under confidentiality, and in a way that does not expose other customers' data. We cooperate with any audit a supervisory authority requires of you.
12. Other assistance
Taking into account the nature of the processing and the information available to us, we help you with data protection impact assessments and with prior consultation of a supervisory authority where Beacon is in scope.
13. Liability and precedence
Each party's liability under this agreement is subject to the limits and exclusions in the terms of service. If this agreement conflicts with the terms of service on a data protection matter, this agreement prevails. Where the EU GDPR applies to your processing, references to UK law in this agreement include the equivalent EU provisions.
Accepted by the controller on creating or continuing to use a Beacon workspace, and by the processor on providing it. Version 1.0, 19 October 2026.