A quiet site still leaves a trace.

Who is responsible?

Artificially.cloud is currently an independently operated editorial project. It is not represented as an LLC, corporation, or other incorporated entity. For this public preview, Artificially.cloud is the operating identity and controller for the limited processing described in this notice.

If a legal entity later becomes the operator, this notice will be updated before that transfer takes effect.

What reaches the service?

When you request a page, ordinary delivery information may be processed automatically by Hostinger and its content-delivery and security systems. Depending on the request, this can include:

• network address, request time, request method, requested path and query;
• response status, response size, and response time;
• browser or device information derived from the request; and
• approximate country derived from the network address, plus browser and risk signals used to detect attacks, scrapers, and malicious automation.

The Atlas and Directory can place selected public filters in the page URL so a view can be reloaded, shared, or revisited. Those selections can therefore appear in an ordinary request. New Cloud Index searches use the fragment after # instead. Browsers do not send that fragment in page requests or referrer headers, but anyone you share the full address with can read it. Older Cloud Index links with ?query= can still send their query on the initial request; the page moves it to the fragment after loading. This does not erase earlier server logs or browser history. The Ownership Ledger accepts short asset labels and issue observations locally, but its script does not place those values in a URL or submit them to the service.

Why is it processed?

Request data is used to deliver pages and assets, maintain reliability, diagnose errors, enforce rate and security controls, prevent abuse and distributed denial-of-service attacks, and meet legal obligations. Where EU or UK data-protection law applies, these limited purposes rely on the legitimate interests in operating and protecting a public website. Artificially.cloud does not use this data to profile readers or measure them for advertising.

Who receives it, and where?

The site is hosted and delivered by Hostinger. Hostinger and its authorized subprocessors may process request data to provide hosting, network delivery, security, support, and related infrastructure. Processing may occur in the United Kingdom, European Economic Area, and other jurisdictions used by Hostinger and its subprocessors.

Where required, Hostinger's Data Processing Addendum incorporates the European Commission's Standard Contractual Clauses and the UK International Data Transfer Addendum. Information may also be disclosed when legally required or necessary to protect the service and its users. Artificially.cloud does not sell this information.

Cookies and local storage

The Artificially.cloud application does not set cookies and does not use session storage, IndexedDB, or a service worker. The Ownership Ledger review prototype offers one optional local-storage record under the key artificially.assetOperations.v1. Nothing is saved until you select “Keep my local ledger in this browser.” That record can hold only short names, broad place labels, issue notes, urgency, dates, and local status. It is not sent to Artificially.cloud, added to the Cloud Index, or synchronized to another device.

Do not enter a street address, access code, VIN or hull identifier, registration or license number, account or insurance number, financial information, personal contact details, precise location, telemetry history, or document contents. Browser storage is not a private vault: another person using the same browser profile may be able to see it. It is not backed up by Artificially.cloud.

The local record remains in that browser profile until you use Erase local ledger, clear the site’s browser data, or remove the browser profile. Turning persistence off removes the saved copy; the current in-memory page state lasts only while that page remains open. If storage is unavailable, full, malformed, or from an unknown version, the interface falls back to an in-memory session and offers a reset.

The Intelligent Room offers a separate “Check this browser” control for VR readiness. Nothing is checked on page load. After you activate it, the page requests its own scene-description file and asks the browser whether immersive VR is supported on the current device. It does not request a headset session, collect headset pose or controller movement, scan the room, use a camera or microphone, or save the answer. The browser or headset platform may handle that support query under its own software and privacy terms.

That provider cookie is used for security and service delivery, not advertising or behavioral analytics. Because it is strictly necessary for the requested service and its protection, this preview does not display a consent banner. If a nonessential cookie, analytics service, or tracker is introduced, this notice and the consent approach must be reviewed before it is enabled.

Separately, Hostinger's CDN may show a browser-verification challenge when security conditions warrant it. A successful challenge may store a verification cookie so the visitor is not immediately challenged again.

How long is request data kept?

The application does not create its own visitor database. Optional Ownership Ledger records remain in the visitor’s browser until erased as described above. Hostinger makes recent access information available through its hosting dashboard, but the visible dashboard window does not establish the provider's complete backend deletion schedule. Provider-held information is retained according to Hostinger's operational, security, contractual, and legal requirements.

Artificially.cloud does not routinely export raw access logs. If a limited export is required to investigate an incident, access will be restricted, unnecessary query values will be redacted where practical, and the working copy will be deleted when the incident and any required legal preservation period end.

Your choices and rights

Depending on where you live, you may have rights to ask about, access, correct, delete, restrict, or object to processing of your personal information, and to complain to an applicable privacy regulator. Artificially.cloud does not discriminate against anyone for making a privacy request and does not sell or share personal information for cross-context behavioral advertising.

You can erase the optional local ledger yourself from the Ownership Ledger controls; because Artificially.cloud never receives that record, the editor cannot retrieve or erase it remotely. The site currently has no public email address or contact form. This notice will be updated when a dedicated contact channel is available.

External links, children, and changes

Source links lead to independent websites with their own practices. Artificially.cloud normally sends only the site origin as the cross-site referrer, not the full article path or Atlas query, but the destination controls its own collection after you leave.

This is a general-audience editorial publication and is not directed to children under 13. The local Ownership Ledger is an adult-oriented interface study; it should not be used to record information about another person.

This notice will be revised when the operator changes, the site adds a new data flow, or provider behavior materially changes. The effective date at the top identifies the current version. A material change will be made conspicuous before or when it takes effect where required.