How requests, infrastructure and analysis are handled.

• What happens after a request is submitted? Process and scope The request is reviewed before scope is confirmed. Nothing is charged or started at the submission stage.

  A submitted request is stored so it can be reviewed. The details provided are read to understand the scope, the provider needs and whether the work fits within what is offered.

  After the review, a response may be sent through the contact details provided. Scope, provider needs and payment details are confirmed at that stage, not before.

  Submitting a request does not create an obligation. Work begins only after the scope is confirmed in writing.

• Why infrastructure may involve external providers Infrastructure Domain, hosting, SSL and server resources are provided by specialised providers. Where required, these items may be arranged through them.

  Domain registration, hosting, SSL and server resources depend on infrastructure operated by external providers. Arranging these items through those providers is normal and expected.

  The work is not limited to resale. It covers selection, configuration, alignment with the confirmed scope and handover.

  Provider rules, pricing, account limits and interruptions are set by those providers and are outside Grau's control.

• Domain, DNS and hosting responsibilities Domain and DNS Domain ownership, DNS records and hosting each carry separate responsibilities. Clear ownership avoids confusion later.

  • Domain registration is held in a registrar account. Ownership and renewal of the domain stay with the account holder.
  • DNS records point the domain to the correct hosting or services. Changes to DNS take time to propagate.
  • Hosting stores the website files and serves them. Hosting and domain can be with the same or different providers.
  • Where these items are arranged within a confirmed scope, the setup and handover are documented so the account holder keeps control.
• SSL setup and renewal scope Hosting and SSL SSL enables encrypted connections. Setup can be arranged within scope; renewal depends on the provider and certificate type.

  An SSL certificate allows the site to be served over HTTPS. Many hosting environments offer certificates that renew automatically.

  Where SSL is arranged within a confirmed scope, installation and correct configuration are covered.

  Renewal behaviour depends on the provider and certificate type. Certificates that do not renew automatically require attention before they expire.

• VPS / VDS selection basics VPS / VDS A VPS or VDS gives dedicated resources for heavier workloads. Selection depends on load, location and whether it is managed.

  • A virtual server provides dedicated CPU, memory and storage separate from shared hosting.
  • Expected load determines the resources needed. Under-sizing causes slowdowns; over-sizing adds cost.
  • Server location affects latency for the target audience.
  • Managed setups include provider-side maintenance; unmanaged setups leave server administration to the account holder unless a separate scope is agreed.
• What technical SEO can and cannot guarantee SEO Technical SEO improves structure, crawlability and measurement quality. Search ranking is not guaranteed.

  Technical SEO work covers site structure, crawlability, indexation signals, page metadata and measurement setup.

  These changes make it easier for search engines to read and understand the site.

  Ranking depends on many factors outside any single site, including competition and search engine changes. For this reason, search ranking is not guaranteed.

• What social media analysis includes Social media analysis Social media work covers analysis and reporting. Account management or advertising is not included unless separately confirmed.

  • Analysis reviews existing accounts, content and available metrics.
  • Reporting presents findings in a readable format with observations.
  • Account management, posting and advertising are separate activities and are not included unless a separate scope is confirmed.
• Payment methods after scope confirmation Payments Payment details are shared only after the requested scope is reviewed.

  Payment details are shared only after the requested scope is reviewed. Depending on the confirmed scope, payment may be made through IBAN/bank transfer, CepBank, easy address transfer or payment link. The website does not collect card numbers, banking passwords or sensitive payment credentials.

  Third-party bank or payment provider rules, delays, fees or interruptions are outside Grau's control.

• What changes after delivery mean for scope Process and scope Changes made after delivery fall outside the original scope. New work requires a separate confirmed scope.

  • The confirmed scope describes what is delivered. Once delivery is complete, that scope is considered met.
  • Later customer changes, third-party edits, panel or DNS changes, code changes or unauthorised edits are outside the original scope.
  • Maintenance, monitoring and support require a separate written scope.
• How long contact form data is kept Process and scope Contact form submissions are kept for 12 months and then removed. The site does not collect payment card data.

  • Submitted requests are stored so they can be reviewed. Stored data includes the details entered in the form, together with IP address, user agent, timestamp and language for security and record purposes.
  • Submissions are kept for 12 months and then removed.
  • The site does not collect card numbers, banking passwords or sensitive payment credentials.

No entries match.