DD Scenery GeneratorSign in ↗

Data & access policy

Updated 10 November 2026

Accounts and access

Drzewiecki Design operates this portal. Accounts can be created through a desktop installation request or issued by an administrator. New installation requests require administrator approval before desktop access is granted. Use a non-personal username and account label; no real name, email address, postal address or telephone number is required. The portal stores password hashes, access permissions, activation status and sign-in times. Existing account labels remain editable by the administrator.

The private console uses a necessary session cookie (HttpOnly, Secure and SameSite Strict). Sessions expire after 30 minutes without activity or eight hours in total. Visible console refreshes count as activity. DDSG does not load analytics, advertising scripts or tracking pixels.

Installations and retention

Each paired copy has a random installation ID. New copies use this ID as their label; the Windows computer name is not sent. Existing labels are retained. The portal stores the owning account, credential hash, permissions, app version, connection times and cumulative operation counts. Project and recovery files stay on the computer. When you explicitly start AI research or geometry generation, the relevant project context and evidence are sent for that task as described below.

Account and installation records are kept while access is administered; contact Drzewiecki Design when access or records are no longer required. Security events are retained for 30 days. Rate-limit buckets use keyed hashes and expire after 24 hours. Expired activation and pairing records are removed after 24 hours. Automatic cleanup runs at most hourly while the portal is in use. These are technical records, not anonymous data.

API allowances

Drzewiecki Design team accounts use an administrator-defined funding and spending policy. External accounts configure their own credentials and OpenAI spending limits. The portal keeps internal job cost limits, actual settled costs and opaque request identifiers for allowance accounting and retry protection while the account is administered. It does not store prompts, model output or project geometry in this ledger. Monthly periods use Europe/Warsaw time. API credentials are encrypted in the portal vault. External account holders can replace or remove their own credentials. Paid research and geometry generation start only through their explicit action buttons. Time and cost estimates are shown first. No money is reserved from the allowance. New paid jobs require a positive remaining allowance; a running job can finish above it before its actual usage is reported.

Search, imagery and hosting

The desktop sends place searches in a request body, rather than in its URL. Query text is not stored in the DDSG database or audit log. Older clients use URL queries. The hosting provider can process IP addresses and HTTP logs; hosting retention is separate from DDSG retention.

Map providers receive the locations of requested image tiles and network information. Their attribution, access conditions and privacy policies apply. Project files retain source identifiers rather than imagery. When explicitly requested, textured ground exports fetch and save imagery locally from the selected configured provider, together with source attribution. Google Maps use is subject to Google Maps terms and the Google privacy policy.

Reference collection checks nearby outdoor Google Street View coverage through the official API. For a configured Street View credential, DDSG relays sample coordinates and panorama requests to Google from the portal. External accounts use their own Street View credential. Photographs are held temporarily in desktop memory with attribution and refreshed when needed. Saved projects and scenery exports exclude these photographs. Enabling 3D terrain downloads elevation data from the applicable configured source. Terrain samples and source metadata are stored in the local project, and native exports retain the vertical reference.

Desktop installation credentials and pending request proofs use Windows encryption. Account passwords submitted for installation approval are not stored by the desktop. Portal API keys are stored in the encrypted vault. The shared DD Team Maps JavaScript key or an external account’s own key is supplied only to its approved desktop to render Google imagery. Other server service keys stay in the vault. Older locally configured browser keys are no longer read.

Material catalogs

The Drzewiecki Design Texture Library catalog and source textures are restricted to authorised team installations. The desktop app stores applied textures locally and includes them in saved project assets and textured exports. External accounts can link a prepared HTTPS catalog or index an online folder. The desktop app reads public HTTPS directory listings, downloadable Dropbox shared folders and OneDrive folders owned by the signed-in Microsoft account. Microsoft sign-in is read-only. After the user approves the estimate, DDSG sends material names, grouping metadata and selected image previews to OpenAI using that account’s key and spending allowance. DDSG retains the resulting personal catalog for matching.

AI research and geometry

Starting reference research sends area context, coordinates, source links and public collection outcomes to OpenAI through the authenticated portal. Starting geometry generation additionally sends the selected and corroborating imagery, kept reference images, their available metadata and mapped building evidence. Depth controls the visual reference limit. Older findings are sent for translation only when you start their translation action.

DDSG retains private analysis job state and results to support completion, recovery and accounting. Submitted image bytes are processed in memory and are not saved in the portal job record. The API provider processes requests under its service settings and retention policy. The allowance ledger stores numeric costs and opaque identifiers separately from job content. Local originals remain unchanged.

Contact

For access, correction or deletion requests, contact Drzewiecki Design through the website contact page. Account aliases and technical identifiers can still relate to individuals; data minimisation does not itself exempt this service from RODO/GDPR.

DownloadsData & access policy