Draft for legal review. Do not publish or accept assent against this draft.
Contact: one@hesly.io. Effective date, registered address, governing law, courts and contracting entity details remain to be confirmed by the operator and counsel.
Service and access
Hesly is a business workspace in development. Access is by invitation. Intended service areas include sales, purchasing, stock, banking and currency records, accounting, directory, projects and people operations. The actual enabled features for a workspace must be stated in its order or service description before paid access begins.
Customer responsibilities
Before approval, counsel and the operator must define customer authority, permitted use, data accuracy, user access controls, customer support, acceptable-use rules and handling of uploaded records. No customer duty or warranty is agreed by this draft.
Commercial terms
Prices, plan names, billing periods, limits, renewal, cancellation, refunds, taxes on fees, payment methods and suspension rules are not approved. They must be supplied in an approved order or plan document before any charge is taken.
Product output and accounting treatment
The product records business data and calculations. Counsel and the product owner must review wording on reliance, exports, exchange-rate sources, tax configuration, accounting outputs, corrections and service availability. This draft does not promise a tax treatment, legal outcome, compliance result or fitness for a particular purpose.
Required legal decisions
Confirm the contracting entity details, applicable law, dispute forum and required language versions.
Review warranties, liability allocation, indemnities, suspension and termination.
Define support, service changes, notices, intellectual-property terms and customer content rights.
Align these terms with the privacy notice, DPA, approved plans and actual invitation flow.
Draft prepared 17 November 2026. No version is effective until reviewed, approved and presented through a reviewed acceptance flow.
HOMBRE NÓMADA S.L. · WORKSPACE DOCUMENT
Hesly workspace privacy notice
Draft for legal review. Do not publish as the operative notice.
Privacy contact: one@hesly.io. Registered address, privacy representative where applicable, effective date and final controller identity remain to be confirmed.
Data and purpose inventory to verify
The workspace is designed to handle business records such as contact details, invoices, purchases, stock movements, payment and currency records, accounting entries, project records and people records. The production data flows, optional fields, access roles and purposes must be confirmed against the deployed system and customer configuration.
Before approval, document whether the service processes account and invitation details, authentication events, support correspondence, customer uploads, audit events, security telemetry, or any special-category or employee information. Do not collect or enable a category until its purpose and safeguards are reviewed.
Controller and processor roles
The customer/operator role for each processing activity must be assessed by counsel. The planned SaaS relationship may involve customer-controlled business data processed by Hesly, while Hesly may separately determine purposes for account administration and service security. These roles and any independent-controller activities must be stated precisely in the final notice and DPA.
Items to confirm before use
Hosting, database, email and support providers; subprocessors; processing locations and transfer mechanisms.
Legal bases and purposes for each data category, including employee and financial records.
Retention and deletion periods, backups, export handling, account closure and legal holds.
Whether cookies, analytics, diagnostics or other identifiers are used in the app.
Data-subject rights, complaint authority, contact route and any applicable representative.
Whether automated decision-making or AI processing touches customer data; current scope must be verified and described accurately.
Contact
Privacy enquiries for this draft review: one@hesly.io. The final notice must specify the verified operator contact details and response process.
Draft prepared 17 November 2026. This is not the public-site privacy notice and must not replace it until reviewed and approved.
HOMBRE NÓMADA S.L. · WORKSPACE DOCUMENT
Hesly data processing agreement
Draft for legal review. Do not execute or attach to customer contracts.
Proposed service provider named for review: Hombre Nómada S.L. · one@hesly.io. Customer legal name, contract date, service schedule and signature blocks must be completed for each customer after legal review.
This document is a negotiation and evidence checklist, not an agreement. No GDPR or other statutory compliance conclusion is made here.
Processing particulars to complete
Subject matter and duration: match the approved service/order and account lifecycle.
Nature and purpose: verify against deployed app features and customer instructions.
Data subjects: may include customer contacts, counterparties, staff and workspace users; confirm exact scope.
Personal-data categories: inventory actual fields, imports, logs and support workflows.
Customer instructions and controller identity: complete for each customer and validate authority.
Processing and backup locations: confirm provider configuration before making commitments.
Subprocessors: obtain the current provider list, locations, functions and change process.
Retention, return and deletion: define active data, backups, exports, legal holds and verified deletion behavior.
Security measures: attach reviewed measures based on implemented controls and evidence.
Assistance and incident notice: set responsibilities, channels and timeframes after review.
International transfers: map access and storage locations and select any required mechanism with counsel.
Clauses requiring counsel
Counsel must draft and approve binding provisions for documented instructions, confidentiality, security, subprocessors, data-subject requests, breach assistance, impact assessments, audits, international transfers, return/deletion, liability, precedence, term and signatures.
Technical evidence required before signature
Verify actual production hosting and database region, backups and restore process, support access, subprocessors, secret handling, access logging, encryption, tenant isolation/RLS, retention/deletion, incident process and the precise features enabled for the customer. Attach only evidence that has been reviewed and can be maintained.
Draft prepared 17 November 2026. No processing agreement is formed by this draft.