Privacy

Operator / controller

Legal name, service address and privacy contact have not yet been supplied for publication.

contact@architectureprofessionalismatlas.com

Cookies, device storage and choices

Atlas uses authentication cookies for the sign-in session. Browser storage remembers requested interface choices such as language, network visibility and historical-map visibility. A session-storage handoff carries a selected map set into the research graph. Historical measurement drawings can be stored in IndexedDB (atlas-historical-measurements) on this device; they have no automatic expiry. Persistent interface settings remain until replaced or cleared; session storage normally ends with the browser tab. Clearing website data can remove local drawings and preferences and end sign-in; export anything you need first. These functions are separate from the optional measurement choice. Necessary storage for an explicitly requested function is assessed under §25(2) no.2 TDDDG; optional measurement requires consent.

Open privacy settings

Map searches, external images and public research records

Geoportal Berlin supplies map and cadastral data. Address queries are sent through Atlas to the Berlin address service; a fallback search can send the query to Photon (photon.komoot.io). Do not enter names or private case details in the address search. Direct map or external image requests can disclose your IP address and the requested resource to the provider. The browser sends no referring page under the Atlas referrer policy. Public project records identify their factual sources and, where available, image credits and licences. Professional names, roles, project participation and publicly documented career information may come from offices, project publishers, public registers and contributor submissions. Public availability does not remove data protection or copyright obligations. The operator must establish and document a lawful basis and fulfil Article 14 duties, including direct information where required; this general notice does not replace them.

Research visualisations and automated decisions

Graph positions and network edges describe selected data, sources and research assumptions. They do not decide access to employment, credit, insurance or another legal entitlement. The current Atlas code does not make solely automated decisions with legal or similarly significant effects under Article 22 GDPR. A network connection is not proof of a personal relationship, endorsement or wrongdoing. Corrections, objections and source challenges can be submitted through Report content.

Berlin data protection authority · complaint

Website measurement and account administration

Only after you enable optional measurement in Privacy settings, Atlas counts public page views in daily totals, grouped by page, broad traffic-source category and device category. The application does not store IP addresses, account identifiers, full referring URLs, URL query strings or visitor identifiers in these statistics, and sets no analytics cookie. Measurement is off by default. The choice is stored on this device for six months; you can withdraw it in Privacy settings at any time. The basis is your consent under Art. 6(1)(a) GDPR and, where applicable, §25(1) TDDDG. Withdrawal stops future measurement; already anonymous daily totals cannot be attributed to an individual. Do Not Track and Global Privacy Control signals are respected. Counts include repeat views and are not unique-visitor numbers. The aggregate window is 180 days; older totals are removed when a new view is recorded. Hosting and security providers process requests separately as described in this notice.

Only the authorised administrator can view the member directory, including account email, registration name, creation date, verification status, sign-in method, last authentication time and any linked Atlas profile. These existing account records support the account-administration purposes described below. Last authentication time does not indicate whether a person is currently online.

Account notices and acceptance records

When a verified account first signs in, Atlas sends the operator a membership notification containing its email address, sign-in method and account creation time. This supports account administration and abuse oversight; it is not a marketing subscription. These limited administrative and security purposes are based on Art. 6(1)(f) GDPR, with the interests of operating and protecting the service. You may object on grounds relating to your situation. Email copies also exist in the sending service and the operator’s mailbox; clearing an application delivery address does not erase those copies.

For email and Google accounts, Atlas records acceptance of the terms against the verified account, with the terms and privacy versions, selected language and timestamp. The confirmation includes adult eligibility. We do not collect a birth date or an IP address in this acceptance record. Publication and profile permissions remain separate. Acceptance evidence is kept while the account is used and thereafter only where and for as long as necessary for statutory obligations or legal claims. The bases are Art. 6(1)(b), and where applicable Art. 6(1)(c) or (f) GDPR.

Third-party information and exact locations

A public project may combine its exact address and parcel with costs, dates, description and a public profile. This can identify residents or project participants even without their names. The contributor’s consent does not replace another person’s rights or a valid basis for processing their data. Share only what is necessary and lawfully authorised; do not upload confidential client material, bank details, identifiable residents or sensitive personal information. If third-party data is received, the operator must assess the legal basis, Article 14 information duties or applicable exceptions, and removal where appropriate. People without accounts can contact us or use the reporting page.

Optional AI document analysis

In the restricted research workspace, an explicitly requested document analysis sends the selected PDF, image or text file, including its contents and potentially its filename, to OpenAI. The import does not archive the original in Atlas; reviewed extracted facts are saved only when you confirm them. This differs from uploading evidence to a project. Remove confidential and unnecessary personal data before analysis. The request uses store:false, but provider safety logs and applicable retention exceptions can still apply. Manual entry remains available. AI output can be wrong and requires human verification; it is not a professional, legal, permit or building-safety assessment.

Reports, rights requests and retention

Content reports and data-rights requests are handled using your contact details, the affected record and the facts needed to investigate and respond. Depending on the request, processing fulfils legal obligations under Art. 6(1)(c) GDPR or the legitimate interests in resolving complaints and defending legal claims under Art. 6(1)(f). We limit access and disclosure to what the case requires, and do not publish the reporter’s contact details. Correspondence is kept only while needed for the case and any applicable legal obligations or claims; it is not retained for unrelated marketing. The reporting form prepares an email on your device and does not submit data until you send it.

Full account deletion can be requested in account settings where the deletion service is available, or by contacting us from your account email and specifying the scope. We verify identity proportionately, coordinate removal across account, records, files and providers, and explain any legally necessary retention. Data-rights requests are answered without undue delay and normally within one month, subject to lawful extensions with notice. Removing a profile alone does not close the account. Backups and already downloaded public copies cannot be represented as instantly erased.

Account access

Atlas uses Supabase Auth for email/password registration, email verification, password recovery and sessions. When enabled, Google can also be used to sign in. Supabase processes the account identifier, email address and authentication data; the configured project region and any further processing locations require account-specific verification. Atlas links the verified account to its saved records and uses secure session cookies to keep you signed in. Passwords are not stored in Atlas project records. Removing the public profile does not remove the sign-in account; use full account deletion in account settings or contact us.

Atlas profiles and project discussions

After signing in to Atlas, you enter your first and last name as private account details and choose a public display name, an individual or office profile, and an optional short biography. Your account email is supplied by the sign-in provider and shown only in your own account settings. Your sign-in email is not shown publicly. The profile appears beside projects you submit for publication with profile consent and comments you choose to publish. Existing publications are not automatically given a public author. Comments and replies are visible with the published project; they are not private messages. Each comment is linked to its author account and creation time. Reactions are linked to your account so you can undo them; other visitors see only totals.

You can remove your comments. The editor can also remove comments; their text and displayed author are then cleared, while a removal marker preserves the reply structure. Removing your Atlas profile clears your reactions, comment text and project attribution but retains your saved projects and your sign-in account. Editing, deleting or withdrawing a published project removes its discussion. Avoid confidential documents and personal information about others in public descriptions or comments.

1. Private project records

Study Area 1 distinguishes completed and planned or ongoing work in your home without a permit requirement, and architectural services with an approval procedure. Home-work records include a title, description, address, optional floor and room, dates, costs and optional evidence. Optional contractor details include profession, company type and staff count. Architectural-service records additionally include HOAI object type, service phases, scale, planning fees, fee zones and approval details. Provide information about other people or companies only when authorised and necessary. Verification documents are optional; do not provide bank details. Private records and drafts are linked to the verified Atlas account. Selecting a parcel does not publish an address.

You may add up to four project images to a saved project or draft. Images are stored separately and are private by default. At submission, the editor can review them. The upload interface resizes them and removes embedded location metadata. Images are excluded from study statistics and can be removed individually. Deleting a project through Study Area 1 also deletes its images.

The legal basis for account access and the private workspace requested by you is Art. 6(1)(b) GDPR. Private storage is separate from permission to contribute. No marketing subscription is created.

2. Optional comparison contributions

A separate voluntary consent (Art. 6(1)(a) GDPR) is required for submitting completed costs. Curators receive exact amounts and limited comparison characteristics; account linkage is retained internally to manage withdrawal. Street address, district, contact details, private record title and documents are excluded from this snapshot. After review, only grouped results may be public.

Public results use fixed broad area/year groups, at least five distinct contributing accounts, and rounded medians. Individual prices and identities are not returned by the public endpoint. This is a disclosure-reduction measure, not a promise of absolute anonymity. Quotes never contribute to completed-cost results.

Project publication and editorial review · optional

At the end of the form, submitting for review saves your project and the consented preview with Pending status. Only an editor can approve publication. Saving a draft remains private and does not submit it. Editing and resubmitting an approved project returns it to Pending.

Private saving does not publish a project. The operator receives a creation notification containing a reference and a protected Atlas link. With a separate choice, you can submit a preview of selected project, scale, service, date and cost information for editorial review and publication. The editor additionally sees your project title, service-scope notes and evidence references. Project-party names and contact details are excluded. Submitted images and verification documents are shared with the editor. Each file has a separate choice: private, public after approval, or available on request. A request reveals the requester’s public profile name to the contributor, who can grant, decline or revoke access. Only that signed-in requester can use a granted download. Changing or removing a file, or resubmitting or withdrawing the project, invalidates previous file access. Requests are stored with the project, file version, requester, status and timestamps; withdrawal removes the requests. Previously downloaded copies cannot be recalled. Project submission includes the exact project address and confirmed parcel in the publication preview. Editorial approval publishes the project at that location on the map without a further visibility step. Do not include names or addresses in a public title. Review does not independently verify the underlying invoices or property rights.

Publication and location sharing rely on your explicit consent (Article 6(1)(a) GDPR). The preview shows the information to be published. You can withdraw it; editing or deleting the source record removes its publication and requires a fresh submission. Previously downloaded copies held by others cannot necessarily be recalled. Quotations remain labelled as quotations and do not enter final-cost statistics.

Resend sends a confirmation to the account email supplied by the sign-in provider when an Atlas profile is created, when a project is first saved privately, and once per submission for editorial review. The message contains a confirmation, an Atlas link and, for projects, a record reference. It includes no project addresses, fees, documents or private notes. A pending recipient address is stored with the delivery status and cleared after the sending service accepts the message. The operator receives a separate new-project alert. An email failure does not remove your saved profile or project.

3. Storage, withdrawal and your rights

You can export, correct or delete private pilot records. Deleting or editing a record removes its shared snapshot; a changed record requires fresh submission and review. Withdrawing a contribution removes it from active shared calculations while retaining your private record. Active records and drafts remain until you delete them or close the account. Closing the service requires notice and an opportunity to export, unless urgent legal or security reasons prevent this. Uploaded files can be downloaded from the project; the account JSON export contains application records, not file binaries or provider logs. Profile removal and account deletion are different operations. Provider backup and log expiry must be confirmed separately and is not an immediate-erasure promise.

Subject to the GDPR conditions, you may request access, rectification, erasure, restriction and portability, object to processing based on legitimate interests, and withdraw consent for future processing. Withdrawal does not affect prior lawful processing. Contact the controller above. You may complain to a supervisory authority, including the Berlin Commissioner for Data Protection and Freedom of Information.

4. Hosting, sign-in and processors

Atlas uses Supabase Auth for account access, with optional Google sign-in, and Sites with Cloudflare-backed hosting, database and file storage. Resend currently handles Atlas transactional notifications; authentication emails are handled by the configured Supabase delivery service. Google processes sign-in under its own applicable terms and privacy information. Supplier roles, contracts, processing locations, transfer safeguards and backup/log retention require account-specific verification. No EU-only processing or zero-retention promise is made.

Account-specific processor contracts, international-transfer arrangements and provider retention schedules have not yet been confirmed in this notice. Contact the operator for the current arrangements; this is an outstanding information requirement, not a restriction on public access.

5. AI, map and campaign links

The homeowner form does not call AI. Its parcel map uses Geoportal Berlin: opening the map requests map tiles from that provider and may disclose the network address and map extent. Address and parcel queries are processed through the Atlas map service. In the separate Atlas AI assistant, submitted text is sent to OpenAI only when you send it; remove unnecessary names, addresses and banking details first. The service assistant uses store:false. This is not a zero-retention guarantee: provider abuse-monitoring logs may still apply. The separate research assistant may save conversations in your private workspace. API data is not used for model training by default under the provider policy.

The map/research page uses its displayed map providers; opening it can create network requests to those services. The pilot adds no advertising pixel, cross-site tracker or marketing cookie. Supabase sign-in and hosting security use necessary session storage where required for the requested service. Only if you tick the separate optional box, a whitelisted campaign code from your incoming link is saved with a record to evaluate recruitment; no click ID, fingerprint or marketing mailing list is collected by the pilot code.