Privacy Policy

Last updated: 29 September 2026

This privacy policy explains how BinSync processes personal data when you use this website, sign in, look up a waste collection schedule, subscribe to a calendar feed, connect Google Calendar, leave an email address, or accept optional cookies. BinSync is built as a practical utility: it uses data to provide the service, keep generated calendar feeds working, understand whether the website functions properly, and improve the product.

BinSync only asks for data that is needed for these purposes. Personal data is not sold. Personal data is not used to build unrelated advertising profiles. Where optional analytics or conversion tracking is used, it is only loaded after you have given consent through the cookie banner.

1. Who is responsible for the processing

Ihor Vovk, operating as a sole proprietorship under the registered trade names BinSync and Vovk Systems, is responsible for the processing of personal data described in this privacy policy. The business is registered with the Dutch Business Register under KVK number 42134340.

For questions, requests, or privacy-related concerns, email [email protected]. The postal and correspondence address is Kwikstaartlaan 42, Box C0794, 3704 GS Zeist. The registered establishment address is shielded in the Dutch Business Register.

2. Personal data BinSync processes

Depending on how you use the service, BinSync may process the following categories of data:

  • postcode, house number, and any house number addition needed to find your collection schedule;
  • the waste provider or municipal source connected to your address;
  • calendar feed identifiers, feed settings, address tokens, and technical feed metadata;
  • account and identity data such as a user identifier, email address, first and last name, and profile image when you create an account or use a sign-in provider;
  • your email address, if you choose to provide it for reminders, notifications, or service settings;
  • billing identifiers, the subscribed address label, and subscription status for paid features; Stripe processes the actual card or bank details and BinSync does not store full payment details;
  • technical request data such as IP address, browser type, device information, timestamps, and logs;
  • cookie preferences and optional analytics or conversion events after consent.

BinSync also stores lightweight postcode-to-provider mapping data. This helps route future lookups more efficiently. That mapping is used for service operation and is not intended to create a full personal profile.

3. Why the data is used

BinSync processes data for the following purposes:

  • to identify the correct source for your waste collection schedule;
  • to retrieve, show, generate, and update your personal calendar feed;
  • to keep calendar subscriptions working over time;
  • to send reminders, notifications, or service emails when you have provided an email address;
  • to start, administer, renew, or cancel a paid BinSync subscription;
  • to prevent abuse, troubleshoot errors, and maintain the security and reliability of the service;
  • to measure website usage and advertising conversion performance when optional cookies are accepted;
  • to improve the website, lookup flow, provider coverage, and calendar feed quality.

4. Google services and Google user data

Google is used for two separate, optional features: signing in to a BinSync account and connecting a dedicated Google Calendar. Each feature has its own OAuth client and authorization. Signing in with Google does not give BinSync access to Google Calendar, and connecting Google Calendar is not required to sign in.

If you sign in with Google, Google provides basic identity information to BinSync's authentication provider, Clerk. This can include your Google account identifier, name, email address, and profile image. Clerk uses this information to authenticate you and manage your BinSync session. BinSync receives a Clerk user identifier and the profile details needed to create and operate your account. BinSync does not use the Google sign-in authorization to call Calendar or other Google APIs.

If you choose to connect Google Calendar directly, BinSync redirects you to Google's OAuth consent screen and requests the calendar.app.created permission. This permission allows BinSync to create a separate secondary calendar in your Google account and to view, create, update, and delete events in calendars created by BinSync. It does not grant BinSync access to your primary calendar, other existing calendars, Gmail, contacts, or Google Drive files.

After you authorize the connection, BinSync receives a one-time authorization code and exchanges it for a Google refresh token. BinSync stores the refresh token in encrypted form, together with the identifier of the dedicated Google calendar and the BinSync connection identifiers needed to synchronize it. Short-lived access tokens are requested when a synchronization runs and are not stored. BinSync uses this access only to create the dedicated calendar and keep its waste collection events synchronized with your BinSync schedule.

Google user data is not sold, used for advertising, or used to build user profiles. BinSync does not allow humans to read Google Calendar data. Data may only be processed by infrastructure providers acting on BinSync's behalf where this is necessary to operate and secure the connection.

Disconnecting Google Calendar from BinSync deletes the stored connection, including the encrypted refresh token, and stops future synchronization. The dedicated calendar and its existing events remain in your Google account until you delete them there. You can also revoke BinSync's access in your Google Account settings or contact BinSync to request deletion of stored connection data.

BinSync's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

5. Legal bases

BinSync processes address and calendar feed data because it is necessary to provide the requested service. If you provide an email address, that data is processed to deliver the reminder, notification, or setting-related functionality you requested. Technical logs and security data are processed because BinSync has a legitimate interest in keeping the service stable, secure, and usable.

Optional analytics and conversion tracking cookies are processed on the basis of consent. You can refuse or withdraw that consent without losing access to the core schedule lookup and calendar feed functionality.

6. Sharing data with others

BinSync may send the address details needed for a lookup to the relevant waste provider, municipal source, or supporting integration in order to retrieve collection data. Clerk processes identity and session data as BinSync's authentication provider. BinSync may also use Stripe for payment and subscription processing, alongside hosting, database, email, analytics, and infrastructure providers that process data on behalf of the service.

Personal data is not sold. Personal data is only shared when necessary to provide the service, operate the website, comply with a legal obligation, or protect the service from misuse.

7. Cookies and analytics

The website uses essential cookies and local browser storage where needed to remember technical choices, such as cookie consent. These are necessary for the website to work correctly.

If you accept optional tracking cookies, BinSync may load analytics and conversion tools such as Google Analytics, Google Ads conversion tracking, and PostHog. These tools help understand how visitors use the website, whether advertising leads to schedule creation, and where the product can be improved. You can manage or withdraw optional cookie consent through the cookie controls on the website.

8. Retention

Personal data is kept no longer than necessary for the purposes described in this policy. Address and calendar feed data may be kept while a feed is active or while it is reasonably needed to maintain the service. Email data is kept while reminders, notifications, or related settings are active. Technical logs are generally kept for a limited period needed for debugging, security, and reliability.

Account and identity data is kept while your BinSync account exists. When the account is deleted through Clerk, BinSync removes its synchronized user record, subject to data that must be retained for a legal, security, billing, or dispute-related purpose.

If you ask for deletion, BinSync will delete or anonymize personal data unless it must be kept for a legal obligation, security reason, dispute, or other legitimate purpose.

9. Security

BinSync takes reasonable technical and organizational measures to protect personal data against loss, misuse, unauthorized access, and unlawful processing. No online service can guarantee perfect security, but the goal is to keep the amount of personal data limited and protect it in a way that matches the practical risk.

10. Your rights

You may have the right to request access to your personal data, correction of inaccurate data, deletion of data, restriction of processing, objection to processing, and data portability. You may also withdraw consent for optional cookies at any time.

To make a privacy request, contact BinSync through the contact link above. BinSync may ask for information needed to verify the request and connect it to the relevant calendar feed or email address.

11. Changes to this policy

BinSync may update this privacy policy when the service, integrations, cookies, providers, or legal requirements change. The most recent version is published on this page. If a change is important for active users, BinSync will make a reasonable effort to communicate it clearly.