English translation of the prepared Spanish document, version 2026-09-06.3. This is not a new contract version or a record of acceptance. Read the Spanish source

Privacy and storage — version 2026-09-06.3

Status: prepared text, awaiting full controller details and verification of the provider and retention inventory before contractual use.

Controller for requests, accounts, support and its own administration: Sergio del Pozo Alvarez / Azprojs, Spain. Contact: contact@azprojs.net. Confirmed professional address and full identification details must be added. For contacts in a customer's workspace, that customer is the controller and Lead Relay acts as processor.

Purposes and legal bases

Data requested when asking for information or purchasing is used to handle that request and prepare or perform the contract. User and support data is used to provide the service. Minimal technical records are used for security and abuse prevention under legitimate interests, with data minimisation and balancing of interests. Records required by law are retained to meet legal obligations. Acceptance of the notice is not treated as general consent for other uses.

No campaigns are carried out on the basis of supposed permission arising from visiting the website. A published business address does not by itself authorise promotional emails. Electronic commercial communications require a permissible basis under the Spanish LSSI as well as the GDPR, sender identification and an easy way to object. Recipients who object must remain on the suppression list.

Data, sources and recipients

Contact details and context supplied by the person, the relevant account and workspace, support information and technical records are received. Third-party data added by a customer is governed by that customer's notices and instructions. If the controller obtains data by another route, it must provide the information required by Article 14 or document the applicable exception.

The infrastructure uses Supabase and Render. Communications may use Resend, ImprovMX and Google depending on the route. Polar manages payments and invoicing under its own obligations. GitHub is used for code and documentation without real customer data. Microsoft or another provider is not considered active merely because integration code exists. The individual annex must detail entities, locations, safeguards and retention; there is no promise that all data remains in the EU without verification.

Retention and rights

Retention depends on the purpose: the contractual relationship and necessary support; operational data according to instructions and agreed retention; legal obligations for the applicable period; and the minimum suppression data needed to respect objections. Specific periods must be set and checked by category, including requests that do not convert, logs and backups. Automatic deletion is not claimed without a verified execution.

Access, rectification, erasure, objection, restriction, portability where applicable and withdrawal of specific consents may be requested at contact@azprojs.net. A paid plan is not required. Responses are provided within the legal deadline, with any justified extensions and corresponding notification. A complaint may be lodged with the Spanish Data Protection Agency, www.aepd.es. Additional identification is requested only when proportionate and necessary.

No automated decisions with legal or similarly significant effects are made. Real data is not added to support AI tools without verifying purpose, contract, safeguards, permissions and necessity. The customer retains supervision of its commercial actions.

Browser

Acquisition analytics is suspended: the web client does not create analytics identifiers or send visit events. Browsing is not interpreted as consent. The product uses functional storage for session, device and preferences; each use must be explained before optional measurement is reactivated. External providers, including checkout, have their own notices. No blanket exemption is claimed for any future storage.