Privacy Policy
Effective August 6, 2026
This Privacy Policy explains how CWS OÜ (“Need for Service,” “we,” “us”) collects, uses, and protects information when you visit needforservice.app, request a demo, or use the Need for Service booking and shop-management application (the “Service”). By using our site or the Service, you agree to this policy.
Information we collect
- Information you provide: name, email address, mobile phone number, shop name, and number of bays when you submit our demo booking or contact forms.
- Shop and customer data: when you use the Service, the appointments, customers, vehicles, and settings you and your customers enter into it.
- Google Calendar data: only if you choose to connect a Google Account — see Google Calendar data below.
- Usage data: standard analytics and advertising identifiers (e.g., cookies and the Meta pixel) to understand site traffic and measure marketing.
How we use your information
- To schedule, confirm, and remind you about a demo you requested (by email and, if you provide a mobile number, by text message).
- To respond to your questions and follow up about Need for Service.
- To operate, secure, and improve our website and services.
Google Calendar data
Connecting a Google Account is optional. If you don’t connect one, we never request or receive any Google user data. If you do connect one, this section governs what we do with it.
What we access, and why
- Your calendar list (
calendar.readonly) — so you can choose which one of your calendars to sync. We read events only from the single calendar you select. - Events on the calendar you select (
calendar.events) — to read when you are already committed, so the Service stops offering those times to your customers; and to create, update, and delete an event for each booking you take. - Your Google Account email address (
openid,email) — shown in your settings so you can see which account is connected.
What we store
From the events on your selected calendar we store only what is needed to work out when you are unavailable: the event’s Google identifier, its title, its start and end time, and whether it is an all-day event. We store this only for the period the Service offers bookings in (approximately the next 120 days).
We do not store event descriptions, attendee lists, guest email addresses, attachments, locations, conferencing links, or any other event content. We do not read or store events from any calendar other than the one you select.
We also store the access and refresh tokens Google issues, so the connection can keep working without asking you to sign in again. Tokens and calendar data are held in our database, which is encrypted at rest, and are never shared with anyone else.
What we write to your calendar
When enabled, each booking becomes an event on the calendar you selected, containing the service booked, the customer’s name, the vehicle, and — only if you leave that setting switched on — the customer’s phone number and any notes. The event is updated if the appointment moves and deleted if it is cancelled. If you also switch on technician invitations, the assigned technician’s email address is added to the event as a guest, which causes Google to email them an invitation.
Retention and deletion
Stored calendar data is replaced on every sync, so anything you delete or change in Google stops affecting the Service on the next sync. Disconnecting Google Calendar in your settings immediately deletes all stored calendar data and the tokens we hold for your account. You can also revoke our access at any time from your Google Account permissions page. Events we already created on your calendar remain yours and are left in place; you can delete them in Google.
Limited Use
Need for Service’s use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
Specifically: we do not sell Google user data; we do not use it for advertising of any kind; we do not use it to train generalized artificial intelligence or machine learning models; and we do not allow humans to read it, except with your explicit consent for a support request you have raised, where required for security or to comply with the law, or on data that has been aggregated and anonymized.
SMS / text messaging
We do not sell your information, and we do not share it with third parties for their own marketing.
Mobile information (your phone number and SMS consent) will not be shared with any third parties or affiliates for marketing or promotional purposes. Text messaging originator opt-in data and consent are not shared with any third parties.
If you provide your mobile number when booking a demo, you consent to receive demo confirmation and reminder text messages from Need for Service. Message frequency varies (typically up to four messages per booked demo). Message and data rates may apply. Reply STOP to opt out at any time, or HELP for help. Consent to receive texts is not a condition of any purchase. See our SMS Terms & Conditions.
Service providers
We share information only with vendors that help us operate, and only as needed to provide our service: Google (calendar scheduling and Google Meet), HubSpot (CRM), Twilio (SMS delivery), Square and Stripe (payment processing), Supabase (database hosting), and Vercel (application and website hosting). These providers process data on our behalf and are not permitted to use it for their own marketing. Google user data is never shared with any of them, or with anyone else.
Data retention
We keep your information for as long as needed to provide the demo, the Service, and follow-up, and as required for legitimate business or legal purposes. You may ask us to delete your information at any time. Google Calendar data has its own, shorter retention — see Google Calendar data above.
Your choices
You can opt out of texts by replying STOP, unsubscribe from emails using the link or by replying, and request access to or deletion of your data by emailing us.
Contact
Questions about this policy? Email matteo@needforservice.net.