RASTE

Website privacy and enquiry information

How RASTE handles website briefs, email enquiries and technical information.

What this notice covers

This notice explains how RASTE handles information when you browse the website, submit a contact enquiry, complete a website brief or share a plan from the interactive website planner. The studio offers website building and optional marketing services in English and Bulgarian. The forms collect information relevant to the request and save it to a private inbox. The planner can also be used without submitting contact details: its recommendation is calculated in your browser. The sections below explain the information used by those journeys, how the owner accesses requests and how to ask a question about information you have submitted.

Information in a website brief

The guided brief asks for your name, email address, business name, selected package, payment preference and project description. It also provides fields for an existing website, proposed pages, available content, reference links and visual preferences. You decide which optional details to provide. A request identifier helps recognise a retry, and the record includes the time of submission, the selected server-side price, the request status and an acknowledgement of the displayed delivery and revision summary. These details are used to understand the requested website and discuss the scope, not to publish your information as a public example.

How a brief is saved and accessed

When you submit the guided form, the website sends the entered information to its order endpoint. After validation, a request is stored in the website database. A success message includes a reference after the save has completed. The request inbox checks the signed-in owner identity on the server before returning records. Public pages do not contain the inbox data. The access restriction is part of the current implementation, but no internet service should be treated as a place to send unnecessary secrets. Keep the brief limited to the business information and materials needed for an initial website discussion.

Contact enquiries and website planner requests

The contact form stores your name, email, business details, selected service, budget information where supplied and the message you choose to send. The planner stores your contact details and answers only when you submit its request form. Those answers describe the business type, page count, languages, features, content readiness and preferred payment option. The package recommendation is checked again on the server when the request is saved. A submission identifier helps avoid creating duplicates when a request is retried. Neither the contact message nor the saved plan is published as a public example. Their purpose is to support a relevant conversation about your website.

Technical information and abuse prevention

The hosting and access systems handle the technical requests needed to serve the website and protect access to the website. The order endpoint checks the request origin, validates the submitted fields and limits repeated submissions. For that limit, the application derives an hourly hash from the connecting address and time bucket instead of storing the raw address in the order record. Rate-limit entries have expiry information and are removed in bounded cleanup operations. This description concerns the application’s own order and rate-limit data; infrastructure providers may handle additional technical information under their own service arrangements.

Fonts, illustrations and external links

The website uses self-hosted illustration assets and requests its web fonts from Google Fonts. Your browser contacts that font service when loading the typeface. The current build does not include advertising pixels or a visitor marketing analytics dashboard. The hosting platform and sign-in service are separate from the site’s own marketing code and may use technologies needed to provide access. Links to reference material or other external pages take you to services with their own privacy practices. Supplying an external reference link in a brief does not give the studio permission to access a private account behind that link.

Keep sensitive information out of project forms

A website brief or consultation request should describe the work rather than disclose credentials. Do not include payment card numbers, account passwords, identity documents, health information or private customer records. Choosing a package in a form expresses a preference; it is not a payment receipt. If a later stage requires access to a domain or an external platform, the access method should be agreed separately and limited to the task. The planner does not log into your current website or run a technical audit. Its recommendation uses only the answers you provide, and you can see that result without sharing your email.

Retention and requests about your information

The current brief database does not automatically delete an order after a short fixed period. Requests remain available for the project discussion and require owner action for removal or correction. Do not assume that closing the page deletes a submitted request. If you want to ask about access, correction or deletion, contact lubo21339@gmail.com and include the request reference where available. Describe the request without sending another copy of sensitive information. A response may require checking that the request concerns your own details. The website does not currently provide a public account page for editing stored briefs.

Changes to features and questions about data

Information handling should stay aligned with the features a website actually uses. A new payment service, analytics tool, email delivery provider or integration can change what information is processed and why. The relevant notice and configuration should be reviewed when that happens. This page describes the forms and planner currently offered by RASTE; it should not be copied unchanged as a policy for a different customer website. For a question about your request, use the contact form and include the reference if available. Explain which action or record concerns you without repeating unnecessary sensitive material in the new message.