BuiltBehind is a product operated by GRANTSCAPE s.r.o. Service-specific controller details and contacts are provided through the applicable account and customer agreement.
1. Website processing
The interactive application experience currently prepares a browser-side summary and does not itself submit the entered form information. Essential hosting, identity and security logs may still be produced to operate and protect the website and invited customer workspaces.
2. Who this notice covers
This notice covers website visitors, applicants, customer and partner contacts, support users and individuals who contact a customer using an authorised channel connected to BuiltBehind.
3. Information we may process
- Identity and contact information such as name, work email, telephone number and organisation.
- Application, sales, billing, contract and support records.
- Business workflow, booking and integration configuration.
- Customer-enquiry content processed under a customer’s instructions.
- Technical, device, security, access and audit information.
- Call or message records only where lawfully configured and clearly disclosed.
4. Purposes and lawful bases
Depending on the relationship and jurisdiction, processing may be necessary to take steps before a contract, perform a contract, comply with law, pursue legitimate interests such as service security and business administration, or act on consent. The final notice must map each purpose to its confirmed lawful basis before collection begins.
5. Controller and processor roles
BuiltBehind may act as controller for its own sales, account, billing and support records. When BuiltBehind processes a business customer’s leads under that customer’s instructions, BuiltBehind would generally act as processor and the customer as controller. A Data Processing Agreement must define these roles before production processing.
6. AI-assisted processing
The public BuiltBehind Support assistant currently answers a submitted question from a verified help set and does not change an account or make a quote. Future workflows may classify enquiries, generate responses, summarise conversations, qualify leads or route work. People must be told when they are interacting directly with AI where required. AI must not make undisclosed legal, medical, employment, credit or similarly significant decisions through BuiltBehind.
7. Sharing and suppliers
Information may later be shared with approved hosting, messaging, telephony, CRM, payment, analytics and AI suppliers, professional advisers or authorities where legally required. No supplier should be listed until contracted and technically confirmed. A public subprocessor register is required before production launch.
8. International transfers
If information is transferred outside the UK or European Economic Area, the operating entity must document the transfer mechanism and safeguards, such as an adequacy decision or approved contractual clauses, before transfer.
9. Retention
Information should be kept only as long as necessary for the stated purpose, contractual and support obligations, legal claims, accounting requirements and security. Final retention periods must be set by record category before live collection.
10. Your rights
Depending on applicable law, individuals may have rights to information, access, correction, erasure, restriction, portability, objection and withdrawal of consent. A verified request channel and response procedure must exist before public launch.
11. Complaints
Individuals should first be able to contact BuiltBehind’s privacy contact. They may also complain to the relevant supervisory authority. The lead EU authority cannot be named until the operating entity and establishment are confirmed; UK visitors can find guidance from the Information Commissioner’s Office.
12. Contact
Privacy requests relating to an active BuiltBehind account should use the verified support or privacy route supplied within that account or its service agreement.