Privacy policy

Effective date: 20 October 2026

This policy explains how Built Kosher Ltd ("we", "us" or "our") handles personal information for Chip Sync. We are responsible for the personal information processed through this service. Contact us at support@builtkosher.com.

1. What Chip Sync does

Chip Sync connects supported Google Contacts, Google Calendar and Google Tasks information to native apps on your Chip phone. Google sign-in takes place in a browser on a computer or another phone. Connecting Google is optional, and you choose which supported services to authorise.

When you manage Google Sync through Chip Cloud, we also associate the connection with your Chip Cloud account identifier and linked phone identifier. This lets the same account manage Google services and photo backup. Google content is not added to your photo library or stored in the Chip Cloud photo database.

2. Information we access

• Google identity: your Google account identifier and email address, so the service can associate the correct account with your connected phone.
• Contacts, if selected: contact names, nicknames, phone numbers, email and postal addresses, organisations, birthdays, notes, groups, favourites and identifiers needed to read and synchronise contact records.
• Calendar, if selected: your calendar list and supported event details, such as titles, descriptions, locations, dates, times, time zones, recurrence, reminder settings and record identifiers.
• Tasks, if selected: task lists, titles, notes, scheduled dates, completion states and identifiers needed to synchronise changes. The service does not support exact timed Google Tasks reminders.
• Connection and technical information: a generated phone identifier, a hash of the phone's access credential, selected permissions, connection and activity times, short-lived pairing state, and operational status/error information. Requests also necessarily expose network information to our hosting provider. The application uses keyed hashes of IP addresses for short-lived abuse counters.

We never receive your Google password. Contact photos, calendar attachments, conferencing links and dedicated browser-link fields are not provided to the phone by this sync service. Text that you put in a contact, event or task may itself contain personal information or an address; it is handled as record content.

3. Why we use it

We use the information to link your phone to the account you authorise, deliver the services you select, read and apply supported changes in both directions, maintain the connection, show its status, prevent abuse and resolve connection problems. Depending on your actions, synchronising can create, change or delete records in your Google account.

We do not use Google data for advertising, profiling for advertising, data brokerage, credit or lending decisions, or training general-purpose AI or machine-learning models. We do not sell or rent Google user data.

4. Google's Limited Use requirements

Our use and transfer of Google API data follows the Google API Services User Data Policy, including its Limited Use requirements. This applies to Google data and information derived from it.

We limit access and use to the user-facing sync functions you choose and their necessary operation and security. We transfer Google data only to provide those functions with your permission, for necessary security purposes, when required by applicable law, or as part of a business transfer after obtaining your explicit prior consent.

We do not allow people to read your Google record content except with your affirmative agreement to view specific data, where necessary for security or to comply with law, or in another limited circumstance permitted by Google's policy. Support requests do not give us unrestricted permission to browse your Google account.

5. Storage and security

The sync service relays contact, event and task content without retaining those record bodies in its database or application logs. Copies remain in Google and on the phones you connect. Content is processed in the service's memory while a sync request runs; this is not end-to-end encryption that prevents the service from processing the content.

To maintain the connection, we store your Google account identifier and email, encrypted authorisation tokens, phone connection records, selected/granted services, and limited rate-limit and synchronisation metadata. We use HTTPS in transit, encrypt stored Google tokens, and store a hash rather than the phone's access secret. Pairing codes are short-lived and single-use. No security measure guarantees complete protection.

6. Providers and sharing

Google supplies the account and API services you authorise. Cloudflare supplies hosting, network protection and database infrastructure for Chip Sync, and processes information needed to deliver that infrastructure. See Google's privacy policy and Cloudflare's privacy policy for their own processing.

Authorised service providers may process information only for the operation, support and security of the service, subject to applicable obligations and Google's requirements. Processing can involve countries outside your own. Where data-protection law requires safeguards for transfers, we will use the applicable safeguards. We do not share your Google data with unrelated advertisers or data resellers.

7. Retention

Connection records and encrypted Google tokens are kept while your phone is linked and the connection is needed. A pairing code is valid for 10 minutes; expired pairing records are eligible for deletion after 24 hours and are removed by scheduled cleanup. Because cleanup is periodic, deletion is not instantaneous. Abuse counters and expired sync locks are also cleared by scheduled cleanup.

A phone connection with no activity for 180 days is eligible for automatic removal. Disconnecting a phone removes its active connection records and stored Google tokens. Infrastructure recovery copies may retain deleted records for the provider's limited recovery period; such copies are not used for active syncing. We may retain information separately where law requires it or where necessary to investigate a specific security incident, for no longer than needed.

8. Your choices, disconnection and deletion

• Choose the services you authorise on Google's permission screen. We request the permissions needed for the features you select.
• Pause individual services or disconnect the phone. Pausing stops that service's sync; it does not itself revoke the existing Google grant.
• Remove Chip Sync's access through your Google Account connections. This can affect all phones using that Google authorisation.
• Request data deletion for your Chip Sync connection by emailing support@builtkosher.com. State that your request concerns Chip Sync and identify the connected email address. We may verify ownership. Never send your password, pairing code or access tokens.

Disconnecting or deleting a connection does not itself erase your contacts, calendar events or tasks from Google, or copies already saved on a phone. Remove those copies using the relevant Google or phone app if that is what you intend. Where another phone still needs the same Google grant, disconnecting one phone removes its access without intentionally revoking the other phone's grant.

9. Data-protection rights

Depending on applicable law, you may have rights to access, correct, erase, restrict or object to processing of your information, obtain a portable copy, withdraw consent, or complain to a data-protection authority. We use information to provide the service you request, protect its security and comply with law; where consent is required, you can withdraw it. Contact the address above to exercise your rights. Withdrawing permission does not affect processing that was lawful before withdrawal.

10. Cookies and website information

These informational pages contain no advertising or analytics trackers. The linking flow uses a short-lived, secure session cookie to match the Google sign-in response to the browser that started it. It is necessary for secure linking, is cleared when the flow completes and otherwise expires after approximately 15 minutes. The site does not use that cookie for advertising.

11. Children

Chip Sync is not directed to children under 13. Do not connect an account unless you meet the applicable age and authorisation requirements for your Google account and this service. If you believe a child has provided information contrary to these requirements, contact us so we can investigate and remove the connection where appropriate.

12. Changes and contact

We will update the date on this policy when it changes and give appropriate notice of material changes. Before using Google data for a new purpose or accessing an additional kind of Google data, we will update the disclosures and obtain any required permission. Questions and privacy requests: support@builtkosher.com.