This Privacy Policy explains how Qualify Base (“Qualify Base”, “QualifyBase”, “we”, “us”, or “our”) collects, uses, discloses, stores, and protects personal information when you use our website at https://www.qualifybase.com and the QualifyBase platform, including our web application, our mobile apps for iPhone and Android, APIs, integrations, AI agents, and related services (collectively, the “Service”). It is a notice for you to read; you are not asked to agree to it.
QualifyBase is an AI-powered lead qualification and engagement platform for businesses (primarily dental clinics, health tourism agencies, and service providers) that automatically answers incoming leads across WhatsApp, Instagram Direct, Facebook Messenger, SMS, voice phone calls, and web chat; qualifies them using AI; follows up; books appointments; and hands off qualified leads to human sales representatives.
Data controller / operator:
Qualify Base
16192 Coastal Highway, Lewes, Delaware 19958, United States
Email: info@qualifybase.com
1. Summary of Key Points
- Two categories of users: (a) business customers that subscribe to QualifyBase (“Customers”), and (b) end-users / prospective patients that Customers communicate with via QualifyBase (“End Users” or “Leads”). For Lead data, the Customer is the data controller and QualifyBase is a data processor acting on the Customer's behalf.
- What we collect: account info, contact data, conversation messages, call audio and transcripts, lead qualification data, calendar availability, payment information, and technical usage data.
- OAuth integrations: We use Google OAuth (Google Calendar) and Meta OAuth (Facebook Pages, Instagram, Messenger) strictly to deliver the features you explicitly connect. We request only the minimum scopes required.
- Google API Services User Data: Our use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. See Section 7.
- Meta Platform data: We handle Instagram and Facebook Messenger data in accordance with Meta Platform Terms and Developer Policies. See Section 8.
- We do not sell your personal information. We do not use data received through Google OAuth or Meta OAuth for advertising, and we do not use it to train general-purpose AI/ML models.
- AI transparency: Our AI agents do not claim to be human. They answer honestly when asked whether they are an AI and say they are digital assistants where the rules in Section 6 call for it.
- Messages to you: We send you sign-in codes and service messages, including help with your setup. News about our plans and offers goes out only if you turned it on, and you can turn it off at any time. See Section 10.
- Your rights: You can access, correct, export, or delete your personal information. See Section 15. If you are in Turkey, see also our KVKK Aydınlatma Metni.
- Data deletion: To request deletion of your personal data, follow the step-by-step instructions at https://www.qualifybase.com/data-deletion.
2. Information We Collect
2.1 Information you provide when creating an account
- Mobile phone number (your sign-in, confirmed by a one-time code), password (stored hashed), and optionally your full name, email address, and avatar.
- Business / clinic name, business type, country, preferred language, and the website address you give us.
- What you enter while building your assistant before you have an account: business details, your choices, and your test conversations. This is kept in a draft with a one-way hash of your IP address, used to limit abuse. A draft nobody claims is deleted after 30 days.
- Team member details when you invite colleagues (email, name, role).
- Notification preferences (email, WhatsApp, in-app).
2.2 Information you provide when configuring the Service
- AI agent configuration: agent name, system prompt, goals, required lead fields, working hours, language, voice settings, pricing/behavior rules.
- Knowledge base content: web URLs, uploaded PDFs and documents, FAQ pairs, free-text knowledge blocks.
- Channel credentials and connection tokens (encrypted at rest) for the channels you enable: phone numbers (Twilio), WhatsApp Business, Instagram / Facebook Page connections (via Meta OAuth), Google Calendar connections (via Google OAuth), web chat widget.
- Email mailboxes you connect to send email to leads: the address, its mail server names and an app password (the password encrypted at rest, never shown again). We use them only to send the email you write to leads, to put a copy in your Sent folder, and to read leads' replies to it. Each new message's headers are checked to find those replies; nothing else in the mailbox is opened or stored. Removing the mailbox deletes the password.
- Market declarations: the countries each AI agent serves.
- Compliance confirmations: the wording a member of your team confirmed (for example, that you hold consent to contact a list), their name and user identifier, the time, and what it related to.
- Billing information (processed by Stripe; see Section 3).
2.3 Lead / End-User data processed on behalf of Customers
When a lead contacts a Customer through a channel connected to QualifyBase, or when a Customer uploads or imports leads, we process the following on the Customer's behalf:
- Contact details: name, phone number (normalized to E.164 format), email address, city, country, preferred language.
- Interest / intent data: requested treatment, service, budget, timeline, and any other fields the Customer configures.
- Message content: full text of inbound and outbound messages across all enabled channels (WhatsApp, Instagram DM, Facebook Messenger, SMS, email, web chat).
- Voice data: audio recordings and transcripts of inbound and outbound phone calls, call duration, call status, call metadata.
- Media attachments: photos (including dental/oral photos), documents, and other files that leads send.
- AI-generated data: lead scores, scoring rationales, AI overviews, conversation classifications, and suggested follow-ups.
- Appointment data: scheduled date/time, duration, timezone, notes, status (confirmed, cancelled, rescheduled, completed, no-show), and associated calendar event IDs.
- Behavioral metadata: conversation state, timestamps, reply windows (including the Instagram/Messenger 24-hour messaging window), follow-up history, delivery status.
Customers are responsible for (a) obtaining any legally required consent from Leads before communicating with them via QualifyBase, (b) giving any notices the law requires beyond the AI disclosures described in Section 6 (for example, notices about call recording and about the Customer's own data processing), and (c) having a lawful basis to upload or process Lead data. Leads should direct requests about their data to the business that contacted them; we will help that business respond.
2.4 Information collected automatically
- Log data: IP address, browser type and version, operating system, device type, referring pages, pages visited, date/time of requests, error traces.
- Authentication cookies and session tokens (HTTP-only, strictly necessary) managed via Supabase Auth.
- Security events: login attempts, failed logins, session activity.
- Product usage: features used, buttons clicked, routes visited, and the steps of sign-up you completed, to help us improve the Service.
- How you found us: if you arrive from a link or an ad, the landing page, referring page, campaign and ad names and identifiers, and advertising click identifiers (such as gclid and fbclid). We keep them with your workspace to see which sources bring customers.
2.5 Information collected from third parties
- Google (if you connect Google Calendar): free/busy availability, calendar event metadata (summary, date/time, attendees you add) — used solely to read availability and create/update appointment events you explicitly trigger. See Section 7.
- Meta (Facebook / Instagram) (if you connect a Page / IG account): Page id and name, Instagram business account id, inbound DMs, Messenger conversations, sender user ids, and message metadata — used solely to deliver and respond to messages through the channels you explicitly connect. See Section 8.
- Stripe: subscription status, payment method type, billing country, invoice status. We do not receive full card numbers.
2.6 Records of your choices
When you accept our Terms, are shown a required notice, or turn optional contact on or off, we record what you chose, the wording and its version, the time, the page, your language, and the country of your number. We keep these records as evidence. See Section 12.
2.7 The QualifyBase mobile app
The QualifyBase app for iPhone and Android shows the same workspace as the web application, and what you do in it is processed as described in this policy. In addition, the app:
- Records, for your account, the type of phone (iPhone or Android), the sign-in session it uses and when you signed in. We use this only to keep your account signed in on one phone at a time; signing in on another phone, or signing out, replaces or removes it.
- Keeps your sign-in on the phone in its secure storage (the iOS Keychain or Android Keystore), and your appearance and language choices on the phone only.
- Asks whether it may send you notifications. We do not currently collect a notification token from your phone.
- Does not access your contacts, photos, camera, microphone or location, and contains no advertising or third-party tracking code.
You cannot create an account, change your password, manage settings or pay in the app; these stay on the web application.
3. Third-Party Services / Sub-processors
We rely on carefully selected sub-processors to deliver the Service. Each sub-processor is contractually bound to protect personal information and to process it only in accordance with our instructions.
| Sub-processor | Purpose | Categories of data | Location |
|---|---|---|---|
| Supabase, Inc. | Primary database (PostgreSQL), authentication, object storage for media files | Account data, contacts, messages, transcripts, images, audio recordings, documents | EU / US (region dependent) |
| Render Services, Inc. | Web application and background worker hosting, cron job execution | HTTP request logs, deployment logs, job metadata | United States |
| ElevenLabs, Inc. | Conversational AI voice agent, speech-to-text, text-to-speech, WhatsApp relay | Conversation transcripts, call audio, lead variables (name, phone, interest) | United States |
| Twilio, Inc. | Phone number provisioning, voice call routing, SMS delivery, sign-in codes by text | Phone numbers, SMS content, call metadata | United States |
| Verimor | SMS delivery and telephony in Turkey, where it is the connected provider | Phone numbers, SMS content, call metadata | Turkey |
| Anthropic, PBC (Claude API) | AI lead scoring, call summarization, conversation analysis, reading business websites during setup | Conversation transcripts, lead metadata used for scoring, public website content | United States |
| Google LLC (Gemini API) | Generating AI agent text replies, transcribing voice messages, describing images, knowledge search | Conversation messages, voice messages, images, knowledge base content | United States / Global |
| Google LLC (Google Workspace) | Sending service email to Customers | Email addresses, message content | United States / Global |
| Resend | Sending email to Leads on a Customer's behalf | Email addresses, message content, attachments | United States |
| Meta Platforms, Inc. | Instagram Direct, Facebook Messenger, WhatsApp Cloud API, sign-in codes on WhatsApp | Messages, phone numbers, sender ids, page / IG account metadata, access tokens | United States / Global |
| Google LLC | Google Calendar API for appointment scheduling | Free/busy slots, calendar event details, refresh/access tokens | United States / Global |
| Stripe, Inc. | Billing and payment processing | Business name, billing email, payment method, usage metrics | United States |
If you connect another service to your workspace, such as Shopify, Pipedrive, Make, Zapier, DigiDentis, or a telephone system, we send it the data that connection is for, on your instruction. Google Analytics and Meta receive data only as described in Section 11, as independent providers of those services. A current list of sub-processors is available from info@qualifybase.com upon request.
4. How We Use Information
- To provide, operate, and maintain the Service, including routing messages, placing and receiving calls, running AI agents, scoring leads, and creating appointments.
- To authenticate users, protect accounts, and enforce access controls.
- To send Customers sign-in codes and messages about their account, billing, security, and support, and, only if they turned it on, the optional contact described in Section 10.
- To understand which pages, campaigns, and ads bring customers, as described in Sections 2.4 and 11.
- To process payments and manage subscriptions.
- To improve, test, and monitor the Service, including debugging, error tracking, and product analytics performed on aggregate or pseudonymized data.
- To comply with legal obligations, enforce our Terms of Service, prevent fraud, and protect the rights, safety, and property of Qualify Base, Customers, and End Users.
We do not: (a) sell personal information; (b) use data obtained via Google OAuth or Meta OAuth for advertising; (c) use Customer or Lead data to train general-purpose AI or ML models; or (d) share Lead data with any party except the sub-processors listed in Section 3, strictly for the purposes stated.
5. Legal Bases for Processing (EEA / UK)
- Performance of a contract — to provide the Service you requested, including sign-in codes and service messages.
- Legitimate interests — to secure, improve, and support the Service, to prevent abuse, and to see which sources bring customers through our own records.
- Consent — for the optional contact in Section 10 and the analytics and marketing cookies in Section 11, and where the Customer has obtained consent from its Leads. You can withdraw consent at any time; withdrawing does not affect what was done before.
- Legal obligation — to comply with applicable laws and lawful requests, including duties to inform people that they are interacting with an AI system.
- Legal claims — keeping compliance records as necessary to establish, exercise, or defend legal claims, which is also our legitimate interest.
6. AI and Automated Processing
QualifyBase uses large language models and conversational AI to respond to leads, classify conversations, extract structured data, and generate lead scores. Specifically:
- ElevenLabs Conversational AI is used to generate voice agent responses, transcribe calls, and relay text conversations. The full conversation (messages and/or audio) is sent to ElevenLabs only for the duration of the active session or to produce post-call transcripts.
- Google Gemini is used to generate AI agent text replies, transcribe voice messages, describe images that people send, and search knowledge base content.
- Anthropic Claude is used to score leads (interest, qualification, urgency, engagement, buying signal), summarize calls, and extract contact fields. Only the data necessary for the scoring task is sent (e.g. the most recent ~50 messages of a conversation and the agent's goals).
- We use these vendors through their commercial API services and do not authorize them to use QualifyBase Customer or Lead data to train their foundation models.
Telling people they are talking to an AI. Our AI agents do not claim to be human, and they answer honestly when a person asks whether they are an AI. An agent also says it is a digital assistant in its first message or spoken line where the country we associate with the person is one where we apply that rule (currently the European Union, the European Economic Area, the United States and its territories, South Korea, and China), or where we cannot determine the country and the Customer's declared markets do not exclude those countries. We determine the country from the country recorded for the Lead and the country code of their phone number. We log when a disclosure is made and when a person asks, with the country it was based on. Customers can arrange for a person to take over a conversation, and an agent will offer this when asked.
Compliance records. When a member of a Customer's team confirms something in the Service, such as holding the consents the law requires to contact a list of people, we record who confirmed, when, the wording, and what it related to.
Automated decisions. Lead scores and classifications help a Customer's team decide whom to contact first. They are not intended to produce legal or similarly significant effects on a person, and a Customer's team can review them. Where the law requires it, Customers must tell Leads that calls may be recorded or transcribed.
7. Google User Data (Google OAuth & Limited Use)
QualifyBase'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.
7.1 Scopes we request
https://www.googleapis.com/auth/calendar.calendarlist.readonly— to list calendars you can write to so you can choose which calendar to connect, and identify the connected account from its primary calendar.https://www.googleapis.com/auth/calendar.events.freebusy— to read busy time windows on your selected calendar, including a shared calendar you can access, so QualifyBase can offer available appointment times without reading existing event details.https://www.googleapis.com/auth/calendar.events— to create, update, and delete events corresponding to appointments booked through QualifyBase on your selected calendar, including shared calendars where you have write access.
Read-only event access cannot create or change appointments. Access limited to calendars you own would exclude shared business calendars, and access limited to app-created calendars would exclude your existing calendars. Although the event permission allows broader access, QualifyBase uses it only to manage its own appointment events; it does not list or retrieve the contents of unrelated events. Earlier connections may also include https://www.googleapis.com/auth/calendar.freebusy; new connections use calendar.events.freebusy instead. We do not request calendar.readonly or full calendar access.
7.2 How we use Google user data
- Read calendar identifiers, names, and the primary-calendar indicator to display the calendar picker, and store the connected account email obtained from the primary calendar identifier.
- Read free/busy availability from the calendar you explicitly connected, to show available appointment slots.
- Create calendar events when a lead books an appointment through QualifyBase. Depending on the appointment, we send Google the title, date/time, timezone, duration, lead name, phone number, and appointment notes or service interest. When online appointments are enabled, an event may also include an attendee email and a Google Meet link. Details sent to Google are subject to the calendar's sharing settings and, when guests are invited, are visible to those guests.
- Update or cancel those events if the lead reschedules or cancels.
- Use availability and appointment results in the scheduling features you enable. Google user data, including derived or aggregated data, is used only to provide or improve these user-facing features in accordance with the Limited Use requirements.
7.3 How we store Google user data
- OAuth access tokens and refresh tokens are stored encrypted at rest in our database (Supabase) and are used only to call the Google Calendar API on your behalf.
- We store the connected account email, selected calendar identifier, appointment-to-Google-event mappings, and connection and sync status. For online appointments, a returned Google Meet link may be stored with the appointment.
- Busy-window start and end times are stored as availability blocks and refreshed during sync. We do not retrieve or store the titles, descriptions, or attendees of unrelated calendar events.
7.4 How we share Google user data
We do not sell or rent Google user data or use it for advertising. We transfer Google user data to the sub-processors listed in Section 3 only as necessary to provide the scheduling features you enable, such as hosting and storing the connection and availability data or processing scheduling tool results during an assistant interaction. We do not use raw, derived, aggregated, or anonymized Google user data to train generalized AI/ML models, or transfer it to third-party AI/ML services for that purpose. Our use and transfer of that data adheres to the Google API Services User Data Policy, including the Limited Use requirements.
7.5 Revoking access
You can disconnect a calendar in the QualifyBase dashboard under Settings → Integrations → Google Calendar → Disconnect. To revoke the Google authorization itself, remove QualifyBase directly at https://myaccount.google.com/permissions. Disconnecting removes the stored connection, OAuth tokens, synced Google availability blocks, and appointment-to-Google-event mappings from our primary database, preventing future sync using that connection. Events already created in Google Calendar remain in your Google account, where you can manage or delete them. Local appointment records, including any saved meeting links, follow the retention and deletion rules in Section 12; you can request their deletion using the instructions in Section 15. The security measures in Section 13 also apply to Google user data.
8. Meta Platform Data (Facebook / Instagram / Messenger)
QualifyBase integrates with Meta Platforms to let Customers respond to messages from their Instagram Business accounts and Facebook Pages. This integration is governed by Meta's Platform Terms, Developer Policies, and applicable Messenger & Instagram Graph API policies.
8.1 Permissions we request
pages_show_list— to list the Facebook Pages you manage so you can select one to connect.pages_manage_metadata— to subscribe the selected Page to webhook events so we can receive incoming messages.pages_read_engagement— to read the connected Page's basic profile and engagement metadata needed to operate the integration.pages_messaging— to send and receive Facebook Messenger messages on the connected Page.business_management— to list the Pages owned by your Meta Business portfolio so Business-owned Pages appear in the connect flow.instagram_basic— to identify the Instagram Business account linked to the connected Page.instagram_manage_messages— to send and receive Instagram Direct messages on the connected account.instagram_manage_comments— to read comments on the connected account's own posts and reels, reply to them publicly, and send the commenter a private reply (Direct message) when the Customer has configured an automation for that post.
8.2 How we use Meta platform data
- Receive incoming Messenger and Instagram Direct messages in real time.
- Generate and send responses from the Customer's AI agent or human reps, within the 24-hour standard messaging window imposed by Meta.
- After the 24-hour window, we only send messages that comply with Meta's messaging rules (e.g. using the
HUMAN_AGENTtag where permitted and explicitly triggered by a human). - Display incoming conversations in the Customer's dashboard and unified inbox.
8.3 How we store Meta platform data
- Page access tokens and Instagram user access tokens are stored encrypted at rest.
- Message content, sender identifiers, and timestamps are stored in the Customer's isolated database tenant (protected by row-level security).
- Media attachments (images, voice notes) sent via Messenger/Instagram are downloaded and stored in Supabase object storage so the Customer can reference them later.
8.4 How we share Meta platform data
We do not sell Meta platform data. We do not use Meta platform data for advertising. We do not use Meta platform data to train general AI/ML models. Meta platform data is shared with sub-processors (Section 3) only as strictly necessary to deliver the Service — for example, passing message text to ElevenLabs or Anthropic to generate an AI reply to the lead.
8.5 Revoking access
You can revoke QualifyBase's access to your Meta Pages / Instagram at any time from the QualifyBase dashboard (Setup → Channels → Disconnect) or from your Facebook Business Integrations page at https://www.facebook.com/settings?tab=business_tools. When you disconnect, we stop making API calls and delete the stored OAuth tokens.
8.6 User data deletion instructions (Meta requirement)
To request deletion of data QualifyBase has received from Meta platforms about you, see our dedicated Data Deletion Instructions page. In summary: disconnect the integration as described above and email info@qualifybase.com from the email address associated with your account with the subject “Data Deletion Request”. We will delete all associated data within 30 days and confirm deletion.
QualifyBase also implements Meta's automated Data Deletion Callback at https://www.qualifybase.com/api/webhooks/meta/data-deletion. When a user triggers the “Remove QualifyBase” flow from their Facebook or Instagram settings, Meta sends a signed request to this endpoint, we verify the signature with our App Secret, generate a confirmation code, and return a URL where the user can check the status of the deletion.
9. WhatsApp Business Data
When a Customer connects WhatsApp Business (either directly via Meta's WhatsApp Cloud API or via ElevenLabs' WhatsApp relay), QualifyBase processes inbound and outbound WhatsApp messages on the Customer's behalf. Message content, sender phone numbers, timestamps, and any media attachments are stored in the Customer's tenant. WhatsApp data is handled in accordance with Meta's WhatsApp Business Policy and is subject to the same confidentiality, non-advertising, and no-ML-training commitments described in Sections 7 and 8.
10. Messages and Calls to You
This section is about messages QualifyBase itself sends to you as a Customer. Messages sent to Leads are covered by Section 2.3.
- Sign-in codes. When you ask for a one-time code, we send it to your number by WhatsApp or by text message. We use your number for this as part of providing the Service.
- Service messages. Security, billing, and service notices; help with your setup by WhatsApp or by phone; and the confirmation and reminders for a call you book with us, which may include a call to confirm it. They do not promote anything.
- A demo call you ask for. If you ask for a demo call on our website, we read the website address you gave us to prepare the assistant, and our AI assistant calls the number you verified there, once, using an AI-generated voice. We do this to answer your request. The assistant tells you it is an AI as described in Section 6, and the call may be recorded and transcribed.
- Optional contact. Only if you turned it on with its own box at sign-up or under Settings → Your account: messages by WhatsApp and SMS and calls, including automated and AI-voice calls, about our plans and offers. It is not required to use the Service. Our AI assistant tells you it is an AI as described in Section 6, and calls may be recorded and transcribed. You can turn this off at any time in the same place, by following the instructions in the message, or by writing to info@qualifybase.com.
- United States and Canada. The only text messages we send to your number are the sign-in codes you ask for. We do not offer the optional contact on these numbers. Our AI assistant calls them only for a demo call you ask for.
Text messages (SMS)
Messages are sent by QualifyBase through Twilio or, in Turkey, Verimor (see Section 3). Message frequency depends on how often you ask for a code. Message and data rates may apply. You can opt out at any time by replying STOP and get help by replying HELP.
We do not sell or share mobile numbers, SMS opt-in data, or related personal information with third parties or affiliates for marketing or promotional purposes.
11. Cookies and Similar Technologies
Always on, because the Service needs them:
- Sign-in cookies issued through Supabase Auth, which keep you signed in, for the life of your session.
qb_draft: links your browser to the assistant you are building before you have an account (30 days).- Your language (
qb_locale,qb_ui_locale; one year), your cookie choice (qb_consent; about six months), and short-lived security and connection cookies used while you connect an account or switch between branches.
Set when you arrive through a tracked link:
qb_acq: the first-party record of how you found us described in Section 2.4 (30 days).aff_ref: the partner who referred you, if you came through a partner link (30 days).
Only if you accept them in the cookie banner:
- Analytics (Google Analytics):
_gaand related cookies, on our public pages, to measure visits. - Marketing (Meta Pixel):
_fbpand_fbc, on our public pages, to measure and improve our advertising. - Purchase events: if you accepted the relevant cookie and later start paying, we tell Google the plan, price, and a workspace identifier, and tell Meta the plan, price, a one-way hash of your email address and of a workspace identifier, your IP address and browser details, so they can measure our advertising.
Until you choose, Google's tag runs on those public pages in a restricted mode that sets no analytics or advertising cookies, though Google may still receive a cookieless signal that a page was opened. The Meta Pixel does not load unless you accept marketing. These tags never run in the dashboard or on pages embedded in other websites. You can change your choice at any time through the “Cookie settings” link in the footer of our pages. We do not operate an advertising network and we do not sell your personal information.
12. Data Retention
- Account data is retained for as long as the Customer has an active subscription, and for up to 90 days after termination to allow reactivation, unless the Customer requests earlier deletion.
- Lead / contact data, messages, transcripts, and recordings are retained for as long as the Customer keeps them in the Service. Customers may delete individual contacts, conversations, or call recordings at any time from the dashboard. Deleted items are purged from primary storage immediately and from backups within 30 days.
- OAuth tokens (Google, Meta) are retained until the Customer disconnects the integration or the Customer's account is deleted, after which they are purged.
- Billing records are retained as required by applicable tax and accounting laws (typically 7 years).
- Security logs are retained for up to 12 months.
- Compliance confirmations and records of your choices (Section 2.6) are retained during the Customer relationship and for up to six years afterwards, as necessary to establish, exercise, or defend legal claims, including after your account is deleted.
- Drafts that no account claims are deleted after 30 days.
13. Security
- All data is transmitted over TLS 1.2+ (HTTPS).
- Data is encrypted at rest in our database and object storage.
- OAuth access and refresh tokens and other channel credentials are encrypted with application-layer encryption before being persisted.
- Multi-tenant isolation is enforced at the database level via PostgreSQL row-level security (RLS), so a Customer can only access its own organization's data.
- Role-based access control separates admins from sales reps within a Customer organization.
- We enforce least-privilege access for employees and require strong authentication for internal tooling.
- We maintain backups and a documented incident-response procedure.
No system is perfectly secure. If we become aware of a personal data breach affecting your information, we will notify you and the appropriate regulators as required by applicable law.
14. International Data Transfers
QualifyBase is operated from the United States. Your information may be processed in the United States, the European Union, and other countries where our sub-processors operate. Where we transfer personal data from the EEA, UK, or Switzerland to a country that has not been recognized as providing adequate protection, we rely on appropriate safeguards such as the European Commission's Standard Contractual Clauses. For people in Turkey, see our KVKK Aydınlatma Metni.
15. Your Rights
Depending on your location, you may have the following rights regarding your personal information:
- Access — obtain a copy of your personal data we hold.
- Rectification — correct inaccurate or incomplete data.
- Erasure (“right to be forgotten”) — request deletion of your data.
- Restriction — limit how we process your data.
- Objection — object to processing based on legitimate interests.
- Portability — receive your data in a structured, machine-readable format.
- Withdraw consent — where processing is based on consent.
- Lodge a complaint with your local supervisory authority.
To exercise any of these rights, email us at info@qualifybase.com. If your account has no email address, write from any address and give the number on your account; we will confirm the request by a message to that number. You can withdraw the optional contact yourself under Settings → Your account. If you are an End User / Lead, please direct your request to the business that contacted you; we will support that business in fulfilling your request.
Data deletion requests: For detailed, step-by-step instructions on how to request deletion of your personal data — including data received from Meta platforms (Facebook, Instagram, Messenger, WhatsApp) — please visit our dedicated Data Deletion Instructions page at https://www.qualifybase.com/data-deletion. We process all valid deletion requests within 30 days.
California residents (CCPA / CPRA): You have the right to know the categories of personal information we collect, use, disclose, and sell (we do not sell), the right to delete, the right to correct, the right to limit the use of sensitive personal information, and the right not to be discriminated against for exercising these rights.
16. Children's Privacy
QualifyBase is not directed to children under 16, and we do not knowingly collect personal information from children. If you believe a child has provided personal information to us, please contact info@qualifybase.com and we will promptly delete it.
17. Changes to This Policy
We may update this Privacy Policy from time to time. Material changes will be announced in the product, by email, or to the number on your account before they take effect. The “Last updated” date at the top indicates when the policy was last revised. Continued use of the Service after the effective date does not change any choice you have made under this policy.
18. Contact Us
For any privacy-related questions, requests, or concerns, please contact:
Qualify Base
16192 Coastal Highway, Lewes, Delaware 19958, United States
Email: info@qualifybase.com