This addendum governs personal data Relacent processes on a subscribing business’s behalf. It defines instructions, security, incident notice, provider changes, export, deletion and limited anonymous-statistics processing.
1 Parties scope and acceptance
This Data Processing Addendum (“DPA”) supplements the Relacent Terms of Use or another written agreement expressly incorporating it (“Main Agreement”) between Relacent LLC, Virginia, United States (“Relacent”), and the subscribing business identified in the account or order (“Customer”). It becomes effective when an authorized Customer representative accepts the version presented with the Main Agreement or signs an agreement incorporating it. Publication alone does not establish acceptance.
“Customer Personal Data” means personal information in Customer Content that Relacent processes on Customer’s behalf. “Data Protection Laws” means privacy and security laws applicable to that processing. “Subprocessor” means a provider Relacent engages to process that data on its behalf. Annex 1 describes the processing. Relacent acts as a processor or service provider; Customer acts as a controller or, where applicable, a processor with authority from its controller.
Relacent separately handles its own account administration, subscription billing, and business-contact information under its Privacy Policy. Providers may have separately disclosed independent-controller roles. These distinctions follow actual processing and law; a contract label does not waive a duty or authorize unrelated use. This DPA continues while Relacent or its subprocessors retain covered data.
2 Instructions and permitted use
Relacent will process Customer Personal Data only to provide, maintain, support, and secure the Services; carry out Customer’s documented instructions consistent with the Main Agreement; perform the narrowly authorized statistics processing in Section 10 where lawful; or meet applicable legal obligations. Customer’s use of enabled features supplies instructions for those features. Relacent will inform Customer if it reasonably determines an instruction infringes Data Protection Laws or cannot lawfully be followed.
Customer is responsible for lawful collection, required notices, consents, and authority for its instructions, including instructions involving employees and end customers. In particular, Customer warrants that it has the notices and consents the law requires for the texts it sends, for recording and transcribing calls answered by its AI receptionist, and for sending records, notes and photos to the AI features it turns on. Customer will not submit the specially regulated data excluded in Annex 1. Relacent remains responsible for its own obligations. Acceptance by a business does not substitute for rights or consent belonging to an individual.
Where the CCPA applies, Relacent will not sell or share Customer Personal Data, use or disclose it outside the direct business relationship or for purposes other than the limited specified purposes in this DPA, or combine it with other personal information except as permitted for a service provider. Relacent will provide the level of privacy protection required by applicable law, notify Customer if it can no longer meet those obligations, and permit reasonable steps to verify compliance and stop and remediate unauthorized use. “Sell” and “share” carry their applicable statutory meanings. These restrictions also constrain creation of statistics; Section 10 is not an exception to them.
3 Confidentiality and security
Relacent will restrict access to people who need it for authorized work and ensure those people are subject to appropriate confidentiality obligations. It will implement and maintain reasonable technical and organizational measures appropriate to the data and risks, as described in Annex 2, and monitor compliance with those measures.
Security changes must not materially reduce the overall protection promised for covered data. No particular certification, audit opinion, or uninterrupted-service guarantee is represented by this DPA unless expressly identified in a separate executed agreement. Customer must manage its users and permissions and use available security controls appropriately.
4 Subprocessors and objections
Customer generally authorizes the subprocessors identified in the accepted Relacent Provider and Subprocessor List, for the functions and data described there. Relacent will keep the list current, identify functions and processing locations, require appropriate written data-protection obligations, and remain responsible for its DPA obligations and subprocessor acts or omissions that cause Relacent to breach them. Where a subprocessor’s terms permit it to use deidentified or aggregated information to improve its own services, the Provider and Subprocessor List says so, and Relacent configures that subprocessor to retain the least information its settings allow.
At least 30 calendar days before a new or replacement subprocessor that Relacent engages directly begins processing Customer Personal Data, Relacent will update the list and email the designated Customer administrator. The notice will identify the provider, function, relevant data and locations, proposed start date and objection method. Customer may object in writing within 30 calendar days after notice on reasonable data-protection grounds. Relacent will not rely on a website-only update instead of the required email.
A listed subprocessor may engage its own new provider on shorter notice to Relacent, as stated for that subprocessor in the Provider and Subprocessor List. Relacent will update the list and email the designated Customer administrator within 2 business days after receiving that notice. The email will give the information above, the provider’s start date and the shorter period. Customer may object within 30 calendar days after Relacent’s email. On a timely objection, Relacent will, at Customer’s choice, stop sending Customer Personal Data to the affected feature until the objection is resolved, or end the affected portion with the refund of unused prepaid fees described below.
If Customer submits a timely objection, Relacent will not permit the proposed provider to process that Customer’s Personal Data while the objection remains unresolved, unless Customer expressly agrees in writing or applicable law requires the particular processing. Existing compliant processing may continue. The parties will work in good faith for up to 30 calendar days after the objection to agree safeguards or an alternative.
If the concern remains unresolved at the end of that period, or the parties determine earlier that no workable resolution exists, Customer may terminate the affected portion by written notice within the following 30 calendar days. Relacent will refund unused prepaid fees attributable to that portion as of termination. The proposed provider will not receive the objecting Customer’s data merely because the objection or termination period expires; the parties must agree a compliant solution or end the affected processing. Relacent may end that portion if it cannot continue it lawfully or without the proposed provider, with the same unused-prepaid refund.
An urgent operational problem does not silently waive this process. Relacent must use an already authorized solution, obtain Customer’s express agreement to a different arrangement, or limit the affected service with appropriate notice and contractual remedies. This section preserves any shorter legal deadline or mandatory customer right.
5 Security incidents
A “Security Incident” is a breach of security resulting in accidental or unlawful destruction, loss, alteration, unauthorized disclosure of, or access to Customer Personal Data processed by Relacent or its subprocessors. Unsuccessful attacks that do not compromise that data are excluded.
Relacent will notify affected Customers without undue delay and no later than 72 hours after becoming aware of a Security Incident affecting their data, or sooner if applicable law requires. It will not wait for a complete investigation before sending an initial notice. The deadline applies on weekends and holidays.
Relacent will provide information then available about the incident, affected data and people where known, likely consequences, mitigation, and a contact for follow-up. It will investigate, take reasonable containment and corrective measures within its control, preserve evidence lawfully, and provide material updates as information becomes available. It will assist Customer with information reasonably needed for Customer’s legal notifications. Notice is not an admission of fault. Each party remains responsible for its own legal notification duties.
Notice will be directed to Customer’s designated incident or administrator email with reasonably available backup contact methods if delivery fails. Customer must keep those contacts current. Relacent will record when it became aware, notify on the information available, and provide updates; uncertainty about the full scope does not restart the 72-hour clock. A provider’s slower reporting terms do not extend Relacent’s deadline once Relacent is aware.
6 Requests and cooperation
Relacent will provide reasonable, timely assistance with access, correction, deletion, portability, opt-out, and other applicable privacy requests, taking account of the processing and available information. It will normally route requests concerning Customer-controlled records to Customer and act on Customer’s valid instructions, except when law requires Relacent to act directly. Verification must be proportionate and must not obstruct a right or delay a valid request improperly.
Relacent will assist with legally required data-protection assessments and regulator inquiries relevant to its processing. It will notify Customer of compulsory requests for Customer Personal Data where legally permitted, limit disclosure as required, and cooperate reasonably with lawful instructions. Nothing requires disclosure of another customer’s records or information Relacent is prohibited from disclosing.
7 Return retention and deletion
During the service period, Customer may use available controls or email support@relacent.com to request a secure export or deletion. Relacent will provide requested exports in a commonly used electronic format appropriate to the records and associated files, subject to verification and lawful restrictions.
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.
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.
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.
Relacent will keep records of scoped deletion instructions and provider requests, distinguish active deletion from backup expiry, and provide confirmation and remaining scheduled dates on request. An independently acting recipient may have separate legal obligations; that does not excuse Relacent’s obligations or those of a provider processing on its behalf.
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.
8 Compliance information and audits
Relacent will maintain appropriate compliance records and make information reasonably necessary to demonstrate compliance available to Customer. Existing independent audit summaries, if any, may be provided confidentially; this clause does not assert that Relacent has obtained a certification or independent audit.
Relacent will first answer Customer’s reasonable written security and privacy questions, at most once a year unless an incident, regulator or law requires otherwise. If those answers and available documentation are insufficient, or a regulator, incident, or applicable law requires further assessment, Relacent will reasonably cooperate with an audit by Customer or a qualified independent assessor bound by confidentiality, on at least 30 days’ written notice. The parties will agree a reasonable scope and schedule, ordinarily remote and during business hours, and no more than annually unless an incident, regulator, or law requires otherwise. An on-site visit takes place only where a regulator or law requires it. Confidentiality, tenant isolation, and protection of credentials and other customers’ records apply. Ordinary Customer-initiated audit costs are Customer’s unless law requires otherwise; charges or procedures must not defeat a mandatory right. Applicable law controls any required broader assessment rights.
9 Processing locations and other recipients
The commercial launch is for U.S. businesses. Relacent’s primary production systems are located in the eastern United States. This does not promise U.S.-only processing or exclude a law that applies to particular records. Relacent will identify applicable provider locations and comply with legally required transfer restrictions. Before a transfer requiring a specific mechanism, the parties must complete and implement that mechanism and its necessary details. This U.S.-launch adaptation does not purport to execute blank European transfer clauses, select an unagreed European forum, or claim Data Privacy Framework certification.
Some enabled services, including mapping, payments, security, and telecommunications, may process limited data under separate controller responsibilities described in the provider list. Such use must be properly authorized, disclosed, and lawful; it is not converted into processing solely on Relacent’s behalf by listing the provider. Relacent will not rely on this paragraph to evade processor obligations or grant those providers a general license to Customer Content.
10 Anonymous industry statistics
“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.
Subject to Data Protection Laws, Customer authorizes the limited creation of qualifying statistics while Relacent provides the Services, for industry benchmarking such as broad pricing, demand, and duration trends. Relacent may use, retain, publish, license, and sell only the qualifying statistical outputs. Customer retains rights in the source content. Relacent may not disclose an individual business’s confidential information or sell identifiable personal records under this authorization.
Creation must be lawful in the first place. Source data and intermediate outputs remain protected until they qualify. Where cross-customer combination of personal data is not permitted for a processor or service provider, Relacent must deidentify within the permitted context before combining qualifying outputs, or refrain from that processing. A pseudonymous dataset, record-level export, customer list, property history, or dataset with a usable reidentification key does not qualify merely because names are removed.
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.
These permissions survive termination only for statistics lawfully created before service ends that continue to qualify. There is no exception to a source-data deletion deadline for commercial analytics. The permission does not authorize AI training; any future training use remains subject to the separate disclosures, permissions, contractual amendments, and legal requirements described in the Main Agreement. If lawful creation or adequate protection cannot be established, Relacent will not create or release that statistics product.
11 Relationship to the main agreement
This DPA controls a conflict with the Main Agreement or EULA regarding covered personal-data processing, subject to mandatory law and any valid mandatory transfer terms. The Main Agreement’s governing law and liability allocation otherwise apply to the extent lawful. This DPA does not create a second liability cap or waive nonwaivable individual rights; all liability arising out of or relating to this DPA, including for subprocessors, is subject to the single aggregate cap and exclusions in the Main Agreement to the extent the law permits. The express provider-objection refund remains available.
Material changes require appropriate notice and agreement as required by the Main Agreement and law. Updating a posted document does not retrospectively authorize incompatible uses of previously collected data. Contact Relacent for DPA, privacy, incident, and provider-change matters at support@relacent.com.
Annex 1 Processing details
Provider: Relacent LLC, 1832 Kempsville Rd, Ste 112 #123, Virginia Beach, VA 23464, United States; support@relacent.com; (757) 993-7449. Customer: the Business Customer identified in the accepted account or order. Its designated administrator is the privacy and incident contact unless another contact is supplied. The agreement record identifies the Customer, authorized representative, acceptance date, and versions of this DPA and the Provider and Subprocessor List, including its backup schedule, published at https://relacent.com/subprocessors.
Subject matter: hosted CRM and service-business operations, including accounts and permissions, customer and property records, imports, estimates and quotes, scheduling, visit history, invoices and receipts, enabled payments, authorized communications, AI features that draft quotes, follow-up messages, visit reports and answers from service records, AI receptionist call handling, recording, transcription, summarization, call transfer and related texting, support, security, backups, and the limited statistics processing in Section 10. Data subjects include business contacts, prospective and existing customers, callers who are not yet customers, property contacts, and authorized personnel, including invited employees aged 16 or older.
Data categories: names and contact details; business and account identifiers; property addresses and related map queries; job notes, photographs and uploaded files; schedules, assignments and visit records; estimates, quotes, invoice and payment-status records; communication content, preferences and delivery history; call audio and recordings, transcripts, call summaries, caller-provided details and call detail records for the AI receptionist; and relevant technical and security information. Payment credentials are subject to the actual payment-provider flow and must not be entered into general notes or uploads.
Scope limitations: live employee GPS tracking and collection of government IDs, SSNs, health records, or comparable specially regulated records are outside the agreed launch purpose. Call recordings, transcripts and summaries are within scope only for Business Customers that enable the AI receptionist. This is a use restriction, not proof that uploaded text or photographs can never contain sensitive information. Addresses, coordinates, communications, and ordinary account information may themselves receive special protection under applicable law. If unexpectedly received, restrict use and address the issue lawfully.
Operations and frequency: collection, hosting, organization, retrieval, display, calculation, transmission as instructed, protection, export, deletion and permitted anonymization during recurring use of enabled features. Duration: the service period, export and active-deletion periods, separately disclosed residual-backup schedule, and specific legal retention duties in Section 7. Functions and processing locations are in the incorporated provider list.
Annex 2 Security commitments for launch
Relacent will maintain the following measures throughout covered processing. The measures describe contractual obligations; no independent certification or completed security audit is represented.
Access and confidentiality. Apply least-privilege access, tenant-scoped authorization, appropriate authentication, stronger controls for privileged access, access removal when no longer needed, and confidentiality obligations for authorized personnel. Protect secrets separately from publicly served code and customer-facing artifacts.
Data handling. Use appropriate encryption in transit and at rest for systems under Relacent’s control; keep customer files private; minimize personal information in diagnostic logs; protect temporary imports and OCR files; and restrict access to backups. For the AI receptionist, configure the voice-agent provider to keep no recordings, transcripts or logs after post-call processing and to delete basic call details after 1 day, copy recordings into private, tenant-scoped storage, and delete the provider’s copy of each call by API once Relacent’s copy is stored. Ordinary email or SMS is not represented as end-to-end encrypted.
Operations. Maintain reasonable vulnerability and patch management, security monitoring, incident escalation that can meet the 72-hour notice deadline, and risk-appropriate security testing. Maintain backup and restoration procedures and test recovery without reviving deleted records.
Lifecycle and providers. Maintain a data inventory, record-category retention schedule, secure export and deletion procedures, privacy-request and appeal handling, provider agreements and change-notice records. Record each backup cycle’s starting event and maximum period; test active-system deletion, expiry and restoration safeguards. Qualify a provider’s relevant retention and security behavior before permitting covered processing. Test deidentification and disclosure risk before releasing statistics, document the assessment and reassess when data or identification risks change.
12 Framework attribution
This DPA is adapted from the Bonterms Data Protection Addendum Version 2.0, Attachment Version, © 2026 Bonterms, Inc., available under Creative Commons Attribution 4.0 International. It substantially modifies the standard for Relacent’s U.S. launch, anonymous statistics, active-system and residual-backup deletion, provider objections, acceptance and security obligations. It is not the unchanged Bonterms standard and does not incorporate uncompleted international transfer exhibits.
Bonterms has not reviewed, certified, or endorsed this adaptation and does not provide legal advice. The document-text license does not license Relacent software or Customer Content.
Bonterms DPA Version 2.0 Attachment Version — https://bonterms.com/standard/dpa-v2-attachment-version
Creative Commons Attribution 4.0 International — https://creativecommons.org/licenses/by/4.0/