Privacy policy

The relevant legislation is Regulation (EU) 2016/679 (GDPR), Spanish Organic Law 3/2018 (LOPDGDD) and, insofar as applicable to the site and electronic communications, Spanish Law 34/2002 (LSSI-CE). This information must reflect the operations actually performed; citing these rules does not, by itself, demonstrate compliance.

The form requires full name, company, work email, main objective and a description of the technical challenge. These are needed to prepare an enquiry with context; the form will not generate a draft if they are incomplete. You can alternatively contact us directly by email.

Role or position, telephone, technology stack, approximate system age, operational criticality, automation level and engineering team size are optional. Other information you voluntarily include in email correspondence may also be received.

As you type, values remain in the browser page. The application does not record them in a database, cookies or local or session storage. Preparing the email includes these values in a draft through a mailto link. A compatible app may open, but opening it does not demonstrate that the message was sent.

You must review and send the email from your own app. Only if it is sent and delivered does it become an enquiry received through ForgeTech's email workflow. The ‘Copy draft’ alternative places text on the clipboard at your request, without sending it. The browser, operating system and email app may manage their own data, autofill or drafts; their behavior is not entirely under ForgeTech's control.

We do not request health, biometric, ideological, political, religious or other special-category data, or passwords or credentials. Do not include them in an enquiry, or unnecessary third-party data or confidential documentation. Receiving unsolicited information does not mean its inclusion is requested or authorized.

Delivering the site requires technical requests to the hosting service, which may include IP addresses and connection metadata. The existence, content and retention of provider logs must be verified; this does not imply that fields typed into the form are sent to the host.

Professional enquiries: receiving and answering communications about software engineering and consulting, and handling requests relating to those services.

Technical assessment: understanding the initial context you choose to send, assessing whether ForgeTech can help and discussing possible next steps. No automatic audit or service commitment is generated.

Business correspondence: maintaining exchanges necessary for an existing professional relationship or to assess a possible collaboration.

Operation and security: meeting technical needs for delivering and protecting the site, limited to data necessary for that purpose. Details of infrastructure logs and operations require provider confirmation.

An enquiry does not register you for a newsletter or automatically subscribe you to marketing communications. No subscription or advertising tracking mechanism is implemented in this version.

The following allocation is a proposal for legal and company review before final publication. The applicable basis depends on who requests the action, the intended relationship and the data actually needed.

Article 6(1)(b) GDPR may apply when responding to a request for precontractual measures made by the data subject, if its conditions are met. It does not automatically apply to every B2B communication by a company representative.

For professional contacts and relationships with a legal entity, legitimate interests under Article 6(1)(f) may be considered, with the appropriate assessment of necessity, proportionality and rights. The presumption in Article 19 LOPDGDD is limited to necessary professional contact details and the purpose of maintaining a relationship with the entity; it does not, by itself, justify the entire technical description or any subsequent use.

For additional technical context and assessment of fit, the basis covering necessary personal information in each relationship must be confirmed. Such information is not presumed to be covered entirely by legitimate interests in professional contact.

Article 6(1)(c) may apply to specific legal obligations, such as handling rights requests and legally required retention. The relevant rule and scope must be identified in the corresponding procedure.

Technical operation and security could rely on a legitimate interest in protecting the service, limited to what is necessary and subject to assessing its conditions. This basis is not assigned to unverified logs. Generic consent is not used as the basis for all enquiries; if a future activity requires consent, it must be requested specifically and separately.

Retention criteria must reflect the time needed to answer the enquiry and, where applicable, manage the professional or precontractual relationship. If the relationship does not continue, the need to retain the information must be reviewed.

The email service's review and deletion periods and practices remain subject to operational confirmation. No automatic deletion or verified technical retention period is announced for this website.

Where erasure is appropriate, legal retention or restriction obligations may remain for addressing liabilities during the required period. An erasure request therefore does not necessarily mean the immediate and unconditional deletion of all information.

The new site's configuration uses Microsoft Azure Static Web Apps to host and deliver static content. This role concerns technical browsing requests; no API is implemented to receive the assessment form's contents.

If you send a message and it reaches ForgeTech's mailbox, its email service is involved. The current provider, authorized persons, processing terms and subprocessors must be confirmed with the company before this information is finalized. Hosting the website does not, by itself, identify the email provider.

Domain or DNS administration is distinct from hosting and email. It does not, by itself, establish that its administrator receives the technical challenge description. Each provider's exact relationship and data access must be verified separately.

Data may be disclosed where a specific legal obligation exists and to the extent it requires. This version includes no CRM, enquiry database or external form-processing service.

The territorial scope of services, support and possible subprocessor access depends on contracts and configuration. It has not been verified that all such processing is limited to the European Economic Area; the absence of international transfers is not asserted.

The company must confirm the flows and, if transfers subject to the GDPR occur, identify their basis, applicable safeguards and how to obtain information about them. No unverified residency guarantees, contractual clauses or specific certifications are asserted. This issue remains pending review before final publication.

You may request access, rectification, erasure, objection and restriction of processing. Portability applies where its legal conditions are met. Where processing relies on consent, you may withdraw it without affecting the lawfulness of processing before withdrawal.

Send your request to ForgeTech's contact email on this page, explaining the right you wish to exercise. Its scope and possible exceptions will be assessed under the GDPR. An identity document copy is not automatically required: proportionate additional information may only be requested where reasonably necessary to verify identity.

You may also lodge a complaint with the Spanish Data Protection Agency. Contact and supervisory authority links appear at the end of this page.

Data protection requires technical and organizational measures proportionate to the nature of the data and processing risks. Their application to email, access and internal procedures must be confirmed in the company's review; no security certification is asserted.

The implementation limits fields and lengths, validates the draft and adds no application persistence or logs of their values. HTTPS encryption protects transport where used, but does not by itself guarantee comprehensive security of the device, email or all processing. No system can promise zero risk.

The implemented workflow does not automatically assess acceptance of requests or profile enquirers. Field validation and draft generation prepare a message; they are not automated decisions producing legal or similar effects. Features of other applications are not used to score these enquiries.

The policy may be updated when legal requirements, services or actual processing operations change. Before enabling an enquiry backend or other significant changes, the relevant providers, flows, bases, periods and notices must be reviewed. The date shown identifies this document version, not a historical publication date.