AP Atlas · 2026-10-13.1 · EN
Historical text version. Current operator details and contact information are on the live legal pages. Impressum · Terms · Privacy
Version 2026-10-13.1
Operator identification and account-specific processing information are not yet complete. The service is publicly accessible; this notice does not mean that contributions are closed. Please use the contact below for privacy or rights concerns.
Legal name, service address and privacy contact have not yet been supplied for publication.
Atlas participation is for adults aged 18 or over. After sign-in, both Google and email users accept the current terms for their verified account before new contributions or other covered changes. Public browsing does not require acceptance. Reading, exporting, deleting or withdrawing existing records remains possible without accepting a new version. Acceptance does not itself publish anything or authorise marketing, new research purposes or model training. Earlier versions are available below.
AP Atlas helps adults document completed, planned and ongoing work in their homes and architectural services in Berlin. A practice record describes a particular commission or service at a place and time. It does not represent an entire building or the complete professional activity of an architect or contractor. Several practices may be recorded on one parcel. Comparisons are descriptive: they are not binding quotations, valuations, price recommendations or guarantees of equivalent services or building quality. Atlas does not broker building contracts. Self-selected contributions do not represent the whole market.
Participation in the current Atlas service is free. Any future paid service would require a separate agreement; participation does not automatically become a paid subscription. Clients, owners, architects, contractors and other participants may contribute information they are entitled to share. Anyone acting for an organisation must be authorised to do so. Private account details and the chosen public profile are separate; the sign-in email is not displayed publicly.
Provide information you know or are authorised to use. Distinguish known facts, estimates and personal assessments; label quotations and final costs correctly. Remove unnecessary personal information and confidential material from text, filenames, images and documents before sharing. Ownership of a building does not automatically grant permission to share an architect’s plans or a photographer’s images.
The submission preview shows the information to be published, including the exact project address, parcel and public profile. Submission sends this preview for editorial review. Approval publishes it directly on the map without another visibility step, while public publication is enabled. A dot indicates that the parcel contains records; clicking the dot or parcel opens its practice list, from which visitors select an individual practice. “Editorially approved” means approved for publication. It does not independently verify invoices, costs, ownership, legal compliance or building quality.
Publishing a practice does not publish all its attachments. For each file, choose private, public after approval or on request. Submitted files are available to the reviewing editor. For files offered on request, the contributor grants, declines or revokes access for the requesting account. Permission to view or download does not itself grant permission to republish. Changing a file or its sharing choice requires resubmission and revokes previous access. Copies already downloaded cannot be recalled.
Rights remain with you or the relevant rights holder. You grant Atlas only the non-exclusive permission needed to store, process and technically format your content for the private workspace and, with your separate consent, publish the preview and the files you have chosen to share. Separately consented grouped comparisons follow their own stated scope. This does not grant blanket permission for advertising, social-media promotion, disclosure to other organisations or general AI model training. The pilot entry form does not call AI. Additional uses require a separately stated basis and, where necessary, separate permission.
You may share links to records. Public availability is not a general licence to republish photographs, plans, documents or collections. Attribution alone does not replace any permission that is required. Reuse, including bulk collection, commercial reuse and model training, depends on the relevant rights, licences and applicable statutory permissions. This text does not impose a blanket ban on legally permitted automated analysis. User contributions, open datasets, software and third-party materials retain their respective rights and licences. No exclusive rights in raw facts or mathematical methods are claimed.
Project discussions are public. Keep comments relevant and share only text you may publish, without other people’s private information. You retain rights in your comments and permit their display with your public profile until removal. The editor may remove unlawful content, personal data shared without permission, harassment or spam. Anyone, including people who did not submit the record, can report inaccurate attribution, rights concerns or personal data using the contact below. Include the record link or reference, the affected content and your reason. You can use the same contact to ask for an explanation or reconsideration of an editorial decision.
Report a record or request a correction · contact@architectureprofessionalismatlas.com
You can correct, export or delete your saved records and withdraw a publication while keeping the private record. Editing or deleting the source record removes its publication; publishing changes requires another submission and review. Removing your Atlas profile clears profile attribution, comment text and reactions, but does not delete saved projects or your sign-in account. Delete projects separately if you want them removed too. Processing and retention details are explained in Privacy. Future features and any changed uses will be described separately; these terms do not grant unrestricted future rights. Mandatory statutory rights remain unaffected.
Exact location and costs may reveal information about occupants and project participants. Before submitting, check permissions, confidentiality duties and the rights of clients, residents, architects and photographers. An uploader’s declaration does not transfer another person’s rights to Atlas. Public file credits are shown to visitors; the file-rights explanation is available only to the contributor and reviewing editor. State the licence or permission basis without uploading private agreements or unnecessary contact details. A file offered on request still needs a lawful sharing basis. Editing rights or credit information invalidates its old access version and requires a fresh project submission.
Use the reporting page or email contact for unlawful content, privacy, copyright or attribution concerns. Give the exact content link or record reference, an explanation and a reply address where possible; confirm that your notice is accurate and complete to the best of your knowledge. Reports are assessed case by case. Measures may include requesting corrections, temporarily restricting access or removing content. Editorial decisions must identify the relevant content, reason and measure; urgent action can precede a response where legally necessary. Contributors can read publication decisions in My projects and request an explanation or reconsideration by email. Reporters should receive acknowledgement and the result through the supplied contact. Where relevant, available statutory complaint and court remedies remain unaffected. This process is not a promise to validate every underlying invoice, right or legal issue.
You may stop using Atlas, withdraw publications and request account deletion. Atlas may restrict an account for unlawful use, serious or repeated breaches, or concrete security risks; measures should be proportionate and explained, with a route to request review. Material service or terms changes are communicated before they take effect where reasonably possible. A new use of content is not authorised by silence or by a change to this page. If the service is discontinued, users should receive reasonable notice and an opportunity to export unless urgent legal or security duties prevent this. Statutory consumer rights remain unaffected, including where applicable to a free digital service.
Atlas provides documentation and research tools, not commissioned architectural, valuation, tax or legal advice. User reports, comparisons and AI outputs can be incomplete or inaccurate and must not replace project-specific professional assessment. These descriptions do not exclude mandatory statutory liability. Liability for intent, gross negligence, culpable injury to life, body or health and other liability that cannot lawfully be limited remains unaffected.
Version 2026-10-13.1
Operator identification and account-specific processing information are not yet complete. The service is publicly accessible; this notice does not mean that contributions are closed. Please use the contact below for privacy or rights concerns.
Legal name, service address and privacy contact have not yet been supplied for publication.
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.
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.
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.
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.
For full account deletion, contact us from your account email and specify 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.
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 primary Auth project is hosted in Ireland. 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; contact us to request account deletion.
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.
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.
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.
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.
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.
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.
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.