Privacy Policy
Last updated: 22 May 2026 · Effective:22 May 2026 · Prime Construct Ltd (trading as TillTalk)
This version supersedes the version dated 8 May 2026. Changes in this revision: explicit disclosure of TillTalk's use of merchant data to operate per-merchant marketing and to inform aggregate decision-policy heuristics across the service (new §5); explicit naming of the Meta marketing-platform data categories accessed under OAuth (§3.5); explicit naming of key named sub-processors and Anthropic's data-training position (§6.1); update of the change-notification mechanism (§14).
This Privacy Policy explains how Prime Construct Ltd (“TillTalk”, “we”, “us”, or “our”) collects, uses, shares, and protects personal data in connection with the TillTalk service. It applies to:
- Visitors to the TillTalk website at tilltalk.ie
- Business owners who sign up for TillTalk as clients
- Customers of TillTalk's clients whose transaction data passes through TillTalk's systems
If you have any questions about this policy or want to exercise your rights, contact us at daniel@tilltalk.ie.
1. Who we are
Data controller for our website and our clients:
Prime Construct Ltd
Trading as TillTalk
Registered office: Farran, Mourneabbey, Co. Cork, P51 KF88, Ireland
Company registration number: 751535
VAT number: IE4224722DH
Contact: daniel@tilltalk.ie
For the personal data of our clients' customers, TillTalk acts as a data processoron behalf of the client. The client is the data controller of their own customer data; TillTalk processes that data only on the client's instructions, under a Data Processing Agreement (DPA).
2. What TillTalk does
TillTalk is an AI-managed marketing service for independent hospitality and retail businesses. Our system:
- Runs Meta, Google, and TikTok advertising campaigns on behalf of our clients
- Reads point-of-sale (POS) transaction data from our clients' till systems (Clover, Square, etc.) on a strictly read-only basis
- Pushes hashed conversion events to ad platforms via the Meta Conversions API (CAPI), Google Enhanced Conversions, and TikTok Events API to verify which ads led to real revenue
- Manages Facebook Page and Instagram Business comments, direct messages, and organic publishing under each client's approval
- Generates weekly reports and recommendations for each client
Understanding what TillTalk does is important for understanding how we use personal data.
3. Personal data we collect
3.1 From website visitors
When you visit tilltalk.ie:
- Technical data: IP address, browser type, device type, operating system, pages visited, referrer URL, time and date of visit
- Cookies and similar technologies: see our Cookie Policy
- Cloudflare Turnstile: we use Cloudflare's bot-protection challenge on signup forms; this collects technical signals about your browser
- Analytics: if enabled, aggregated usage statistics
3.2 From clients (business owners who sign up)
When you sign up as a client:
- Account data: name, email address, business name, business address, phone number, business category, website
- Authentication data: password (hashed; never stored in plain text)
- Billing data: payment information processed by Stripe; we do not store full card numbers
- Communications: WhatsApp messages, dashboard chat messages, emails between you and TillTalk
- Voice notes: audio you send via WhatsApp is transcribed via a third-party speech-to-text service. Audio files are processed and not retained by TillTalk after transcription; the resulting text is retained as part of your conversation history.
- POS connection credentials: tokens or OAuth grants for your POS system, encrypted at rest. We use these to read transaction data only.
3.3 From clients' customers (your customers' data, when you are a client)
When TillTalk reads your client's POS transactions to verify ad performance, the following customer-level fields may be processed:
- Hashed identifiers: customer email, phone number, first name, last name (each hashed via deterministic SHA-256 before any storage or transmission)
- Card token: an opaque token from the POS system, never the card number itself
- Transaction metadata: amount, tip, tender type (cash/card/gift card), channel, timestamp, refund status
TillTalk does not store raw email addresses, raw phone numbers, or raw names of clients' customers. Only deterministic hashes are persisted. The original raw values are read from the POS system, hashed in memory, and discarded.
3.4 From third parties
- Stripe: billing and subscription status
- Twilio: WhatsApp delivery confirmations
- POS providers (Clover, Square, etc.): transaction data on the client's instruction
- Ad platforms (Meta, Google, TikTok): aggregated ad performance metrics and audience match rates relating to campaigns we run on the client's behalf
3.5 From merchant marketing-platform connections (Meta, Google, TikTok)
When you, as a client, grant TillTalk OAuth consent to operate your marketing accounts, TillTalk reads:
- Facebook Pages and Instagram Business accounts: page metadata, posts, ratings, comments, direct messages, follower data, page-level insights
- Ad accounts and Business Manager metadata: ad accounts, campaigns, ad sets, ad performance, audience metadata, attribution data, ad spend
- Lead forms: leads submitted to your Facebook Lead Ads (when leads_retrieval is granted)
Access is per-merchant under your OAuth grant. TillTalk uses these to plan and run campaigns, publish organic content under your approval, respond to comments and direct messages under your approval, measure ad performance, and compute incremental revenue. TillTalk does not access another client's marketing data using your OAuth grant.
4. How we use personal data and why
| Purpose | Personal data | Legal basis |
|---|---|---|
| Operate the website | Technical data, cookies | Legitimate interest (running our service) |
| Authenticate clients | Account data, authentication data | Performance of contract |
| Provide the TillTalk service to clients | Account data, communications, POS credentials, transaction data | Performance of contract |
| Run ad campaigns and verify their effectiveness | Hashed customer identifiers, transaction metadata | Performance of contract (with the client; we are a processor) |
| Build matched audiences for ad platforms (Meta CAPI, Google Customer Match, TikTok) | Hashed customer identifiers, transaction metadata | Performance of contract (with the client; we are a processor) |
| Detect POS anomalies excluded from incremental revenue calculation | Transaction metadata | Performance of contract |
| Manage Facebook Page and Instagram Business comments, direct messages, and organic publishing under client approval | Page content, comments, messages, IG posts | Performance of contract |
| Bill clients | Account data, billing data | Performance of contract |
| Send service emails (account, security, billing) | Account data, email | Performance of contract |
| Send marketing emails to prospective clients | Email, name | Legitimate interest (B2B), with consent where required by ePrivacy law; opt-out available in every email |
| Detect fraud and abuse | Technical data, communications | Legitimate interest |
| Comply with legal obligations | All applicable data | Legal obligation |
| Improve the service via aggregate decision-policy heuristics (see §5) | Aggregated outcome data; no personally identifiable information | Legitimate interest |
We never use the personal data of our clients' customers for any purpose other than verifying ad performance for the client whose customers they are. We do not build cross-client profiles of consumers. We do not sell personal data. We do not use one client's customer data to benefit another client. See §5 below for how aggregate, non-identifying outcome signal does inform the service across clients.
5. How merchant data informs the service
Each merchant's data is used to operate that merchant's marketing campaigns. This includes building a per-merchant brand voice profile (the agent's understanding of how the merchant talks, what they value, what they want to convey), per-merchant prompt context (recent decisions, conversation history, recent POS patterns), and per-merchant operational learning (which audiences perform for this merchant, when their restaurant is at capacity, what their customers typically ask about).
Outcomes from each merchant's marketing decisions feed into TillTalk's aggregate decision-policy heuristics. These heuristics are statistical patterns derived from outcomes — for example, “campaigns targeting Tuesday-lunch with audience characteristic X performed Y% better across N merchants in similar businesses.” Heuristics are aggregated across merchants. The aggregation never exposes any individual merchant's data, customer records, campaign specifics, or financial details to any other merchant.
What crosses merchants is statistical signal. What does not cross merchants is personally identifiable information, raw campaign data, customer records, financial figures, or any data that could identify a specific merchant or their customers. No merchant data is sold, licensed, or shared with any party other than the platforms required to operate the merchant's marketing (Meta, Google, TikTok, Anthropic, Supabase, Railway, Vercel, Twilio).
6. Sharing personal data
We share personal data with the following categories of recipients, only as necessary:
6.1 Named key sub-processors
TillTalk currently shares personal data with the following named recipients to operate the service:
- Meta Platforms Ireland Ltd (Ireland, EU) — operate Facebook Page, Instagram Business account, and Meta Ads campaigns on the Merchant's behalf under merchant authorisation. Receives hashed customer identifiers via the Marketing API and Conversions API.
- Google Ireland Ltd (Ireland, EU) — operate Google Ads campaigns and Enhanced Conversions on the Merchant's behalf when the Merchant authorises Google Ads. Receives hashed customer identifiers via the Google Ads API and Customer Match.
- TikTok Technology Limited (Ireland, EU) — operate TikTok For Business campaigns on the Merchant's behalf when the Merchant authorises TikTok. Receives hashed customer identifiers via the TikTok Marketing API and Events API.
- Anthropic — TillTalk uses Claude (Anthropic's AI) to perform agent reasoning. Data sent to Anthropic via the API is processed under Anthropic's data processing terms. No data sent to Anthropic via the standard API is used to train Anthropic's foundation models.
- Supabase — the database provider that hosts TillTalk's per-client records. Located in the EU.
- Railway and Vercel — compute and hosting providers for the TillTalk backend and dashboard.
- Twilio — WhatsApp and SMS message delivery.
- Stripe — payment processing for subscription billing.
- SendGrid — transactional and marketing email delivery.
- Sentry — application error monitoring.
No other third parties. No personal data is sold.
6.2 Categories of sub-processors
In addition to the named recipients above, TillTalk relies on service providers in the following categories to operate the service:
- Database, authentication, and file storage — for storing client account data, encrypted credentials, and operational data
- Application hosting and compute — for running the TillTalk backend and AI agent infrastructure
- Website hosting — for serving tilltalk.ie and our client dashboard
- Payment processing — for billing clients and processing subscription payments
- Messaging delivery — for sending WhatsApp and SMS messages between TillTalk and clients
- WhatsApp Business platform — the underlying platform on which messaging delivery operates
- AI processing — for the AI capabilities that power the TillTalk service
- Speech-to-text processing — for transcribing voice notes you send to TillTalk
- Email delivery — for transactional and marketing emails
- Edge networking and bot protection — for serving traffic and protecting signup flows
- Error monitoring — for detecting and diagnosing application errors
- Asset storage and image processing — for storing creative materials used in advertising
- Source-code and knowledge-base hosting — for storing TillTalk's source code and operational knowledge
A current named list of sub-processors is available at tilltalk.ie/sub-processors. We work to ensure that an appropriate Data Processing Agreement (DPA) is signed with each of these providers before they process personal data on our behalf, and we will inform clients of any material additions to our sub-processor list at least 30 days in advance.
If you are a Clover merchant, see our Clover Privacy Addendum for additional detail on how data received from Clover is handled.
6.3 Ad platforms (on client instruction)
When you are a client, we push hashed conversion events to the ad platforms you have asked us to run campaigns on:
- Meta (Facebook / Instagram) via the Conversions API
- Google via Enhanced Conversions
- TikTok via the Events API
These events contain hashed identifiers and transaction values. The ad platforms use them for matching, attribution, and measurement. The hashing is deterministic, which means the platforms can match the hashes against hashes derived from their own user records. The hash itself does not allow recovery of the original raw value, but a successful match enables the platform to associate the conversion event with a known platform user. For that reason, hashed identifiers may still constitute personal data under GDPR.
6.4 Legal disclosures
We may disclose personal data when required by law, court order, or to protect legal rights, safety, or property.
6.5 Business transfers
If TillTalk is acquired or merged, personal data may transfer to the new owner under the same protections.
7. International data transfers
Some of our service providers are based outside the European Economic Area, primarily in the United States. Where personal data is transferred outside the EEA, we rely on:
- EU Standard Contractual Clauses with the recipient
- Adequacy decisions where the European Commission has determined the destination country provides an adequate level of protection (e.g. EU-US Data Privacy Framework)
- Supplementary measures such as encryption in transit and at rest, and the hashing of customer identifiers before transfer
You can request copies of the safeguards in place by contacting daniel@tilltalk.ie.
8. How long we keep personal data
| Data | Retention |
|---|---|
| Website visit logs | 30 days |
| Client account data | Duration of the client relationship plus 7 years (Irish Companies Act / tax law) |
| Client billing records | 7 years (Irish tax law) |
| Communications between client and TillTalk | Duration of the client relationship plus 2 years |
| Voice note audio | Discarded immediately after transcription |
| Merchant marketing-platform data (Meta Pages, IG, ad accounts, BM) | Duration of the client engagement plus 30 days for deletion processing |
| Hashed customer identifiers | 24 months row-level; aggregated into daily summaries thereafter (see §11) |
| Hashed customer identifiers from cancelled clients | Deleted within 30 days of contract termination |
| Aggregate decision-policy heuristics (see §5) | Retained beyond engagement; anonymised and statistical only; contains no personally identifiable information about any merchant or customer |
| Sentry error logs | 90 days |
After these periods, data is deleted or fully anonymised.
9. Your rights under GDPR
If you are in the EEA, UK, or another jurisdiction granting equivalent rights, you have the following rights:
- Access — request a copy of the personal data we hold about you
- Rectification — correct inaccurate personal data
- Erasure — request deletion of your personal data (“right to be forgotten”) via tilltalk.ie/data-deletion
- Restriction — restrict our processing of your personal data
- Portability — receive your personal data in a portable format
- Objection — object to processing based on legitimate interest
- Withdraw consent — where processing is based on consent
- Complaint — lodge a complaint with the Irish Data Protection Commission (dataprotection.ie) or your local supervisory authority
To exercise any of these rights, email daniel@tilltalk.ie. We will respond within one month.
A note on the customers of our clients:if you are a customer of a TillTalk client and want to exercise rights over your personal data, please contact the client directly — they are the data controller and hold the relationship with you. TillTalk will assist the client in fulfilling your request.
9.1 Two ways to stop sharing data with TillTalk
Beyond the formal rights listed above, you can stop TillTalk from processing your data in two practical ways. Each has a different scope.
(a) Disconnect an individual integration. If you uninstall the TillTalk app from one of your connected systems (for example, removing it from your Clover dashboard, revoking permissions from your Meta account, or disconnecting any other integration), TillTalk will automatically and without further request:
- delete the access token or credential we held for that integration;
- delete the raw data we cached from that platform (for example, individual transaction snapshots, fetch logs, webhook events older than 90 days);
- mark the integration as disconnected in your TillTalk account.
Your TillTalk account itself, your other connected integrations, your conversation history with us, and any aggregated reports already delivered to you are preserved. You can reconnect the integration at any time by reauthorising it; doing so issues a new access token and resumes normal operation.
(b) Cancel your TillTalk account. If you cancel your account (currently by emailing daniel@tilltalk.ie; a self-service cancellation flow will be added to the dashboard), TillTalk will delete all data we hold about your business across every connected platform. Some records — billing records, audit logs, error logs — are retained for the legally-mandated periods set out in §8 and then deleted.
The first option is the right one if a specific integration is no longer useful to you, if you are migrating to a different POS or ad platform, or if you uninstalled an app by accident and want to reconnect later. The second is the right one if you are ending your TillTalk subscription entirely.
10. Security
We implement technical and organisational measures appropriate to the nature of the personal data we process and the risks involved, including:
- Encryption in transit: TLS 1.2 or higher for all communications between TillTalk components and external services
- Encryption at rest: database encryption at rest for all stored data; sensitive credentials are additionally encrypted before storage
- Hashing of customer identifiers: SHA-256 deterministic hashing applied before customer identifiers are persisted or transmitted to ad platforms
- Access controls: access to production systems and personal data is restricted to authorised personnel; at present this is limited to the founder. As TillTalk grows, role-based access controls will be expanded accordingly
- Error monitoring: Sentry monitoring for application errors and anomalies, with alerts to the founder
- Read-only POS access: TillTalk does not write to client POS systems; all POS interactions are read-only by design and enforced in code
- Periodic review: sub-processor agreements and security practices are reviewed at least annually
We are continuing to develop our internal logging and audit capabilities. If you have specific questions about the controls in place at any time, contact daniel@tilltalk.ie.
No system is perfectly secure. If we become aware of a personal data breach affecting your data, we will notify you and the Data Protection Commission as required by GDPR (within 72 hours where feasible).
11. Specific notes on customer data hashing and ad platform matching
This section explains how TillTalk handles your customers' data (when you are a client) and your data (when you are a customer of a TillTalk client).
When a customer pays at a TillTalk client's POS, the transaction may include identifying fields such as email, phone, or name (entered at the till, captured by a loyalty system, or provided through online ordering).
TillTalk's processing pipeline:
- Read the transaction from the POS API
- Normalise the identifying fields (lowercase email, strip phone formatting, etc.)
- Hash each field using deterministic SHA-256
- Store only the hashes — raw values are never written to disk by TillTalk
- Push the hashes to the relevant ad platform's conversion API along with the transaction value, so the platform can verify that one of its users became a paying customer
- Aggregate transaction data older than 24 months into daily summaries; row-level personal data is deleted at that point
Hashing is deterministic, meaning the same input always produces the same hash. This allows ad platforms to match a hash they receive from TillTalk against a hash derived from their own user records, without TillTalk and the platform exchanging raw personal data. As noted in §6.3, hashed identifiers can still constitute personal data under GDPR because a successful match links the conversion to a known user on the receiving platform.
Cash transactions and transactions without identifying fields are never hashed or pushed to ad platforms. Anonymous transactions cannot be attributed and are excluded by design.
If you are a customer of a TillTalk client and want a transaction record relating to you removed, please contact the client directly. The client can instruct TillTalk to remove its hashed record. Where ad platforms expose deletion endpoints (such as Meta's CAPI deletion event or Google's user-data deletion API), TillTalk will use those endpoints to propagate the deletion to the platforms on the client's instruction. Some platforms apply their own processing timelines to deletion requests, which are outside TillTalk's control.
12. Cookies
See our separate Cookie Policy at tilltalk.ie/cookies for details on cookies and similar technologies.
In summary:
- Strictly necessary cookies (authentication, security)
- Functional cookies (remembering your preferences)
- Analytics cookies (only if you consent)
- No advertising or tracking cookies on tilltalk.ie itself
13. Children
TillTalk is a B2B service for businesses. We do not knowingly collect personal data from children under 16. If you become aware that a child has provided personal data to us, please contact daniel@tilltalk.ie and we will delete it.
14. Changes to this policy
We may update this policy from time to time. The “Last updated” date at the top will reflect the most recent change. Material changes will be notified to clients via WhatsApp at least 14 days before they take effect; non-material changes (clarifications, typos, structural reorganisation) take effect on publication.
A version history of this policy is available on request.
15. Complaints
If you believe TillTalk has not handled your personal data in accordance with applicable law, you have the right to lodge a complaint with:
Irish Data Protection Commission
21 Fitzwilliam Square South
Dublin 2, D02 RD28
Ireland
Phone: +353 (0)761 104 800
Website: dataprotection.ie
We would appreciate the opportunity to address your concern first by emailing daniel@tilltalk.ie before you contact the Data Protection Commission.
16. Contact
For any privacy-related question, request, or complaint:
Email: daniel@tilltalk.ie
Post: Prime Construct Ltd, Farran, Mourneabbey, Co. Cork, P51 KF88, Ireland
We aim to respond within 5 working days for general queries and within one month for formal data subject rights requests.