Privacy Policy – Writly — cold outreach, done for you

1) Who We Are

Writly is operated by X Group Prime LLC, located in Doral, Florida. We provide a call desk platform for service businesses that answers calls, books appointments, sends confirmations, and places follow-up calls.

If you have questions about this Privacy Policy or your data, contact us at hello@writly.io.

2) Information We Collect

We collect the following types of information:

Account information

• Your name, email address, and phone number
• Your business name and company details
• Payment and billing information (processed securely through Stripe)
• Google account email and OAuth tokens, if you connect Google Calendar (see Section 8)

Campaign and call data

• Phone numbers and contact details of prospects you target through campaigns
• Call recordings, call notes, and call outcome data
• Campaign configurations including scripts, target criteria, and offer details

Usage data

• Dashboard activity and feature usage
• Device information, browser type, and IP address
• Pages visited and interactions within the Platform

3) How We Use Your Information

We use the information we collect to:

• Run your call campaigns: execute outbound calls, record results, and deliver reports through your dashboard.
• Maintain compliance: manage do-not-call suppression lists, enforce calling-hour restrictions, and meet telemarketing regulations (including TCPA requirements).
• Process payments: manage subscriptions and billing through Stripe.
• Improve the platform: analyze usage patterns and aggregated data to enhance features, performance, and reliability.
• Communicate with you: send service updates, billing notifications, and respond to support requests.
• Ensure quality: review call recordings for quality assurance and accurate call classification.

4) SMS Disclosures

Writly sends SMS (text) messages to end users (such as homeowners) who provide a mobile phone number during a booking with Writly's AI assistant. Writly is the sender of these SMS messages and the messages are branded as Writly.

When customers book an appointment through Writly's AI assistant — by phone call or through the web chat widget on writly.io — we collect their phone number to send SMS appointment notifications.

These messages include booking confirmations, appointment reminders, payment links, rescheduling or cancellation updates, and other service-related communications.

Message frequency varies based on the user's bookings. Standard message and data rates may apply.

Users can reply STOP to any message to unsubscribe at any time. Users can reply HELP for support.

Consent to receive SMS messages is not a condition of purchase.

For questions about Writly's SMS practices or to request deletion of your phone number, contact us at hello@writly.io.

See the SMS Communications section of our Terms of Service for the full end-user SMS terms.

4A) Phone Number Collection and Use

This section describes how Writly collects, uses, shares, and lets you delete your phone number when you book through Writly's AI assistant.

Collection

Phone numbers are collected during the booking interaction (by phone or through the Writly web chat) for the purpose of sending SMS confirmations, reminders, payment links, and other booking-related messages as described in Section 4.

Use

Your phone number is used to deliver the SMS messages you consented to when booking, to identify you on return visits so your booking history is available, and to support fulfillment of the booking you requested.

No sale or transfer for marketing

We will not share, sell, or transfer mobile opt-in data, SMS consent, or phone numbers with third parties or affiliates for promotional or marketing purposes. All the above categories exclude text messaging originator opt-in data and consent; this information will not be shared with any third parties.

Sharing with the service provider you booked

Your phone number may be shared with the service provider (contractor) you are booking with, solely for the purpose of fulfilling that booking — for example, if the provider needs to contact you about scheduling, access to the service location, or service completion. Any separate communications you receive directly from the service provider are governed by the service provider's own terms and privacy practices, not by Writly's SMS program.

Service providers that process data on our behalf

We also share phone numbers with the infrastructure providers we use to deliver SMS (for example, Telnyx) strictly for the purpose of sending and receiving the messages described in Section 4. These providers are contractually required to protect your data.

Deletion and opt-out

You can request deletion of your phone number at any time by emailing hello@writly.io, or stop further SMS messages immediately by replying STOP to any Writly SMS. Upon a deletion request we will remove your phone number from active records, subject to retention required by law or to honor your STOP request (such as maintaining a suppression list).

5) Call Recordings

Recording of calls placed through Writly

Phone calls placed or received through Writly are recorded. This includes:

• Inbound calls to a Client's Writly number, where Writly answers as that Client's business.
• Outbound calls placed as part of a Client's campaign.

Recordings, transcripts, and call summaries are stored securely in Amazon S3 with encryption at rest and access logging. They are retained for a reasonable period for quality, accuracy, dispute resolution, and Client review purposes.

Disclosure to callers

On inbound calls, Writly's AI may state at the start of the call that the call is being recorded, in compliance with jurisdictions that require all-party consent (including but not limited to California, Connecticut, Florida, Illinois, Maryland, Massachusetts, Montana, Nevada, New Hampshire, Pennsylvania, and Washington). Callers who do not wish to be recorded may end the call at any time.

Client access to recordings

The Client whose Writly number received or placed the call can listen to the recording, read the full transcript, and view a structured summary of every call directly in their Writly dashboard. This includes calls Writly answered on their behalf when they were unavailable. Recordings and transcripts are not shared with any other Client or third party.

Internal access

Within Writly, recording access is restricted to authorized personnel for the purposes listed above (quality, dispute resolution, troubleshooting, and improving the service). Recordings are never sold, used for advertising, or shared with third parties for marketing purposes.

6) We Do Not Sell Your Data

We do not sell, rent, or trade your personal information or your prospect data to third parties. Your data is used solely to provide and improve the Writly service as described in this policy.

7) Third-Party Services

We use the following third-party services to operate the Platform:

• Telnyx: telephony infrastructure for making and managing phone calls. Telnyx may process call data and phone numbers as part of call delivery.
• Stripe: payment processing for subscriptions and billing. Stripe handles your payment card information directly — we do not store your full card details on our servers.
• Google (Calendar, Sign-In): used for optional calendar integration and sign-in. We receive your email address and calendar data only if you connect Google Calendar. See Section 8 for full details. Google's privacy policy.
• Jobber (Getjobber.com): optional scheduling integration for service businesses. We receive your Jobber account information, the calendars/users you select, and the visits we book on your behalf only if you connect Jobber. See Section 8A for full details. Jobber's privacy policy.
• Clover (clover.com): optional point-of-sale integration for restaurant and retail businesses. We receive your Clover merchant identifier, OAuth tokens, live menu (items, prices, modifiers), and order/payment records only if you connect Clover. See Section 8B for full details. Clover's privacy policy.

These providers have their own privacy policies and are contractually required to protect your data. We only share the minimum information necessary for them to perform their services.

8) Use of Google User Data

When you connect your Google Calendar to Writly, we request access through Google's OAuth consent screen. This section explains what Google user data we access, how we use it, how we store it, and how you can revoke access.

Data we access

• Your Google account email address (via the userinfo.email scope), used to identify the connected account and display it in your settings.
• Your calendar list (calendar.readonly), used to let you choose which calendars Writly should check for conflicts.
• Busy times and event data from the calendars you select (calendar.readonly), used to calculate your real availability during phone calls.
• Event creation permission (calendar.events), used to book appointments directly on your primary calendar when a caller agrees to a time.

How we use this data

Writly uses Google user data solely to provide user-facing scheduling features inside the product: reading your availability during calls, proposing open times, and booking appointments on your calendar. We do not use Google user data to train machine-learning models, build advertising profiles, or for any purpose unrelated to the scheduling feature you explicitly enabled.

How we store this data

We store OAuth access and refresh tokens encrypted in our database so Writly can read and write to your calendar on your behalf. We do not copy your full calendar contents into our database; we query Google in real time when needed. Token storage is limited to the tenant that connected the calendar.

Sharing

We do not share, transfer, or sell Google user data to third parties. Google user data is never used for advertising, resold, or passed to human reviewers except where required by law or with your explicit consent to resolve a support issue.

Revoking access

You can disconnect Google Calendar from Writly at any time inside your Writly settings under Scheduling. You can also revoke access directly at https://myaccount.google.com/permissions. When access is revoked, Writly deletes the stored tokens and stops querying Google on your behalf.

Limited Use disclosure

Writly'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.

8A) Use of Jobber User Data

When you connect your Jobber account to Writly, we request access through Jobber's OAuth consent screen. This section explains what Jobber user data we access, how we use it, how we store it, and how you can revoke access.

Data we access

• Your Jobber account name and identifier, used to identify the connected account and display it in your settings.
• The list of users on your Jobber account (read_users), so you can choose which team members' schedules count for conflicts and which user owns new visits.
• Visit and schedule data for the users you select (read_visits, read_jobs), used to calculate your real availability while a call is in progress.
• Client and property records (read_clients, read_properties), used to find an existing client or property that matches the caller before creating a new one.
• Permission to create or update clients, properties, jobs, and visits (write_clients, write_properties, write_jobs, write_visits), used to book the appointment when a caller agrees to a time.

How we use this data

Writly uses Jobber user data solely to provide user-facing scheduling features inside the product: reading your availability during calls, proposing open times, and booking visits into your Jobber account. We do not use Jobber user data to train machine-learning models, build advertising profiles, or for any purpose unrelated to the scheduling feature you explicitly enabled.

How we store this data

We store OAuth access and refresh tokens in our database so Writly can read your schedule and book visits on your behalf. We do not copy your full Jobber dataset into our database; we query Jobber's API in real time when needed. Token storage is limited to the tenant that connected the account, and refresh tokens are rotated on each refresh.

Sharing

We do not share, transfer, or sell Jobber user data to third parties. Jobber user data is never used for advertising, resold, or passed to human reviewers except where required by law or with your explicit consent to resolve a support issue.

Revoking access

You can disconnect Jobber from Writly at any time inside your Writly settings under Scheduling. You can also revoke access directly from inside Jobber under Apps → Connected Apps → Disconnect. When access is revoked through either path, Writly receives Jobber's APP_DISCONNECT webhook, deletes the stored tokens, and stops querying Jobber on your behalf.

Limited use

Writly's use of information received from Jobber's API is limited to providing the scheduling features you enabled and complies with Jobber's Developer Terms and the data-handling commitments described in this Privacy Policy.

8B) Use of Clover Merchant Data

When you connect your Clover merchant account to Writly, we request access through Clover's OAuth consent screen. This section explains what Clover merchant data we access, how we use it, how we store it, and how you can revoke access.

Data we access

• Your Clover merchant identifier and merchant name (read_merchant), used to identify the connected account and display it in your settings.
• Your live inventory: items, prices, categories, and modifier groups (read_inventory), used so the AI receptionist can read your real menu to callers and build orders only from items you actually sell.
• Order data and the ability to create or update orders (read_orders, write_orders), used to place phone-orders into your Clover register so the kitchen sees the ticket.
• Payment records and the ability to create payment-link sessions (read_payments, write_payments), used to send Hosted Checkout pay-links to callers and to confirm when a payment has been received.

How we use this data

Writly uses Clover merchant data solely to provide user-facing phone-order and payment features inside the product: reading your live menu during calls, creating Hosted Checkout sessions, sending the resulting pay-link by SMS to the caller, marking the order as paid in your Writly dashboard when the payment webhook fires, and surfacing the order in your call feed for follow-up. We do not use Clover merchant data to train machine-learning models, build advertising profiles, share with other Writly tenants, or for any purpose unrelated to the phone-order feature you explicitly enabled.

How we store this data

We store OAuth access and refresh tokens in our database so Writly can read your menu and create orders on your behalf; access tokens are short-lived (30 minutes) and refreshed via Clover's rotating refresh-token endpoint. We cache your menu briefly (up to 5 minutes) for performance and invalidate the cache when Clover sends an inventory-change webhook. We do not copy your full Clover dataset into our database; orders, payments, and customer records continue to live in Clover. Token storage is limited to the tenant that connected the merchant account.

Sharing

We do not share, transfer, or sell Clover merchant data to third parties. Clover merchant data is never used for advertising, resold, or passed to human reviewers except where required by law or with your explicit consent to resolve a support issue. Funds collected via Clover Hosted Checkout settle directly into your own Clover merchant account — Writly does not act as a payment processor and does not take a commission on Clover-processed transactions.

Revoking access

You can disconnect Clover from Writly at any time inside your Writly settings under Get Paid → Clover. You can also uninstall the Writly app directly from inside your Clover dashboard under More Tools → Installed Apps → Uninstall. When the Writly app is uninstalled in Clover, Clover sends a DELETE webhook for the A:<appId> object; Writly receives this signal, deletes the stored tokens, and stops querying Clover on your behalf.

Limited use

Writly's use of information received from Clover's API is limited to providing the phone-order and payment features you enabled and complies with the Clover Developer Agreement and the data-handling commitments described in this Privacy Policy.

9) Data Security

We take reasonable technical and organizational measures to protect your information, including encryption of data in transit and at rest, access controls, and secure infrastructure.

However, no method of electronic transmission or storage is 100% secure. While we strive to protect your data, we cannot guarantee absolute security.

10) Data Retention

We retain your account information and campaign data for as long as your account is active or as needed to provide services.

Call recordings are retained for a reasonable period for quality and compliance purposes.

Google OAuth tokens are deleted when you disconnect Google Calendar in Writly or revoke access via your Google account.

Jobber OAuth tokens are deleted when you disconnect Jobber in Writly settings, when you disconnect the Writly app from inside Jobber, or when Jobber sends an APP_DISCONNECT webhook to Writly.

Clover OAuth tokens are deleted when you disconnect Clover in Writly settings, or when you uninstall the Writly app from inside your Clover merchant dashboard (which causes Clover to send an A:<appId> DELETE webhook to Writly). The cached menu is also invalidated at that point.

If you close your account, we may retain certain data as required by law or for legitimate business purposes (such as maintaining do-not-call suppression lists).

11) Your Rights

Depending on your jurisdiction, you may have the right to:

• Access the personal data we hold about you
• Request correction of inaccurate data
• Request deletion of your data (subject to legal obligations)
• Object to or restrict certain processing of your data
• Revoke Google Calendar access by disconnecting in Writly settings or at https://myaccount.google.com/permissions
• Revoke Jobber access by disconnecting in Writly settings or by removing the Writly app inside Jobber under Apps → Connected Apps → Disconnect
• Revoke Clover access by disconnecting in Writly settings or by uninstalling the Writly app inside Clover under More Tools → Installed Apps → Uninstall

To exercise any of these rights, contact us at hello@writly.io. We will respond within a reasonable timeframe.

12) Cookies and Analytics

We may use cookies and similar technologies to remember your preferences, keep you logged in, and understand how you use the Platform.

We use analytics tools to measure site performance and improve the user experience. These tools may collect anonymized usage data.

13) Changes to This Policy

We may update this Privacy Policy from time to time. If we make material changes, we will notify you through the Platform or by email. Continued use of the Platform after changes are posted constitutes acceptance of the updated policy.

14) Governing Law

This Privacy Policy is governed by the laws of the State of Florida, USA. Any disputes related to this policy will be resolved in Florida, USA.

15) Contact Us

If you have questions, concerns, or requests regarding this Privacy Policy or your personal data, please contact us:

X Group Prime LLC DBA Writly

Doral, FL

Email: hello@writly.io