This policy explains the information Relacent handles, the purposes and recipients, retention and deletion, and how to exercise applicable privacy rights. It distinguishes records we process for a service business from information we use to administer Relacent.
1 Who we are and what this policy covers
Relacent LLC is a Virginia limited liability company that provides software for service businesses. This Privacy Policy describes how we handle personal information through relacent.com, app.relacent.com and other Relacent-hosted interfaces, our support channels, calls and texts with Relacent itself, and customer-facing booking, quote, and payment pages that link to this policy.
When a business uses Relacent to manage its customers, workers, properties, and services, that business generally determines why those records are collected and how they are used. We process those records on its behalf under our agreement, its instructions, and the Relacent Data Processing Addendum where applicable. The business is responsible for its own privacy notices and practices. We separately determine how information is used for our own account administration, subscription billing, security, and support. Section 3 explains the limited anonymous-statistics use; it does not turn identifiable customer records into Relacent’s property.
2 Information we collect
The information we receive depends on how you interact with Relacent and which features a business enables.
Account and business information. This includes names, business names, email addresses, telephone numbers, account identifiers, authentication information, workspace memberships, permissions, subscription choices, and information provided to support.
Customer Content. Businesses and their authorized users may provide customer and contact details, property addresses, inquiry notes, estimates, quotes, jobs, appointments, schedules, crew and equipment assignments, visit records, communication preferences, invoices, receipts, and related history. Customer Content also includes files, photographs, PDFs, imported lists, messages, and other information submitted to or stored in their workspaces.
Public interactions. When you request an appointment, respond to a quote, make a payment, or send information to a service business through Relacent, we receive the information entered in that process and records of the interaction. The relevant business can access information submitted to it.
Booking a call with Relacent. If you book a call with us at relacent.com/book, the scheduling form is provided by HubSpot, Inc. and shown in a frame on that page. HubSpot collects the details you enter there, such as your name, email address and any notes, and the time you choose, and makes them available to us so we can hold the call and follow up about Relacent. HubSpot handles this information under its privacy policy at https://legal.hubspot.com/privacy-policy. No HubSpot tracking or advertising code runs on our pages, and booking a call does not sign you up for marketing emails.
Billing and transaction information. Stripe processes payment-card entry through its hosted payment interfaces. Relacent receives the account and connected-business identifiers, subscription and invoice details, transaction amounts and currency, payment and refund status, and limited payment-method information needed for the enabled integration, such as card brand, last four digits and funding type (for example, prepaid) where supplied, and a card identifier used only for the free-trial eligibility check in Section 3. Do not put full card numbers, security codes or bank credentials into notes, messages or uploads.
Technical and operational information. We and our infrastructure providers receive information such as IP addresses, browser and device characteristics, request times, errors, and security events. Internal operational monitoring may also record account or workspace identifiers, affected features, response times, API request counts, consumption, usage limits, and associated costs. Cookies and browser storage may maintain sessions, remember preferences, or retain form drafts. See Section 6 for further disclosures.
Messaging information. For enabled SMS and email features, we process sender and recipient details, message content, delivery and failure events, replies, preferences, opt-out requests and evidence of consent. Delivery or provider acceptance does not establish that a person read a message.
AI receptionist calls. When a business turns on Relacent’s AI receptionist, calls to that business’s receptionist number are answered by an automated AI voice agent. For those calls we process the caller’s telephone number, the call audio, a recording of the call, a written transcript, an automatically generated summary, the details the caller gives (such as name, address, service needed and preferred time), call times and duration, and technical call records from the telephone carrier. Texts sent or received in connection with a call are covered by “Messaging information”.
Calls and texts with Relacent. When you call or text Relacent itself, for example to ask about Relacent or book a demo, we process your telephone number, what you tell us, call and message records and, where the call is answered by Relacent’s own AI receptionist, the recording, transcript and summary described above. We use this information to answer you, follow up on your request and keep records of the conversation.
We receive information directly from you, from the business or workspace that authorizes your access, from activity on the service, and from integrations you or that business authorizes. Please do not upload information that you do not have permission to provide.
3 How we use information
We use information to provide the features you request; maintain accounts and access permissions; process subscriptions and enabled transactions; support customers; troubleshoot errors; protect the service against fraud, abuse, and unauthorized access; and meet legal obligations.
For Customer Content, this includes carrying out the business’s instructions to organize records, import files, schedule work, create documents, provide customer-facing pages, and transmit authorized communications. We do not treat the presence of a person’s information in a workspace as consent to unrelated marketing.
For the AI receptionist, we use call and message information to answer the call, respond to the caller, create the transcript and summary, record requests and bookings in the business’s workspace, transfer calls, send texts the caller agreed to, write replies to customers’ texts when the business turns that on, measure usage for billing, and keep the service secure. We do not use the AI receptionist to make outbound or marketing calls.
We use technical and operational information to identify critical errors, diagnose reliability problems, monitor API usage and costs, enforce usage limits, and protect the service. These are the purposes of our internal operational analytics. We use contact information to communicate about accounts, security, billing, and support. Relacent does not currently send marketing emails. If we start sending them to account holders, each will include a working unsubscribe link, and unsubscribing will not stop the account, security, billing and service messages that running your account requires. Messages that a service business directs through Relacent are separate from Relacent’s own communications.
Free-trial eligibility. Each business may receive one free trial of a paid plan. To enforce this, when a trial starts we keep a limited fraud-prevention record of one-way keyed hashes (scrambled codes that cannot be turned back into the original details) of the payment-card identifier supplied by Stripe, the account owner’s email address, the business telephone number and, if texting is set up, the business’s federal tax identification number (EIN). We compare these codes only to decide whether a new trial request comes from a business, card or contact that has already received a trial. A match does not prevent subscribing; it means a paid plan starts without a free trial, as shown before you confirm. The record is not used for marketing, analytics, sale or any other purpose. Section 8 explains how long it is kept. If you believe a match is wrong, contact support@relacent.com.
Anonymous industry statistics. Where our customer agreement and applicable law permit it, we may create, retain, publish, license, or sell aggregated industry statistics, such as broad regional price ranges, job-duration benchmarks, and seasonal demand trends. This describes an authorized potential use, not a claim that Relacent already sells a statistics product. “Anonymous Industry Statistics” means aggregated statistical information derived from permitted service data that meets applicable legal standards for deidentified or anonymous information and cannot reasonably identify, be linked to, or reveal confidential information about any individual person, household, or Business Customer, including by combination with other reasonably available information. Removing names, substituting account numbers, hashing identifiers, or keeping a reidentification key does not by itself meet this definition.
Relacent will use reasonable technical and organizational measures to prevent identification, including removing identifiers, grouping information at a sufficiently broad level, and suppressing small groups, outliers, or combinations that could expose a person or business. We will not attempt to reidentify qualifying statistics. We will require recipients to maintain those protections, prohibit reidentification and identifying combinations, restrict onward disclosure accordingly, and exercise reasonable oversight of compliance. Statistics that fail these safeguards must not be sold or disclosed as anonymous.
We do not sell identifiable workspace records or identifiable subscriber contact information as a data product. Until data satisfies the anonymity safeguards, it remains subject to all applicable personal-data and confidentiality restrictions. Creating statistics must itself be lawful; this policy does not replace required notices, permissions, or consent, authorize an incompatible secondary use, or expand AI-training rights.
4 AI and future changes in data use
Relacent does not currently use Customer Content or customers’ personal information to train or fine-tune AI models. This describes our current practice rather than a permanent commitment that we will never offer a training-related use.
AI features. When a business uses Relacent’s AI features, such as the assistant, quote drafting, follow-up messages and visit reports, the records, notes and photos needed for that request are sent to our AI-model provider, Anthropic, to produce the result. Anthropic’s commercial terms do not allow it to train models on that information. It deletes it within 30 days, except content flagged under its usage policy, which it may keep for up to 2 years, or where the law requires. Results are shown to the business’s users, who are asked to review them before sending or relying on them.
AI receptionist. Calls and texts handled by the AI receptionist are processed by AI models operated by our providers, listed in the Provider and Subprocessor List. The receptionist tells callers at the start of each call that it is an AI and that the call is recorded. Relacent does not use call recordings, transcripts, summaries or messages to train AI models. Our voice-agent provider, Retell AI, states that the AI-model, speech and voice providers it uses are contractually barred from training on this information, and that Retell itself may use de-identified or aggregated information to improve its own products, including its models. We set Retell to delete recordings, transcripts and logs about 10 minutes after each call, keeping only basic call details, which limits what Retell holds for any such use. AI-generated replies and summaries can contain mistakes; businesses are asked to check bookings and details before relying on them.
If we introduce AI training that uses customer information, we will first explain the information involved, its purpose, the parties that receive it, and the choices available. We will obtain any permissions, consent, or contractual amendments required by applicable law and our commitments before that use begins. Updating this policy alone does not authorize a materially incompatible use of previously collected information.
Using a model to process information for a requested feature is different from training a model. This policy does not grant unrestricted training rights. Some providers separately process information for their own disclosed purposes, including security or service improvement, as described in the provider list and for Cloudflare in Section 7. Their roles and practices must be assessed for the services we enable.
5 When information is disclosed
Within the relevant workspace and customer interaction. Authorized business users can access records according to their permissions. Information may also be disclosed to recipients chosen by the business, including through messages, exports, and customer-facing links. Businesses should manage access and sharing carefully.
To providers that help operate the service. The Relacent Provider and Subprocessor List identifies the providers used for enabled features, the information involved, their functions, processing locations and applicable retention schedules. Providers acting on our behalf are subject to written data-protection restrictions. Some services also process limited information as independent controllers under their own notices. Listing a provider does not give it access to every workspace or authorize an unrelated use. For AI features, this includes the AI-model provider; for the AI receptionist, the voice-agent provider that runs the call and writes text replies, and the telephone provider that carries calls and texts.
To connected services you authorize. If you connect another service or direct an export, that service receives information as instructed and handles it under its own terms.
For legal and security purposes. We may disclose information when reasonably necessary to comply with applicable law or valid legal process, protect people or the service, investigate abuse, or establish or defend legal claims.
In a business transaction. Relevant information may be disclosed in connection with a merger, financing, acquisition, restructuring, or transfer of business assets, subject to appropriate confidentiality protections and applicable law. We will provide notice of changes where required.
Qualifying Anonymous Industry Statistics may be disclosed under Section 3 if a future statistics product is introduced lawfully. We do not currently sell that product. We do not sell personal information or share it for cross-context behavioral advertising, as those terms are defined under applicable privacy law, or use it for targeted advertising. Our future statistics permission does not authorize activity that legally constitutes selling or sharing personal information.
Text messages. We do not sell or rent telephone numbers, SMS opt-in records or messaging consent. No mobile information will be shared with third parties or affiliates for marketing or promotional purposes, and text messaging opt-in data and consent will not be shared with any third parties, except the business that sends the messages, the providers and carriers that deliver them, and as legally required. Messaging consent belongs to the particular sender and purpose; it is not transferable marketing permission. Necessary disclosures to the business sending the message, delivery providers and carriers, and for legally required or security purposes remain subject to the protections and purposes described in this policy. You can reply STOP to any text to opt out or HELP for help; the SMS Terms at https://relacent.com/sms-terms explain how texting works.
6 Cookies, browser storage and advertising choices
Cookies and similar technologies can support authentication, security, preferences, and continuity of work. Browser settings may let you block cookies or clear stored information. Doing so can sign you out, remove a locally retained draft, or prevent a feature from working.
Except for the cookieless page statistics on relacent.com described in Section 7, Relacent does not use visitor analytics, advertising pixels, session replay, or email open and click tracking. Internal operational monitoring is limited to service reliability, security, errors, API consumption, limits and costs. It is not used to build advertising profiles. We minimize diagnostic content and do not intentionally record customer files or message bodies in routine error logs.
Legacy Do Not Track signals do not cause us to change the collection needed for the purposes described in this policy. Do Not Track is distinct from legally recognized opt-out preference signals, such as Global Privacy Control. Our restrictions on sale, sharing and targeted advertising apply whether or not a signal is sent. Where an applicable law requires a recognized signal to be treated as an opt-out request, we will honor it for the processing to which it applies without requiring an additional request that the law does not permit. Signals do not disable necessary authentication, security, payment or customer-directed communications.
The public marketing pages do not set analytics or advertising cookies. The scheduler on relacent.com/book is HubSpot’s own page shown in a frame; HubSpot may set its own cookies inside that frame, as its privacy policy explains. Authenticated features use session and security technologies; browser storage may also preserve preferences or recoverable drafts. When you use enabled Google Maps features, map requests, addresses or coordinates, IP addresses and related device or connection information may be sent to Google. Google’s Privacy Policy at https://policies.google.com/privacy is incorporated for those features and explains Google’s separate processing; the Google Maps and Google Earth Additional Terms apply at https://maps.google.com/help/terms_maps/. We do not use the integration for live employee GPS tracking at launch.
Error reports. When a page or background job in Relacent fails, our servers send a short error report to our error-monitoring provider, Sentry. Before it is sent, we remove email addresses, phone numbers, street addresses, IP addresses, card and account numbers, link tokens and query strings, and business and user identifiers are replaced with one-way codes. Browsers do not contact Sentry directly.
7 Cloudflare security services
Where enabled, Cloudflare security and network services help deliver and protect our websites and forms. They may process IP addresses, browser and connection information, request metadata and technical security signals. Cloudflare Turnstile uses browser and device signals to distinguish people from bots and also processes signals to improve its bot-detection capabilities. The Provider and Subprocessor List identifies the enabled Cloudflare products and their roles. Cloudflare’s Turnstile Privacy Addendum explains that product’s processing.
Page statistics on relacent.com. On the public pages of relacent.com, Cloudflare Web Analytics counts page views and measures how quickly pages load. It does not set cookies or use browser storage, does not build profiles of visitors and does not follow you across other websites. Cloudflare receives the address of the page, the referring page, the browser and device type, the country inferred from your IP address and page-load timings, and we see only totals. It does not run on app.relacent.com, in workspaces, or on the booking, quote or payment pages that businesses send to their customers.
Cloudflare Turnstile Privacy Addendum — https://www.cloudflare.com/turnstile-privacy-policy/
8 Retention and deletion
Routine retention depends on the record’s purpose, sensitivity, the business’s instructions and legal duties. Workspace records remain available while the service continues unless valid deletion instructions or a shorter schedule apply. Temporary imports and OCR files are retained only as needed for extraction, review and safe recovery. Reliability and API-cost logs are limited to the operational period needed to diagnose errors, reconcile usage and protect the service. Support records are retained for the period needed to resolve the request and meet applicable legal duties. Financial and consent records follow their specific legal requirements. We maintain a record-category schedule and remove information when its justified purpose and applicable retention period end; keeping an account read-only does not justify retaining unrelated data indefinitely, and read-only access ends after no more than 12 months.
AI receptionist records. Call recordings are kept in the business’s workspace for 30 days by default, or for the period the business chooses between 1 day and 12 months, and are then deleted automatically. Transcripts, summaries and the requests or bookings created from a call are part of the business’s Customer Content and follow its deletion instructions. Our voice-agent provider deletes its copies of recordings, transcripts and call logs about 10 minutes after each call and keeps basic call details for at most 1 day; its backups follow the schedule in the Provider and Subprocessor List. Our telephone provider keeps call and message detail records (numbers, times, durations and delivery status) as an independent controller for its own billing, fraud-prevention and legal purposes, as described in the Provider and Subprocessor List. Usage totals used for billing are kept with billing records.
On receipt of a valid, authorized deletion request or instruction, Relacent will delete the requested information from active systems within 30 calendar days, subject to specific legal retention requirements and any shorter applicable legal deadline. Active systems include databases, files, temporary imports and OCR files, searchable logs and caches containing the requested information, and relevant active copies processed by providers on Relacent’s behalf. Relacent will promptly initiate the applicable provider deletion processes; forwarding a request alone does not establish that deletion is complete.
Residual copies in disaster-recovery backups are subject to a separate, documented deletion schedule. Relacent will identify the applicable backup cycle, its starting event and maximum retention period in the Provider and Subprocessor List or an agreed retention schedule made available to the Business Customer before acceptance. Backup periods must be supported by the actual configuration and provider commitments; a period measured from termination of Relacent’s provider account is not treated as a period measured from a customer’s deletion request. Relacent will not keep copies indefinitely or extend an agreed period merely by making another backup.
During any permitted backup-retention period, the information will be isolated from ordinary use and protected under the same confidentiality and security obligations. It may be accessed only as necessary for disaster recovery or compliance with law, and deletion instructions must be reapplied before restored records return to ordinary use. It will not be used for analytics, AI training, sales or another commercial purpose. Any shorter applicable legal deadline controls.
We may verify identity and authority where permitted or required, and will request any necessary information promptly rather than using verification to delay a valid request. If a request concerns records controlled by a service business, we will route it to that business and assist as described in Section 9. For those records, the 30-day commitment applies when we receive the business’s valid deletion instruction or a request that we must act on directly under applicable law.
Only specific records subject to a legal retention or preservation duty, including binding legal process, may be kept beyond the applicable deletion deadline. Relacent will document the duty and the affected records, minimize and restrict the retained information to that purpose, review whether the duty continues, and delete the records when it ends. General usefulness, possible future sales, ordinary business convenience or a provider’s optional retention setting is not a legal retention duty. Relacent will explain an applicable exception where legally permitted.
Free-trial eligibility record. The fraud-prevention record described in Section 3 contains only keyed hashes. It is kept for 24 months from the start of the trial it relates to, including after a deletion request, account closure or termination, because it is needed to detect and prevent repeated free-trial abuse, a purpose for which applicable privacy laws permit retention. It is then deleted automatically. During that period it is restricted to the trial-eligibility check and is not used for any other purpose. A deletion response will identify this record if it applies.
Agreement and billing-authorization records. When a business closes or deletes its account, we keep a minimal record of its acceptance of our Terms of Use, EULA and Data Processing Addendum and of its recurring-billing authorization: the business name, the accepting person’s name and email address, the document versions accepted, the time of acceptance and the billing terms shown. We keep this record for 3 years after the subscription ends to maintain accurate business and tax records and to respond to payment disputes and legal claims, purposes for which applicable privacy laws permit retention, and then delete it automatically. It is restricted to those purposes and is not used for anything else. A deletion response will identify this record if it applies.
Compliance records. When a business account is deleted, we keep minimal records needed to show that we met our legal duties, separate from the business’s Customer Content: records of privacy requests and our responses for 24 months, and records of security incidents, copyright notices and text-message consent or opt-out disputes for 4 years. They are then deleted automatically and are not used for any other purpose.
Canceling renewal does not by itself request deletion of a workspace. Business Customers should export needed records before requesting deletion. Copies independently exported or retained by a service business or another recipient are subject to that recipient’s responsibilities. Deletion does not cancel a legally required record or transfer another business’s records to the requester.
After workspace service actually ends, the Business Customer has 30 calendar days to request or complete a secure export of its Customer Content through available controls or by emailing support@relacent.com. Relacent will delete the remaining Customer Content from active systems during the following 30 calendar days, no later than 60 calendar days after service ends. Residual disaster-recovery copies follow the separately disclosed backup schedule. A valid earlier deletion instruction starts its own 30-calendar-day active-system deadline; the earlier applicable deadline controls. Specific legal retention duties and shorter applicable legal deadlines remain controlling.
An account with read-only access remains in limited service for up to 12 months, as described in the Terms of Use. The end of a trial or paid period does not start the post-service export and deletion schedule while read-only access continues. That schedule starts when the workspace service actually ends: when read-only access ends without a paid plan being confirmed, or upon account closure or termination. A valid earlier deletion request still starts its own deletion deadline.
Qualifying Anonymous Industry Statistics created lawfully before service ends may be retained and sold after cancellation or deletion of the underlying records while they continue to satisfy the safeguards in this agreement. This does not permit retention of identifiable source records, row-level pseudonymous records, or reidentification keys beyond their deletion deadline. We will not create new commercial statistics from records held solely for export, deletion, or legally required retention after service ends.
A deletion response will distinguish completed active-system deletion from residual backup retention, identify the applicable schedule and expected expiry, and explain any lawful exception where permitted. We will not represent that every copy has been erased while known backup copies remain. You can request retention information and confirmation at support@relacent.com.
9 Your choices and privacy requests
Contact support@relacent.com with privacy questions or requests. Depending on where you live, which law applies, and our role in processing the information, you may have rights to confirm processing, access or obtain a copy, correct inaccuracies, request deletion, or opt out of certain uses such as sale, targeted advertising, or qualifying profiling. These rights may have legal exceptions.
If a service business controls the records in question, contact that business first. If you contact us, we will help identify the appropriate business when possible and assist it with requests as required by our agreement and applicable law.
Where permitted or required by applicable law for the particular request, we may request information reasonably necessary to verify your identity or an authorized agent’s authority. We will not require identity verification for an opt-out request where applicable law prohibits it. Please do not send sensitive identity documents unless we request them through an appropriate method. We will respond within applicable legal time limits and will not unlawfully discriminate against you for exercising your rights.
Where applicable law gives you an appeal right, appeal a denied request by emailing support@relacent.com with “Privacy appeal” in the subject and enough information to identify the request. We will review the decision, respond within the applicable legal period with reasons, and explain the available regulator complaint route if the appeal is denied. You may submit requests and appeals through an authorized agent where the law permits. We will not impose a contractual deadline that shortens a statutory right.
For messages sent by a service business using Relacent, follow that message’s preference or unsubscribe instructions, where applicable, or contact that business. Communication preferences do not replace consent required by law.
If you call a business that uses the AI receptionist and do not want to talk to an AI or be recorded, say so, and the receptionist will offer to connect you to the business or give you another way to reach it. To ask for a copy or deletion of a call record, contact that business, or contact us and we will route the request to it.
10 Security, user eligibility and processing locations
We use reasonable administrative, technical, and organizational measures designed to protect personal information, including separating each business’s records in the database, requiring an authenticator code at sign-in, keeping files in private storage, encrypting backups and limiting who at Relacent can access production systems. No system or transmission is completely secure, and we cannot guarantee that information will never be accessed, disclosed or lost. Please protect your credentials and tell us promptly if you suspect unauthorized access.
A person opening a Relacent subscription must be at least 18, have reached the legal age of majority where they live, and have authority to act for the subscribing business. Businesses may invite employees who are at least 16. Employees who have not reached the applicable age of majority may use an invited account only under the business’s authorization and supervision, with parental or guardian permission where required by law. They may not open or purchase a Relacent subscription.
Relacent accounts are not intended for anyone under 16, and our service is not directed to children under 13. We do not knowingly collect personal information from children under 13 through our own pages. If you believe someone under the permitted age has provided information through their own account, contact support@relacent.com so we can investigate and take appropriate action. These account rules do not determine whose information a business may lawfully keep in its customer records.
Our initial service is offered to businesses in the United States, and our primary production systems are located in the eastern United States. Information may be processed in other countries by the providers identified in the Provider and Subprocessor List, including for support and security. Those countries may have different privacy laws. We use the contractual and other safeguards required by the law applicable to the transfer. A U.S. customer location does not establish U.S.-only processing or remove a legal transfer requirement.
11 Changes and contact information
We may update this policy to reflect changes in our practices or legal obligations. We will show the effective date and provide additional notice or obtain consent when required. We will not treat a policy update alone as permission to use previously collected information in a materially incompatible way.
Privacy contact: support@relacent.com
Relacent LLC, 1832 Kempsville Rd, Ste 112 #123, Virginia Beach, VA 23464, United States
Telephone: (757) 993-7449
Website: https://relacent.com