Privacy Notice
1. Controller
The controller for personal data processed in this application is:
accuras GmbH
Henkestr. 91
91052 Erlangen
Germany
E-mail: info@accuras.de
Telephone: +49 9131 933 0214
Managing directors: Tobias Zobel
We have not appointed a data protection officer because we are not required to (Art. 37 GDPR, § 38 BDSG). Please send data protection questions to info@accuras.de.
Roles
This application is deployed by organizations — hospitals, campuses, event operators — to offer wayfinding to their visitors.
- For data arising from use of the visitor app, accuras GmbH is the controller within the meaning of Art. 4(7) GDPR.
- For the shared accuras account and sign-in, accuras GmbH is the controller. The account can be used across Organizations.
- For an Organization's membership records, Page content, editing permissions, uploads and author history, that Organization is the controller and accuras GmbH processes the data on its behalf.
- For requests to accuras (section 2.12), accuras GmbH is the controller.
2. What we process
2.1 Delivering the application
Opening the application processes the connection data technically required to serve it: IP address, timestamp, requested resource, user agent.
- Purpose: delivery and operational security.
- Legal basis: Art. 6(1)(f) GDPR — legitimate interest in securely operating the service you requested.
- Retention: 14 days in operational monitoring (Grafana Cloud).
2.1.1 Link Scans and App Opens
When a Link is opened, for example by scanning a QR code with the phone camera or with the scanner in the application, the server records the ID of the Link reached and of the QR code scanned, where there is one, the Organization, the time, and whether the request is classified as direct or automated. When the application loads, it records the Organization, the time, whether the application was opened through a Link or another way, and the same classification. It examines the User-Agent during the request but does not store it. Neither the IP address nor an identifier of your device is stored, and nothing is stored on or read from your device. These requests are counted even without consent to usage analytics (section 2.3), and repeat requests are counted separately.
- Purpose: analysing usage for our business reporting: how often Links and the application are opened, including the share of automated requests.
- Legal basis: Art. 6(1)(f) GDPR. Our legitimate interest is business reporting on usage. Your interests do not override it because no IP address, User-Agent or device identifier is stored, individual requests cannot be attributed to you or linked to one another, and the data is only ever analysed in totals. You may object to this processing (section 6).
- Retention: individual requests are combined into daily counts per Link, QR code, entry route and classification after 90 days and then deleted. The daily counts are kept indefinitely.
2.2 Location and sensor data on your device
If you grant location access, your device determines your position and, where available, its orientation. These values are processed on your device to show you on the map and route you. Without your consent to usage data (section 2.3) they leave the device only as far as a feature you use needs them: when you ask for directions from your location, your device sends the starting point to our server, which computes the route with it (for the map service, see section 4.2).
- Purpose: showing your position and routing you.
- Legal basis: Art. 6(1)(a) GDPR — your consent, given through your browser's location prompt.
- Retention: in memory, for the duration of the session only.
Location access is optional. The application remains fully usable without it; you can place a starting point on the map yourself instead. When you share your location live, section 2.11 applies as well.
2.3 Usage data (consent-based)
Only if you agreed in the consent notice do we transmit usage data to us: position and floor, the origins and destinations of routes, search terms, and a random session identifier.
- Purpose: improving wayfinding and how easily destinations are found.
- Legal basis: Art. 6(1)(a) GDPR.
- Retention: 90 days after receipt, then deleted. In operational monitoring (Grafana Cloud) the retention in section 2.1 applies.
The session identifier is regenerated every time the application loads, is held only in memory, and is written to neither a cookie nor local storage. It cannot be used to recognise you across sessions.
2.4 Positioning research measurements (consent-based)
Also only with your consent, we record short sensor traces around a QR-code scan — satellite position with its accuracy, altitude, heading and speed, plus gyroscope and magnetometer readings — covering 30 seconds before the scan and 5 seconds after it.
- Purpose: research into and improvement of indoor positioning.
- Legal basis: Art. 6(1)(a) GDPR.
- Retention: 365 days after receipt, then deleted. In operational monitoring (Grafana Cloud) the retention in section 2.1 applies.
This processing is not necessary to provide you with wayfinding. It serves research, which is why we describe it separately. If you decline, it does not happen at all.
2.5 Feedback
If you send us feedback through the rating feature, we process your star rating and your free text.
- Purpose: handling your feedback.
- Legal basis: Art. 6(1)(a) GDPR.
- Retention: Web3Forms forwards the feedback to us by e-mail. We delete it no later than twelve months after receipt.
Please do not enter health data or other special-category data under Art. 9 GDPR in the free-text field.
2.6 Profile picture
Signed-in users can choose to upload a profile picture. It is stored as a square 256 × 256 pixel JPEG, once per account and independent of any organization. The image is re-encoded before it is stored; metadata of the uploaded file, such as where or with which camera it was taken, is not stored. Members of an organization the person belongs to see the picture. Only the person can replace or remove it; removing it deletes it.
accuras GmbH is the controller, because the picture belongs to your account independently of any organization. The legal basis is Art. 6(1)(a) GDPR: you consent by uploading the picture voluntarily and withdraw by removing it. Retention: until you remove it; on request we delete it together with your account.
2.7 Bookings
Bookings store the Organization, booker and participant identifiers, participant groups, the resource and reserved time, buffers, title, description, Facility note and cancellation reason. A default title may contain the member's display name. Changes remain in event history together with the acting member's identifier. Linked Tasks can copy the title, resource, Booking day and Facility note. Automatic Task comments include Booking changes and cancellation reasons; these Task texts are included in the existing machine translation described in section 4. Members can read their own Booking details; Booking Managers can read the Organization's occupancy plan. Resource calendars expose busy intervals without other members' names, titles or notes. Optional Event publication shares the Booking title, description, time and resource with its selected audience; public publication requires an authorized manager. Facility notes, participants and cancellation reasons are not copied to the Event. Cancellation releases the reservation and retains its history. A confirmed, changed or cancelled Booking is emailed, with a calendar entry, to the booker, the selected participants and the individual members of the selected User Groups, through the email provider listed in section 4. Each message shows only what its recipient may see: the title, description, time, the location if the recipient may see it, the cancellation reason of occurrences that concern them and links to navigate, change or cancel; never the Facility note or Tasks. The Console keeps, per Booking and recipient address, the last invitation sent (including its calendar entry) and a delivery receipt, so that a participant who is removed or whose booking is cancelled can be told. Rendered messages waiting in the delivery queue are deleted seven days after sending; messages that failed permanently remain until an operator removes them. Whoever answers an invitation in their calendar sends the answer to the invitation's sender address. The Console reads that mailbox without changing anything in it and takes from a calendar reply only the answer (accepted, tentative, declined), when it was sent, the invited member, the Booking and, where applicable, the Team through which the member is invited. It does not store the text of a message; other messages in the mailbox are neither changed nor kept. The booker, co-organizers, Booking Managers, Admins and Owners see the answer of every individually invited person and, for a Team, only how many answered each way; an invited member sees only their own answer. When the time of the invitation changes or the member is no longer invited, their answer lapses. The sender of a reply is not authenticated. Incoming replies stay in the mailbox; the Console deletes none of them. For Bookings, the respective Organization is the controller and determines legal basis and retention; accuras GmbH processes them as processor and deletes them on the Organization's instruction or when the contract ends.
2.8 Shared account and sign-in
An accuras account can be used by visitors, Organization members and people invited to edit individual Pages. An invitation grants access; it does not create a separate kind of account. We process your account identifier, name, email address and its verification status, the credentials for your chosen sign-in method, and session and sign-in records. If you use your Organization's identity provider, it authenticates you and supplies the account information needed for sign-in.
accuras GmbH is responsible for providing the shared account. The legal basis for basic account processing is Article 6(1)(b) GDPR, to provide the account service you request. Sign-in and security records protect accounts against misuse under Article 6(1)(f) GDPR, our legitimate interest in secure access. These purposes do not include marketing or consent-based usage analytics.
We keep the shared account until you request its deletion. Losing Organization membership or Page-editing access does not delete it. Sign-in events stored by our identity service expire after 30 days; operational logs follow section 2.1. Session cookies and remembered-device storage are described in section 5. You can request account deletion through the contact details in section 1. Organization-owned records are handled separately as described below; account deletion does not automatically erase Page history or uploaded content.
2.9 Page editing and author history
When you claim permission to edit a Room or Feature Page, the Organization stores your account identifier, name, email and verification status, and the times you claimed, last opened and last saved under that permission. Administrators can review and revoke the permission. The permission record is removed when revoked or when the Page is deleted.
For anyone who saves a Resource Page, including members and invited editors, a separate author directory stores the latest recorded name and email. Page history records the saved changes, the acting account and the time, so administrators can identify and restore earlier versions. Removing editing access does not remove that history or the author directory. These records have no automatic expiry. Images and PDFs uploaded while editing are stored in the Organization's object storage; removing permission does not delete those files.
The Organization is responsible for its Page content, permissions, files and author history and determines the applicable legal basis and retention, including the handling of erasure requests. accuras stores and operates these records on its behalf. Contact the Organization about those records; you can also contact us using section 1. Removing access, deleting an account and requesting erasure of Organization records are distinct actions; the rights in section 6 apply.
2.10 Reports
Where an Organization has switched Reports on, you can report a problem to it from the map, with or without signing in. We store your text, up to three photos, the place the Report concerns, the time and the language of your app. Photos are re-encoded before they are stored; metadata of the uploaded file, such as where it was taken or camera data, is not kept. If you are signed in, your account identifier and name are stored with the Report. Without a sign-in we store nothing about you, and no IP address.
Reports and their photos are visible only to members of the Organization with the Manager, Admin or Owner role. They can create a Task from a Report and take over its text, place and photos, which then belong to the Task. The Report itself then holds only its time, its place and the reference to the Task. A dismissed Report is deleted 30 days after its dismissal and an unreviewed one 90 days after it was received, each with its photos. Managers, Admins and Owners can delete a Report at once at any time.
Please do not photograph people, and do not include health data or other special categories of data under Art. 9 GDPR in the text.
The Organization is the controller for Reports and determines the legal basis; accuras GmbH processes them as its processor. Contact the Organization about them; you can also contact us using section 1. The rights in section 6 apply.
2.11 Sharing your live location
In the accuras app for iPhone, you can share your location live while signed in, for 15 minutes, one hour or eight hours, unless the Organization has switched the feature off. You receive a link and decide yourself whom to give it to. Anyone with the link sees your location on the Organization's map together with your name and, if you have one, your profile picture, until the chosen time runs out or you stop sharing; where the Organization requires sign-in, the viewer signs in first. While you share, the app keeps sending your location to our server, also while it runs in the background; iOS shows this with its location indicator.
For each share we store your account ID, your name from your sign-in, a re-encoded copy of your profile picture of at most 256 × 256 pixels, the expiry time and only your latest location (coordinates, floor, accuracy and heading), which the next one overwrites. We keep no history of your locations, and locations are not logged. When your location lies outside the Organization's area, viewers only see that you are not on the map right now, without coordinates. When you stop sharing or the Organization switches the feature off, the share is deleted at once with its location and picture. When the time runs out, the link shows nothing from that moment and the share is deleted within a minute; if the Organization's application is resting at that moment, this happens as soon as it runs again.
Your location in a clinic can reveal information about your health. Give the link only to people who should see it.
- Purpose: making your location visible to the people you give the link to.
- Recipients: anyone who has the link.
- Legal basis: to be added
- Retention: until you stop sharing, at most until shortly after the chosen time runs out.
The controller is accuras GmbH (section 1, allocation of roles). The rights in section 6 apply.
2.12 Requests to accuras
As a signed-in Member of an Organization, you can write us a request in accuras under "Help and support", in the web app, in Admin mode and in the accuras app. We store your text and our replies, your account ID, your name and your role in the Organization from your sign-in, your e-mail address, and details the app sends by itself: which app and version, browser or device, language, where in the app you were, and up to ten requests to our server that failed shortly before (method, path, status, time). We do not accept attachments. Please do not write health data or details about patients or other persons into your request; we do not need them to answer.
Your request is kept with the Organization in which you wrote it. There only you see it; other Members do not, not even with the role Admin or Owner. At accuras, members of staff read and answer it in an internal application, reached through Cloudflare (section 4).
Our assistant reads new requests, sorts them, looks for the cause in our documentation and source code and proposes replies. For this it uses a language model from Anthropic, which acts on our behalf (section 4). The model receives the request's subject, text and the details sent along, and our replies. We replace e-mail addresses and phone numbers in the text with placeholders first; your name, your e-mail address and your account ID do not go to the model, and the text of your request goes into no web search. Anthropic does not use this data for training and usually deletes it within 30 days; content that breaks Anthropic's usage policy may be kept by Anthropic for up to two years. The assistant decides and sends nothing: every reply is approved or written by a person and sent with their own account.
When we reply, you receive an e-mail with a link to your request. The reply itself is not in it. We use your e-mail address only for this.
- Purpose: handling and answering your request and fixing reported faults.
- Legal basis: Art. 6(1)(f) GDPR. Our legitimate interest is answering questions about using accuras and fixing reported faults, also in the interest of your Organization, which uses accuras. A request is voluntary.
- Retention: We delete a request with all its messages and the details sent along twelve months after its last message, earlier when you ask us to or when your Organization's data is deleted. We delete our assistant's working copies after 30 days. A deleted request stays in backups until the backup expires: a backup taken before a new version of accuras 30 days after a newer one exists, the continuous backup of our databases after a few days.
For requests, accuras GmbH is the controller, even though the request is stored with your Organization. Where we look at your Organization's data to answer, we do so on its behalf. The rights in section 6 apply, including the right to object under Art. 21 GDPR.
3. Consent and withdrawal
We obtain the consents in sections 2.3 and 2.4 through a notice that offers both answers as equals. The application is fully usable if you decline.
You may withdraw consent at any time with effect for the future, using the switch beside the legal links. Withdrawal is as easy as giving consent (Art. 7(3) GDPR). Data not yet transmitted is discarded when you withdraw. The lawfulness of processing carried out before withdrawal is unaffected.
4. Recipients
We use the following service providers. Where they process on our behalf, a contract under Art. 28 GDPR is in place.
The Admin style generation card derives colours from three base colours in the browser without sending them to an AI provider. Saving and applying styles still use our servers. The separate AI style-generation API remains available and uses the providers described below.
| Recipient | Purpose | Data | Location |
|---|---|---|---|
| Cloudflare | connection to our internal application in which members of staff read and answer requests to accuras | a request's subject, status, times and ID, the Organization's name and identifiers, the name and role of the person who wrote it; our assistant's reports, sorting and proposed replies, our members of staff's questions and notes to it with their names, and a preview of the latest of these messages (first line, up to 140 characters); these texts can restate what the request says; IP address and request metadata of our members of staff | United States, EU-U.S. Data Privacy Framework; role: processor; retention: for the transfer only, we store nothing at Cloudflare |
| GitHub | Organization infrastructure provisioning branches and pull requests | Organization slug, infrastructure configuration, branch/PR text and request metadata | United States, EU-U.S. Data Privacy Framework; role: processor; retention: as long as the repository and its history exist |
| IONOS Cloud | hosting, storage, databases, container registry | all stored data; operational registry access metadata | Application hosting and registry in Frankfurt am Main (de-fra); IONOS Object Storage in Berlin (eu-central-3) |
| IONOS Mail | delivering Booking invitations, changes and cancellations with a calendar entry; reading the calendar replies (accepted, tentative, declined) to those invitations; telling a Member that a request to accuras has a reply | recipient email address, the Organization's name as sender name, and the Booking's title, description, cancellation reason, time, place, navigation link and management link; no Facility notes and no Tasks; when reading, the sender address and calendar reply of incoming messages; for the reply notice, the e-mail address and a link to the request, without the reply | Germany; role: processor; retention: sent messages for delivery only, our delivery queue deletes them seven days after sending; incoming replies stay in the mailbox, the Console deletes none of them |
| Mapbox | satellite imagery; in Admin, place search and static map images; computing outdoor routes | IP address, map viewport; for place search the search text; for route computation, from our server: start or destination rounded to about 10 m, gate of the route network or hand-off point of the drive, mode of travel and language, without your IP address or any identifier | United States |
| Grafana Cloud | operational monitoring | log and trace data | United Kingdom (prod-eu-west-2) |
| Web3Forms | delivering feedback | rating and free text | third country |
| YouTube | Videos in Pages and the Greeting view | IP address, browser request metadata and any cookies the browser sends | United States, EU-U.S. Data Privacy Framework |
| Anthropic | floorplan analysis, machine translation of organization content including Tasks, reviewed Decorative Feature generation, Organization Style generation from a Brand Palette, reading requests to accuras and proposing replies | organization floorplans and content text; Task text (title, description, Stop titles and descriptions, checklists) and Task comments members write as free text, including copied Booking notes and automatic Booking change/cancellation notices; selected spatial geometry and labels, floorplan crops, generation prompts, feedback, reference images and model manifests supplied by administrators; Brand Palette, light or dark mode and administrators' free-text colour wishes; when enabled, reusable Material and Wallgroup identifiers, names, colours and opacities; the subject, text and details sent along of requests to accuras and our replies, with e-mail addresses and phone numbers masked, without name, e-mail address and account ID | United States |
The development search experiment briefly reuses probabilities for identical permitted input using opaque fingerprints in server memory. These entries are valid for at most 30 seconds; each search checks current visibility again. Diagnostic logs use random request identifiers and record timings, counts and failure categories, without search text, destination content or account identity.
Event managers can upload images and PDF documents for Event Pages. Selected files are transferred to organization-scoped object storage through short-lived upload links. The server validates the files and serves the processed copies only while the Event and its location remain visible to the reader. Upload progress and unsaved Page edits are kept in memory while the editor is open.
Our application servers are located in Frankfurt am Main. The additional IONOS Object Storage, used for backups among other purposes, is located in Berlin (eu-central-3).
4.1 Transfers to third countries
For transfers to the United States and the United Kingdom we rely on the European Commission's adequacy decision for the United Kingdom; for recipients in the United States certified under the EU-U.S. Data Privacy Framework (Mapbox, Google, GitHub, Grafana Labs, Cloudflare), on that adequacy decision; and for Anthropic and Web3Forms, on the European Commission's standard contractual clauses (Art. 46(2)(c) GDPR) in their data processing agreements.
4.2 Map service
Map engine (technical draft). The map is drawn on your device by our own
map engine. It loads outdoor vector tiles from our own tile server
(tiles.accuras.io), so your device contacts no third party for them. Map
data comes from OpenStreetMap, using the OpenMapTiles schema.
The map does not use Mapbox's map software, and your device contacts Mapbox
only for the following requests. When you switch on satellite imagery, your
device fetches satellite image tiles from Mapbox (api.mapbox.com), which
transmits your IP address and the map area shown. In Admin, searching for a
place by name sends Mapbox the search text and the point the map is looking at,
and the positioning settings show a map image that Mapbox draws of the
Organization's start position or camera view.
Mapbox also computes outdoor routes on our behalf: the part of a route that runs outside the area our route network covers, and, for directions by car or bicycle, the drive or ride to the place to park. For this our server, not your device, sends Mapbox two points: the point outside the route network, that is your start or destination, rounded to about 10 m, and the point where the route reaches the network. That is a gate of the Organization's route network, such as the junction where the lanes of a site meet a public street, or the hand-off point of the drive: the entrance of the place to park or of the building, or, without one, the nearest point on a street. It adds the mode of travel (walking, driving or cycling) and the language. Mapbox receives neither your IP address nor any account, session or device identifier with it. For these requests Mapbox is our processor; section 4.1 applies to the transfer to the United States.
5. Storage on your device
Under § 25 TDDDG (formerly TTDSG) we store information on your device or access it. The entries below are strictly necessary to provide the feature you requested and therefore require no consent (§ 25(2)(2) TDDDG):
| Entry | Type | Purpose | Duration |
|---|---|---|---|
accTrackingConsentChoice | local storage | stores your answer to the consent notice | until you clear it |
accSelectedLanguage | local storage | chosen language | until you clear it |
accMapPosition:* | local storage | map center, zoom, rotation and tilt per organization, including the shared map and style preview in Admin and when switching between admin and visitor | until you clear it |
accAdminFrameFilterTab | local storage | last selected Context or Audience filter tab in Admin mode | until you clear it |
accSelectedFloor:* | local storage | selected floor per organization, including the shared map and style preview in Admin and when switching between admin and visitor | until you clear it |
accColorScheme | local storage | light or dark appearance | until you clear it |
accFloorIndicatorMinimized | local storage | collapsed floor indicator | until you clear it |
accSplashAccent | local storage | splash screen accent colour | until you clear it |
accRafShim | local storage | technical flag for frame rendering | until you clear it |
accMapUseGps | local storage | whether GPS positioning on the map is switched on or off | until you clear it |
accMapSatellite | local storage | whether satellite imagery is shown under the map | until you clear it |
accGpsUserChoiceMade | local storage | records that you chose the GPS setting yourself, so the organization's default does not override it | until you clear it |
accAccessibilityPreference | local storage | whether routes should avoid stairs and other barriers | until you clear it |
accCompassGranted | local storage | records that you allowed compass access on an earlier visit, so the prompt is renewed on the first tap | until you clear it |
accPositioningLastKnown | local storage | last determined position (coordinates, accuracy, time, floor), so it survives a reload | until you clear it; no longer used after six hours |
accLastPosition:* | local storage | your last position per organization (coordinates, floor, source, accuracy, time), restored at start | until you clear it; discarded at the next start after six hours |
accParkedVehicle:* | local storage | where you left your car or bicycle per organization (coordinates and floor where the walk from it started, or the place to park itself, its name, time), so a later trip starts with the walk to it | until you drive or ride off; no longer used after 10 hours and deleted at the next start for that organization |
accLastViewed:* | local storage | recently opened Features and buildings per organization for quick return | until you clear it |
accChecklistProgress:* | local storage | to be added | to be added |
accuras_session_hint | local storage | records that this device had a signed-in session; the session itself is always checked | until you sign out or clear it |
accBasemapStyle:* | local storage | cached basemap style per colour scheme, so it is not downloaded on every start | until you clear it; replaced on the next use after 24 hours |
accuras-assets-v1 | browser Cache Storage | the app's own program files (scripts, stylesheets, fonts) cached so they are not downloaded again; they hold nothing about you, but the files kept show which parts of the app were opened on the device | until you clear it; at most 300 entries, the least recently used are removed first, entries older than 30 days are replaced when next requested |
accuras-basemap-style-v2 | browser Cache Storage | cached basemap style, so it is not downloaded on every start; nothing in it relates to you | until you clear it; at most 10 entries, entries older than 24 hours are replaced when next requested |
accuras-tiles-signed-v1 | browser Cache Storage | map tiles of the public map whose contents can go out of date (all kinds except walls and the concealment of rooms not shown to the public, "audience concealment"), cached so they are not downloaded in full each time; the context, feature and marker tiles contain time-limited signed addresses of icons and models, which are the same for every visitor and are not created for you; nothing tied to your account is stored; the tiles show which map areas were viewed on the device | until you clear it; at most 400 entries, the least recently used are removed first, entries older than 24 hours are replaced when next requested |
accuras-tiles-static-v1 | browser Cache Storage | map tiles of the walls and of the concealment of rooms not shown to the public ("audience concealment") of the public map, cached so they are not downloaded again when the map is opened again; they contain no signed addresses and nothing about you, but they show which map areas were viewed on the device | until you clear it; at most 250 entries, the least recently used are removed first, entries older than 30 days are replaced when next requested |
accuras-classification-v1 | browser Cache Storage | public data of the organization (outlines and names of its Premises, and per Premises building outlines, floors and areas) that the app uses to recognize which building the device is in, also without a connection, for example during a route; the answers are the same for every visitor and nothing in them relates to your account; the entries kept show which Premises were near the device or on a route | until you clear it; at most 200 entries, the least recently used are removed first, entries older than 7 days are replaced when next requested |
workbox-precache-v2-* | browser Cache Storage | the app's start page, cached so the app notices a new version, and its web app description and the decoder scripts for the map's 3D models, cached so they are available without a new download; the same for every visitor, nothing in them relates to you | until you clear it; a fixed set of files that a new version of the app replaces |
accSwRecoveryAttempted | session storage | allows one automatic repair per tab when an app update is stuck | until you close the tab |
accuras_auth_required_redirect | session storage | allows one automatic redirect to sign-in per tab where the organization requires sign-in, so a cancelled sign-in does not loop | until you close the tab |
accuras:chunk-reload-attempted | session storage | allows one automatic reload per tab when an app file the tab needs could not be loaded, for example because a new version removed it | until you close the tab |
accuras.visitor.sessionId | session storage | random identifier per tab, sent with each request to our servers so their technical logs of one session can be grouped | until you close the tab |
accuras_login_org_slug | session storage (sign-in pages) | organization of the sign-in in progress, so the sign-in pages keep its branding across steps | until you close the tab |
helpEnabled | local storage (sign-in and account pages) | whether help texts are shown on the account pages | until you clear it |
pageSize | local storage (sign-in and account pages) | chosen number of rows per page in account page tables | until you clear it |
__Host-accuras_reports_gate | cookie | sign-in session of the development environment's E2E reports page (reports.dev.accuras.io only, never set in production) | 7 days |
__Host-accuras_reports_gate_csrf | cookie | protects that sign-in against forged requests (same page only) | until the sign-in completes |
__Secure-accuras_share | cookie | keeps a share (a presentation or document at share.accuras.io) open after its password was entered, for that share only; holds nothing about you | 12 hours, at most until the share ends |
accuras_locale | cookie | language across the applications | 1 year |
accuras_color_scheme | cookie | appearance across the applications | 1 year |
__Host-accuras_session | cookie | sign-in session (authenticated areas only), restricted to the API host | 7 days |
__Host-accuras_session_csrf | cookie | binds the sign-in callback to this browser, restricted to the API host | until sign-in completes, at most 15 minutes |
Shared Terminal devices
Pairing keeps a shared Terminal connected without signing in its visitors. This device-access storage is strictly necessary (§ 25(2)(2) TDDDG); it contains no visitor identity or activity.
| Key | Storage | Purpose | Retention |
|---|---|---|---|
accuras:terminal-device | local storage | Organization identifier, Terminal code and random device credential; during pairing also the receipt, display code, expiry and separate polling credential | pairing details until approval or observed expiry; device access until observed revocation, replacement, a change of Terminal or clearing browser storage |
Entries in Admin
In Admin, which staff of the deploying organization use, the application stores the following entries in local storage, session storage or the browser's Cache Storage. They too are strictly necessary (§ 25(2)(2) TDDDG). The respective organization is controller here; accuras GmbH is processor.
| Entry | Type | Purpose | Duration |
|---|---|---|---|
accLayerVisibility | local storage | map layers shown in the editor | until you clear it |
accContentLang | local storage | content language the editor works in | until you clear it |
accWalkabilityPriorVisible | local storage | whether the prior heatmap overlay is shown on the editor map | until you clear it |
accWalkabilityPriorOpacity | local storage | opacity of the prior heatmap overlay on the editor map | until you clear it |
accSnapLayerConfig | local storage | map layers that drawing snaps to | until you clear it |
accSnapEnabled | local storage | whether snapping is switched on in the editor | until you clear it |
accSnapDistance | local storage | chosen snapping distance in the editor | until you clear it |
accFloorplanOpacity | local storage | opacity of floorplans on the editor map | until you clear it |
accTempFloorplans:* | local storage | identifiers of temporarily shown floorplans per organization | until you clear it |
accAdminLastPosition:* | local storage | last device position in the editor per organization (coordinates, accuracy, time, floor, source) for the position marker and the Page preview | until you clear it |
roomDetectionJob:* | local storage | running room detection per floorplan, so its progress is shown again after a reload | until the room detection ends while the floorplan is open, otherwise until you clear it |
accuras.bimImports:* | local storage | running BIM model imports per organization, so their progress survives closing the dialog and a reload | until you clear it |
accuras.pendingGroupPlacements:* | local storage | where a BIM floorplan group is placed per organization until its import has produced floors | until you clear it |
accuras.referenceMarker.color | local storage | last colour used for reference markers | until you clear it |
accFeatureCopyConfig | local storage | properties copied when a Feature is duplicated | until you clear it |
accFloorplanListExpanded | local storage | expanded Premises and floorplan groups in the floorplan list (identifiers) | until you clear it |
accuras:last-org-slug | local storage | last opened organization, so Admin opens it directly | until you clear it, switch organization or access is refused |
accuras.audience-filter.* | local storage | chosen Audience filter per organization (identifiers and names of Teams and groups) | until you reset or clear it |
accAdminLastViewed:* | local storage | recently opened Features, materials and contexts per organization for quick return | until you clear it |
accBasemapStyle:* | local storage | cached basemap style per colour scheme | until you clear it; replaced on the next use after 24 hours |
accFavorites | local storage | saved Features, Premises and buildings in Admin | until you clear it |
accuras:admin:preload-reload | session storage | allows one automatic reload per tab when a new version removed an Admin file still needed | until you close the tab |
Favorites
The Visitor app stores saved Feature, Room, Event and exact Event date references in accFavorites:* in local storage, one entry per Organization, on this device. Event references contain the Organization and Event identifiers and, for a saved date, its opaque occurrence identifier. Event titles, Page content and locations are fetched again subject to the current access rules. Saving a reference grants no access. Users can remove individual saved references from Favorites.
Storing them is strictly necessary (§ 25(2)(2) TDDDG) because you create the Favorites explicitly. They stay until you remove them or clear the storage.
6. Your rights
You have the right to
- access the data we process about you (Art. 15 GDPR),
- rectification of inaccurate data (Art. 16 GDPR),
- erasure (Art. 17 GDPR),
- restriction of processing (Art. 18 GDPR),
- data portability (Art. 20 GDPR), and
- object to processing based on legitimate interests (Art. 21 GDPR).
A message to info@accuras.de is enough to exercise them.
Please note that the data described in sections 2.1.1, 2.3 and 2.4 generally does not allow us to identify you: we assign no persistent device identifier, and the session identifier ends when the page reloads. Where we cannot identify you, Art. 11(2) GDPR does not oblige us to collect additional data purely to satisfy an access or erasure request. In that case, please send us details that allow your data to be located.
7. Right to lodge a complaint
Without prejudice to any other remedy, you have the right to lodge a complaint with a supervisory authority, in particular in the Member State of your residence, place of work, or the place of the alleged infringement (Art. 77 GDPR).
The authority competent for us is:
Bayerisches Landesamt für Datenschutzaufsicht (BayLDA)
Promenade 18
91522 Ansbach
Organization-authored Page content
Pages and the Greeting view can display videos, images and links selected by the Organization. A YouTube component loads its embedded player when displayed; image components request their configured image URL. These requests expose the visitor’s IP address and browser request metadata to the respective host. External links and document links open when selected. Google is an independent controller for the data it receives when the player loads and determines its retention itself. Google LLC is certified under the EU-U.S. Data Privacy Framework. The legal basis for loading it is Art. 6(1)(f) GDPR; our legitimate interest is showing the content the Organization chose.
Opening in maps apps
For directions by car or bicycle, “Open in Maps” offers Apple Maps, Google Maps and, by car, Waze. Only when you choose one does the application open that service, as its app or website, with the coordinates of the hand-off point as the destination, that is the place to park or the entrance the drive ends at; the provider then receives these coordinates together with your IP address and browser request metadata. The chosen app is kept only in the directions’ address; nothing is stored on your device for it.
Website www.accuras.io
This notice also covers our website at www.accuras.io. The controller is accuras GmbH (section 1).
Hosting. The website runs on our own servers at IONOS Cloud in Frankfurt am Main, which also run the application. When you open it, we process connection data as described in section 2.1, for the same purpose, on the same legal basis and for the same retention period. The website serves all of its content itself, including its depictions of the apps; it embeds no third-party services.
Marketing films. At media.accuras.io, our own servers in Frankfurt am Main
deliver our marketing films from IONOS storage in Berlin. Section 2.1 also
applies to connection data. The watch page uses your browser's video controls,
without an embedded third-party player, visitor counting, cookies or Local
Storage entries.
Demo and sign-in. Links such as "In der Demo ansehen" open the Visitor app with sample data at demo.app.accuras.io, and "Anmelden" opens the application's sign-in at admin.accuras.io. The sections of this notice about the application apply to both; the website itself transmits nothing for this.
Storage on your device. The website stores nothing on your device: no
cookies, no local storage entries and no Cache Storage. If your browser visited
the earlier version of the website, the website removes that version's Cache
Storage, such as its cached program files (app-code), and the service worker
that created it on your next visit. It does not read entries the earlier
version kept in local storage, such as the chosen language, appearance and use
case; you can delete them in your
browser's settings.
Visit count. When opened, the website sends a request to our own server. It names your browser's preferred language among the website's, the use case whose page you open first or that the link you opened names (hospital, trade fair or university, for any other only "other"), and the website you came from, by its name only without a path (for example linkedin.com). The server classifies the visit as direct or automated from the User-Agent. These details are kept with the record of the request in our operations monitoring (Grafana Cloud), alongside the connection data described in section 2.1, and are evaluated only as totals. Nothing is stored on or read from your device for this, and no identifier is formed that links visits to you or to each other; repeated visits are counted individually, opening another page of the website or returning to a page is not.
- Purpose: measuring the website's reach for our business reporting: how often it is opened, in which language and from which other websites.
- Legal basis: Art. 6(1)(f) GDPR. Our legitimate interest is business reporting on the website's reach. Your interests do not override it, because nothing is stored on your device, no identifier is formed and the details are evaluated only as totals. You can object to the processing (section 6).
- Retention: 14 days in operations monitoring, like the connection data described in section 2.1.
Contact. The website's contact form transmits and stores nothing. It opens your e-mail program with a prepared message to info@accuras.de; we receive your details by e-mail only once you send it.
- Purpose: answering your inquiry.
- Legal basis: Art. 6(1)(b) GDPR where your inquiry aims at a contract, otherwise Art. 6(1)(f) GDPR; our legitimate interest is answering inquiries.
- Retention: until your inquiry is fully handled. We keep commercial correspondence for as long as commercial and tax law require (up to six years, § 257 HGB, § 147 AO).
8. Changes
We update this notice when the processing it describes changes. The version available in the application at the time is the one that applies.
Last updated: 18 November 2026