Privacy Policy
Last updated: October 5, 2026
1. Scope and Data Controllers
This policy applies exclusively to data processing carried out through the platform and services of Edit ERP.
Under Law No. 25,326, the following roles are defined:
- Edit Software as Data Controller: with respect to identification, contact, billing, and credentials data of merchant and enterprise users (tenants), as well as direct operator and user accounts.
- Edit Software as Data Processor (art. 25, Law 25,326): with respect to final customer and buyer data, suppliers, invoices, logistics, and collection records that each merchant registers and manages within the system. In these cases, the merchant user acts as the Data Controller before its respective customers and data subjects.
Edit Software Identification Data:
- Corporate Name: DE LA RIVA DIEGO GERMAN Y SOTTILE SEBASTIAN
- Tax ID (CUIT): 30-71787906-2
- Legal Address: Jorge Newbery 885, Junín, Buenos Aires Province (ZIP 6000), Argentine Republic
- Contact & Privacy Email: info@editsoftware.dev
- Contact Phone: +54 236-422-5126
2. Data Processed in the System
Edit ERP processes only the categories of data strictly required for commercial, operational, accounting, and tax management:
a) Merchant and Enterprise User Data (Tenants)
- Commercial and tax identification: corporate name, trade name, business description, tax ID (CUIT/CUIL), tax status before ARCA/AFIP (Registered Taxpayer, Monotributo, Exempt, etc.), and Gross Income tax registration (multilateral or local agreement - e.g., ARBA).
- Corporate contact details: commercial/tax address and branch offices, contact person name, corporate email, and support/ticket email (mailTickets).
- Credentials and external integrations: digital certificates and private keys for electronic invoicing before ARCA/AFIP (WSAA/WSFE), online store identifiers and API access tokens (TiendaNube Store ID and tokens), and banking or financial API credentials (BCRA, bank statements).
b) System Users and Operators (Merchant Staff)
- Authentication and credentials: username, password secured with strong cryptographic hashing (SHA-512), change history, and expiration policies.
- Personal identification: first and last name or user description, corporate or personal email.
- Roles, permissions, and traceability: profiles, assigned permission groups and privileges, and activity audit logging recording timestamp and user for record creation, deletion, modification, or reopening.
c) Customer and Final Buyer Data (B2B and B2C)
- Personal and tax identification: full first and last names, company name, identity document type and number (DNI, Passport, Identity Card), tax ID (CUIT/CUIL/CDI), nationality, and VAT status.
- Contact and communication: email address for invoice and quote delivery, landline and mobile phones with area codes, website, and secondary contacts (name, position, tags, alternate contacts).
- Address and geolocation: street, number, floor, apartment, neighborhood, postal code, city, province, country, official tax address verified with ARCA/AFIP, geographic coordinates (GPS) for logistics, and secondary delivery addresses.
- Customer self-service portal: password secured with SHA-512 cryptographic hashing, document delivery preferences, and assigned commercial conditions (price lists, bonuses, discounts).
- Financial information and current account: credit/debit balance, pending and settled receipts, alerts and credit limits set by the merchant (yellow and red warning thresholds, balance limits, and portfolio check limits).
d) Supplier and Contractor Data
- Identification and contact: company name, contact/owner name, CUIT/CUIL, VAT status, withholding and tax perception regime (Income Tax, VAT, IIBB/ARBA), email, telephone, mobile phone, address, and city.
- Banking details for payments: Single Banking Code (CBU), bank account number, financial institution, and descriptive transfer details.
- Tax information: withholding/perception exemption certificates and percentages with validity dates.
e) Transactional and Billing Data
- Transaction details: document type (Invoices A/B/C/M/E, Debit/Credit Notes, Receipts, Delivery Notes, Quotes, Purchase Orders), point of sale, legal number and letter, issue and due dates, line items, quantities, unit prices, subtotals, VAT rates (21%, 10.5%, 27%, 0%), exempt amounts, perceptions/withholdings, currency, and exchange rate.
- Official tax details (ARCA/AFIP): Electronic Authorization Code (CAE or CAEA), tax expiration date, and 2D barcode containing fiscal data.
- E-Commerce integration: external order ID and external payment status.
f) Logistics, Shipping, and Delivery Confirmation
- Shipping destination: delivery address, postal code, city, assigned logistics zone, scheduled delivery date and warehouse departure time.
- In-transit goods traceability: Transport Operation Code (COT - ARBA), carrier and vehicle details, and declared freight value.
- Confirmation and receipt: receiver full name, identity document number, and digital signature or graphical proof of receipt.
g) Financial Data, Payment Methods, and Collections
- Cash management: cash inflows and outflows by branch office.
- Banking transactions and wire transfers: payment receipt or bank reference number, payer/beneficiary name, origin and destination bank accounts.
- Check management: check number, issuing bank, branch, amount, issue date, collection/payment date, drawer name or CUIT, and check status (in portfolio, deposited, endorsed to third parties, rejected).
h) Technical Traceability, Security, and Auditing
- Session and security tokens: JWT (JSON Web Tokens) cryptographically signed with HMAC-SHA256 containing user ID, company ID, and username, plus password reset tokens expiring after 24 hours.
- Operational logs: outbound email logs with attached invoices, system error logs and tax authorization attempts, and document reopening history.
3. Purposes of Data Processing
| Data Category | Specific Purpose in the ERP |
|---|---|
| Merchant and user data | Service contract administration, user authentication, profile and permission control, change audit logging, and technical support. |
| Customer and final buyer data | Issuance of fiscal invoices, current account tracking, product delivery, collections, and customer self-service portal access. |
| Supplier and contractor data | Issuance of purchase orders, calculation and application of tax withholdings, and payment settlements via bank transfer or check. |
| Billing and transaction data | Compliance with tax regulations and electronic invoicing mandates before ARCA/AFIP, and operational accounting records. |
| Logistics and delivery confirmation | Delivery route planning, issuance of transport operation codes (COT) with ARBA, and reliable proof of receipt of goods. |
| Collections, accounts, and checks | Bank reconciliation, portfolio check and payment instrument management, balance monitoring, and cash control by branch. |
| Technical traceability and auditing | Session security enforcement, unauthorized access prevention, transaction integrity verification, and error logging. |
4. Legal Basis for Processing
Data processing in Edit ERP is grounded in the provisions of Law No. 25,326:
- Execution of a contractual or commercial relationship: necessary to deliver the ERP software service to merchants, and for merchants to execute sales, purchases, and services with their customers and suppliers (art. 6 inc. c).
- Compliance with legal and tax obligations: electronic invoicing mandates, authorization codes (CAE/CAEA), tax withholdings, and cargo transport codes (COT) mandated by ARCA/AFIP, ARBA, and relevant fiscal authorities (art. 5 inc. 2.b).
- Consent and merchant relationship: where applicable, obtained by the merchant user from its own customers and staff.
- Legitimate interest and IT security: database integrity protection, transaction traceability, and prevention of fraud or unauthorized access.
5. Final Buyers: Exclusive Use and Non-Commercialization Guarantee
Express commitment regarding final buyers' data: Personal data of customers and final consumers registered in the ERP is processed solely and exclusively for operational, transactional, accounting, and logistical management of the merchant that registered them. Under no circumstances is this data sold, assigned, rented, or shared with third parties for commercial, advertising, or profiling purposes. It is transmitted only to the public authorities and technical infrastructure providers specified in section 7, and solely to the extent indispensable to satisfy legal invoicing mandates or execute operations requested by the merchant.
Edit Software does not commercially exploit the customer databases of its merchants, nor does it share such information with other merchants or advertising networks.
6. High-Confidentiality Data and Sensitive Data Exclusion
The system processes certain data under reinforced confidentiality safeguards:
- Fiscal and banking credentials: digital certificates and private keys for ARCA/AFIP, e-commerce tokens, and banking API keys are stored for the exclusive technical execution of authorized communications.
- GPS coordinates and delivery signature: used strictly to confirm logistics deliveries, never for real-time tracking or advertising purposes.
- Banking details and checks: CBU codes, account numbers, and checks are processed confidentially for the sole purpose of settling or recording payments and collections.
- Exclusion of sensitive data: Edit ERP is a business and enterprise management platform. It is not designed to store or process sensitive data as defined under Article 2 of Law No. 25,326 (racial origin, religious beliefs, political views, health records, etc.). Merchant users are strictly prohibited from entering sensitive data into free-text fields.
8. External Integrations and Access Control
The merchant user maintains complete control over integrations activated in their ERP instance:
| Integration / Module | Credentials Used | Purpose and Disconnection |
|---|---|---|
| ARCA / AFIP (Electronic Invoicing) | Digital certificate and private key managed by the merchant. | Invoice generation and cryptographic signing. Certificate revocation in ARCA or request to support halts issuance. |
| TiendaNube (E-Commerce) | Store ID and API access tokens supplied by the platform. | Sales synchronization. May be revoked from the online store admin panel or by requesting disconnection via support. |
| Bank Reconciliation | Configured bank accounts and bank statement files. | Accounting transaction control. Configuration may be edited or deleted by the merchant. |
In addition, the platform provides granular role-based access control (RBAC), ensuring that merchant staff access only the modules and information relevant to their assigned responsibilities.
9. Data Retention
Information retention periods in Edit ERP are governed by the following criteria:
- During the term of the contractual relationship: merchant, operator, customer, and transaction records remain active in the database while the merchant maintains an active subscription and service with Edit Software.
- Tax and commercial legal obligations: pursuant to the Argentine Civil and Commercial Code and ARCA/AFIP regulations requiring the preservation of accounting books and fiscal invoices, transactional and billing data will be retained for applicable statutory periods, even after service termination.
- Security tokens: active session tokens are destroyed upon logout, and password recovery tokens automatically expire after 24 hours.
10. Data Subject Rights (Law No. 25,326)
Law No. 25,326 guarantees any natural or legal person the following rights regarding their personal data:
- Right of Access: to learn what personal data is held in databases and the purpose of its processing.
- Right of Rectification and Updating: to correct inaccurate or erroneous data and keep it up to date.
- Right of Deletion: to request the removal of data when no legal or contractual requirement obligates its retention.
Inquiries and Request Channel:
For data belonging to merchants or system users, requests may be sent to info@editsoftware.dev. For final buyers, suppliers, or delivery recipients whose data was entered by a merchant, requests should be directed primarily to that merchant (as Data Controller); Edit Software will assist the merchant in fulfilling technical execution.
In accordance with applicable law, access requests will be answered within ten (10) calendar days, and rectification or deletion requests within five (5) business days.
12. Service Termination and Data Deletion
Upon termination of the service agreement, the merchant may request data export and account closure via technical support. Once the process concludes, operational data is deactivated or deleted, preserving only those invoices and records required by prevailing tax and accounting retention laws.
13. Technical and Organizational Security Measures
Edit ERP implements technical and access safeguards to protect the confidentiality, integrity, and availability of information:
- Secure credential storage: passwords for ERP users and customer self-service portal accounts are protected using strong cryptographic hashing (SHA-512).
- Authenticated session tokens: authentication built upon JWT tokens cryptographically signed using HMAC-SHA256, binding user and enterprise identifiers.
- Password governance: password expiration controls, password change history, and temporary recovery tokens valid for 24 hours.
- Role-based access control: strict permission assignments by group and profile to prevent unauthorized internal access within the organization.
- Traceability and operation auditing: granular timestamp and user logging for every record creation, deletion, modification, or reopening, alongside operational error and tax authorization logging.
14. Changes to this Policy
Edit Software may update this Privacy Policy to reflect system improvements, new integrations, or regulatory changes. Any material change will be communicated to merchants through standard support channels and reflected in the updated date in the header.
15. Contact
For inquiries regarding ERP operations or data privacy:
- Email: info@editsoftware.dev
- Phone: +54 236-422-5126
- Address: Jorge Newbery 885, Junín, Buenos Aires Province, Argentine Republic
- Technical Support & Unlinking: standard support channel or via mailTickets configured in your instance.