PRIVACY NOTICE
How Kerdence handles personal data
What we collect, why, who helps us process it, how long we keep it, and how to ask us to show, correct or delete it.
1. Who we are
This notice is given by Kerdence Systems LLP (UEN T26LL0930K), 135 Cashew Road, #06-117, Singapore 670135 (“Kerdence”, “we”, “us”). It explains how we collect, use, disclose and look after personal data under Singapore’s Personal Data Protection Act 2012 (PDPA).
It covers our website kerdencesystems.com, our service pages on sign.kerdencesystems.com (booking a call, sending an enquiry, applying to join, signing contracts), our own social media Pages and accounts, and the Kerdence platform we use to run our business.
Our Data Protection Officer can be reached at dpo@kerdencesystems.com or by post at the address above. Write to the DPO for any question about this notice or your personal data.
When we act for a client. Some of our clients use the Kerdence platform to run their own business, and their customers’ data passes through it. For that data the client is the organisation responsible and Kerdence is its data intermediary: we process it only on the client’s instructions, under our contract with them. If you are a customer of one of our clients, please contact that business first. We will help them answer you.
2. What we collect, and from whom
Website visitors
- Enquiries. The enquiry form on kerdencesystems.com does not send anything to us. It prepares an email draft in your own email app, and you choose whether to send it. If you do, we receive what you wrote: usually your name, email address, company, the service you are interested in and your message. You can also copy or download the draft; it then stays on your device.
- Ordinary request data. Like every website, our host receives technical details when your browser loads a page: your IP address, browser type, the page requested and the time.
- “Is this really Kerdence?” If you check a caller’s code on our verify page, only the code you type is sent to our service to look it up.
- The website has no analytics, advertising pixels or tracking scripts.
People who book a call or send an enquiry on our service pages
- Your name and email address, and if you give them, your phone number, company and a short message or topic.
- The time you booked, and the campaign tags in the link you followed (for example, which of our posts it came from).
- When you arrive from one of our campaign links, we count the visit using only the link’s tags, the page and the time. We do not record your IP address, browser or identity for this count.
- Our forms refuse NRIC, passport and bank details. Please do not send them to us.
Businesses and business contacts we may call
- We find businesses from public sources: the ACRA register of entities (published on data.gov.sg), OpenStreetMap, and Google’s places service (from which we keep only Google’s place reference).
- We keep the business name, a contact phone number, email address, website and postal code, notes of our calls, short voice notes our team records about a call, and the result of each Do Not Call check (see section 8).
- If you ask us not to contact you, we keep your number or address on a do-not-contact list so that we never contact you again.
Applicants and members of our team
- When you apply: your full name, email, phone, the entity you would contract through (if any), country, the type of your ID document and its last four characters only, and a short note on why you are applying. We never ask for a full NRIC or passport number, or for bank or tax details, on an application.
- When you join: your name, work email and role; your contract and its version; your earnings, statements and payments; the training you complete, practice scores and practice-call recordings; your sign-in and sign-out times and device type; a record of who viewed your records; your presence on the team board, daily check-ins and coaching notes; your work chat messages and files; meeting attendance, audio and transcripts; and the questions you ask Kai, our team assistant, and its answers.
- To be paid, you give your identity, bank and tax details directly to Stripe on Stripe’s own page. Kerdence does not receive or store them; we keep Stripe’s account reference and status.
Clients and their contact people
- The client’s legal name, UEN and address; contact people’s names, job titles, emails, phone and WhatsApp numbers; notes from our consultations; proposals and contracts.
- Electronic signing: the signer’s name, email, signature image, the IP address and browser used, the time of each step, and the signed documents.
- Payments: the paying company’s name and billing email are sent to Stripe, which holds them and any card details. We keep Stripe’s references, amounts and dates.
- Platform access: the names and emails of the client’s administrators, and their sign-in records.
People who comment on or message our social media Pages
- When you comment on a post, or send a message to, Kerdence’s own Facebook Page, Instagram account or LinkedIn Page, the platform’s official API gives us: the name shown on your profile, the platform’s ID for your profile, the text you wrote, when you wrote it, and the post or conversation it belongs to. We also keep the replies our team writes to you.
- A person on our team reads and answers each item. We only ever reply to someone who wrote to us first; our system cannot start a conversation.
- TikTok: we use TikTok’s official API only to publish our own videos and to read their total views, likes, comments and shares. We receive no information about individual TikTok users through it.
- We also read the published numbers of our own posts (impressions, engagements, clicks), which are totals and do not identify you.
3. Why we use it
- To answer your enquiry, hold the call you booked, and follow up on it.
- To contact businesses that may benefit from our services, by phone, email or text, subject to the Do Not Call rules.
- To consider your application, and to engage, train, support, pay and work with members of our team.
- To prepare, sign, perform and enforce our contracts, and to invoice and collect payment.
- To reply to comments and messages sent to our social media Pages, and to measure how our own posts perform.
- To provide the Kerdence platform to our clients, and to process their customers’ data on their instructions.
- To keep our systems secure, keep records of who did what, and meet our legal, tax and accounting obligations.
We do not sell personal data, and we do not use it for advertising profiles.
4. Who processes it for us
We use the following service providers. Each processes personal data only to provide its service to us.
| Provider | What it does for us | Personal data involved |
|---|---|---|
| DigitalOcean | Our main server, in its Singapore region | The Kerdence platform’s data |
| Netlify | Hosts the website kerdencesystems.com | Ordinary request data (IP address, browser, page, time) |
| Cloudflare | Our domain’s DNS, the secure connection to our service pages on sign.kerdencesystems.com, and routing of email sent to our addresses | Request data for our service pages; email in transit |
| Gmail for our business email; Google Drive for our encrypted off-site backups; the Gemini API for Kai, our team assistant (paid tier) | Emails you send us; backups (encrypted before upload, so Google cannot read them); team members’ questions to Kai | |
| Anthropic | The Claude API, the backup provider for Kai | Team members’ questions to Kai |
| Resend | Delivers email we send | Recipient addresses and the content of our emails |
| Stripe | Client invoices and payments; payouts to team members | Paying company’s name and billing email, card details; team members’ identity, bank and tax details |
| Meta (Facebook, Instagram), LinkedIn, TikTok | Publishing our own posts, reading their numbers, and (Meta and LinkedIn) receiving and answering comments and messages sent to our Pages, through each platform’s official API | As described in section 2 |
| PDPC Do Not Call Registry | Checking Singapore numbers before we call or text them | The phone number checked |
Kai, our team assistant. Kai only serves our own team. When a team member asks Kai a question, we send the AI provider the question with phone numbers, email addresses and links masked out, the name of the page the member is on, and the list of actions Kai can take. We never send client records, figures, private messages or customer details. We use only the providers’ paid API terms, under which they do not use the content to train their models.
Tools a client connects. When a client connects its own systems to the Kerdence platform (for example its email provider, WhatsApp Business account, calendar, accounting software, CRM or Stripe account), the data goes to that provider on the client’s instructions and under the client’s own agreement with it.
We may also disclose personal data when the law requires it, or to our professional advisers under a duty of confidence.
5. Transfers outside Singapore
We keep the Kerdence platform’s data in Singapore: on our server in DigitalOcean’s Singapore region and on our standby computer in Singapore. Some of the providers in section 4 process data in other countries, including the United States: Google, Anthropic, Resend, Stripe, Meta, LinkedIn and TikTok, and the global networks of Netlify and Cloudflare. Kai’s questions may be processed by Google or Anthropic outside Singapore.
When we transfer personal data outside Singapore, we take steps to make sure it is protected to a standard comparable to the PDPA, by relying on each provider’s binding data processing terms.
6. How long we keep it
We keep personal data only as long as we need it for the purpose we collected it for, or as the law requires. These are our periods:
| Data | How long |
|---|---|
| A booking slot held but not confirmed | 1 day |
| Businesses we contacted that did not go further, with their call records and voice notes | 180 days |
| Do Not Call check results | Until the result expires (21 days after the check) |
| Our do-not-contact list | Kept, so that we never contact you again |
| Comments and messages sent to our social media Pages, and our replies | 12 months from when we received them |
| Bookings and prospects who booked a call, enquiry emails | Until the enquiry is closed |
| Applications | For the period needed to decide on them; approved applications are kept with the member’s file |
| Team members’ sign-in records | 12 months |
| Team members’ presence on the team board | 30 days (the latest status stays) |
| Check-ins, coaching notes and records of who viewed a member’s file | For the engagement, then 12 months |
| Practice-call recordings | 30 days |
| Meeting audio | Until it is transcribed |
| Questions to Kai and its answers | 400 days |
| Work chat messages and files | 7 years |
| Email content waiting to be sent | Deleted once it has been sent or has failed |
| Signed contracts, signing evidence, invoices, payments and pay records | For as long as the law requires us to keep them as business, tax and accounting records |
| Our clients’ customers’ data | As the client decides while it is our client; deleted 30 days after the client’s exit window, and from backups within 90 days |
Backups. Our backups are encrypted. After we delete data, it remains in backups until they are replaced: we keep daily backups for 14 days and weekly backups for 8 weeks.
7. Your rights and how to use them
Under the PDPA you may ask us:
- for access to the personal data we hold about you, and how it has been used or disclosed in the past year;
- to correct personal data that is wrong or incomplete;
- to withdraw your consent to our collecting, using or disclosing your personal data. We will tell you what withdrawing means for you (for example, that we can no longer process an application or provide a service) before we act on it;
- to delete your personal data where we no longer need it. For social media data, see our data deletion instructions.
Email dpo@kerdencesystems.com with your request. We may ask you to confirm your identity before we act, so that we do not give your data to someone else. We will respond within 30 days. If we need longer, we will tell you within that time when we expect to respond.
We do not charge for these requests.
If you are not satisfied with our response, you may contact the Personal Data Protection Commission at pdpc.gov.sg.
8. Calls, texts and the Do Not Call Registry
- Before we call or text a Singapore telephone number about our services, we check it against the Do Not Call Registry, for both voice calls and text messages. A check is valid for 21 days; after that we check again. A number registered on the DNC Registry is not called or texted.
- Our team can see a Singapore number only while a current check shows it is not registered.
- If you tell us to stop, by phone, email or reply, we add your number or address to our do-not-contact list and will not contact you again for marketing.
- If someone calls you from Kerdence and you are unsure, ask the caller for their code and check it at kerdencesystems.com/verify. We never ask for passwords, one-time codes, NRIC or passport numbers, or bank details on a call or in a message.
9. Cookies and browser storage
The website kerdencesystems.com sets no cookies. It keeps one entry in your browser’s local storage: your answer to the question “May we count which post or link brought you here?”, so that we do not ask again. Only if you tap Allow do we record the campaign and source tags of the link you arrived by and pass them on to our booking page; nothing else is measured and nothing is shared with advertisers. Our cookie notice explains this in full. The project calculator and the workflow examples run only in your browser.
When you sign a contract on sign.kerdencesystems.com, the page keeps your signing session in your browser tab’s session storage. It is deleted when you close the tab.
10. How we protect it
We protect personal data with access by role, so that each person on our team sees only what their work needs; separation of each client’s data in our database; encryption of stored credentials, keys and backups; sign-in with passkeys for our team; and records of who accessed what. Our application logs are built to record codes and identifiers, not the content of messages or enquiries.
11. Changes to this notice
We will update this notice when what we collect or how we use it changes, and show the new effective date at the top.