A discussion draft, not an executed agreement
live.link is operated by Melade LLC, formed in Pennsylvania, United States. This page outlines proposed terms for customers who need a data processing agreement. It is an unsigned discussion draft subject to legal review. Visiting this page, creating an account or using the service does not execute this agreement or establish compliance with a particular privacy law.
Contact info@live.link before using live.link for processing that requires a signed data processing agreement, a specified processing location or additional contractual safeguards. The intended initial launch market is the United States. No international transfer agreement or standard contractual clauses are incorporated by this page.
Identify the parties and their roles
A customer may decide why and how personal information in its projects is processed, while live.link processes that information to provide the customer’s requested service. The roles depend on the actual activity and applicable law. Account administration, service security and legal compliance can involve separate responsibilities described in the Privacy Policy.
A completed agreement would identify the customer, authorized contacts, applicable service agreement, processing roles and governing privacy requirements. It would distinguish customer content from account, security and operational records instead of assigning one role to every activity.
Describe the processing
The proposed scope covers hosting, storing, saving versions, previewing and delivering supported websites and documents, and carrying out specifically requested supported AI operations. It would include supported reader responses only where the customer enables the relevant feature.
Customer content may contain names, contact information, document text, files, instructions and reader responses. People represented can include the customer’s personnel, contributors and readers. Exact categories, purposes and any sensitive information must be assessed with the customer before agreement; this draft does not approve regulated or sensitive-data use.
The processing schedule would identify the relevant services, authorized audiences, duration, locations and deletion or return arrangements. Unreleased features are outside the agreed scope unless expressly added after acceptance.
Instructions and access
Proposed terms would limit processing of customer content to documented lawful instructions and necessary service operations, with a process for instructions that conflict with law. A legal requirement to process differently would be addressed under the applicable notification rules.
Customer instructions would include authorized account actions, audience choices and scoped agent actions. Access would remain limited by the service’s authorization controls. Proposed confidentiality obligations would apply to personnel permitted to process the covered information.
Security and assistance
An agreed security schedule would describe the measures actually provided for the covered service, including access controls, credential scope, management/content separation and relevant provider arrangements. It would not treat a marketing statement as a certification or substitute for assessing the customer’s risks.
The agreement would define assistance with individual rights requests, security incidents and required assessments, including contacts, information exchange and legally appropriate notification timing. This draft creates no fixed incident-response deadline, audit certification or service-level guarantee.
Service providers and transfers
The service’s Privacy Policy describes provider functions, including authentication/database, hosting, security, email and requested AI processing. Not every provider performs every function for each customer. A completed agreement would include the actual subprocessor identities, relevant locations and services, and the process for authorization, notice and objections.
Any required cross-border safeguards must be assessed and agreed before the covered processing begins. This page does not establish a regional hosting promise, an executed transfer mechanism or an approved subprocessor annex.
Return, deletion and evidence
Proposed terms would address return or deletion of covered customer information at the end of the service, subject to applicable legal retention duties, recovery windows and documented backup/provider deletion cycles. Turning off a published link is not the same as erasing saved versions or recipients’ copies.
An agreement would also define information and proportionate audit arrangements needed to assess the agreed obligations, protecting other customers’ information and service security. Retention schedules and technical capabilities must be confirmed before contractual deadlines are accepted.
Request an agreement
Email info@live.link with your organization’s name, the service you intend to use, the kinds of personal information involved, relevant countries and contractual requirements. Do not attach production datasets, credentials or unnecessary sensitive information.
The next step is a reviewed agreement with completed processing and security schedules, provider/transfer terms and authorized acceptance by both parties. Until then, this page is a proposal only.