Telephone: +353 857532402. Email is the main support channel. This is an ordinary contact number, not an emergency or 24/7 support line.
What MarshalUp processes, why it is used and the choices available to you.
Who is responsible
MarshalUp is operated by Ovidiu Dinu, an individual based in Ireland (“I”, “me” or “the operator”). MarshalUp is the service name. Contact Build Forward support about privacy. BuildForward is used in the support-domain name. Neither name identifies a separate legal supplier. Geographic contact address: 206 The Kestrel, The Sanctuary
Mahon
Cork T12D579
Ireland
Your workplace decides how MarshalUp is used at its site, who has access and which operational records to enter. It is responsible for explaining its workplace purposes and legal basis. MarshalUp's operator handles account administration, service security, billing reconciliation and support.
For the described service, your workplace is the controller of the operational records it instructs me to process, and I act as its processor under a separate data-processing agreement. I act as a controller for my own account administration, purchase reconciliation, service security and direct support purposes described below. These responsibilities depend on the actual processing. Your workplace should give you its own privacy information and identify its contact. This notice is information about processing; reading it or using the app does not itself give consent or execute a workplace data-processing agreement.
Information used by the service
- Account and membership: name, email address, account identifier, sign-in method, approval status, role and building/site membership. Firebase Authentication processes the information needed for email/password or Apple sign-in. We do not ask you to send your password to support.
- Workplace agreement records: customer legal name and address, site scope, representative name and role, privacy/security contact, signed-in account/contact, the authority and agreement declarations, document versions and exact copies, offer identifiers/times and server-confirmed acceptance date. Authority is self-declared, not independently verified. The acceptance flow stores an unaccepted document offer when a representative requests review; an offer alone is not an executed agreement.
- Workplace records: site and building details, floors and zones, assembly points, emergency contacts and their telephone numbers, training/certification records, attendance and check-in times, coverage claims and panel assignments.
- Safety activities: check results, notes and follow-up actions, scheduled drills, incident participation/status, observations and completed-event records. Names, identifiers and timestamps may identify the people who performed an action.
- Technical information: notification registration tokens and account bindings, authentication/security information, device-attestation information, request and error logs and timestamps used by Google, Apple and our backend to operate and protect the service. Provider infrastructure may process IP addresses and device/request information. Technical processing and installation identifiers can begin at app launch before sign-in; notification permission does not switch off all Firebase technical processing. Packaged Firebase SDKs also declare diagnostic and installation-related metadata used for service-quality analytics. No Firebase Analytics, Crashlytics, Performance Monitoring or advertising SDK product is linked by the app target reviewed for this version; this does not mean the necessary SDKs collect no diagnostics.
- Purchase information: Apple product and transaction identifiers, subscription status, renewal/expiry information and the site associated with an entitlement. Apple processes the purchase payment details; the app does not collect your payment-card number.
- Communications: support emails and attachments you choose to send, operational email recipients/content, delivery outcomes and provider email-engagement events described below. If you specifically request help with a missing account-verification email, a Firebase-issued verification link may be sent through our existing Brevo transactional service. This does not require you to give support your password.
Account identity and sign-in information are needed to create and secure an account. Without them I cannot provide account access. Your workplace determines which operational records it requires and should explain the consequences of not supplying them. Optional support attachments are not required for an account; avoid sending unnecessary personal information.
Records may be entered by you, your administrator or other authorised team members. When completing a check, you can take or choose a photo and draw a signature where the check asks for this evidence. On saving the check, compressed photo and signature images are stored with its record in Firebase and can be viewed by authorised users with access to that record. A drawn signature is recorded evidence, not independent verification of identity or confirmation that a workplace is safe. Only include relevant evidence and avoid unnecessary images of people or sensitive information. Camera access requires your permission; the photo picker lets you choose the image to attach. Older records may also contain external attachment links; opening those links can involve the external host. The QR scanner uses camera input to read a code; camera frames are processed on the device rather than uploaded by this scanner. This version does not request device Location Services. Selecting a building or recording a zone/status can still indicate where someone is at work.
Do not enter medical histories, personal evacuation plans or other unnecessary sensitive information in free-text notes. Older records may contain absence reasons or other sensitive information. Removing a feature does not erase previously stored information. If special-category data is retained or collected, the workplace and operator must establish the additional lawful conditions and safeguards before use.
Purposes and legal bases
- Your own account and purchase relationship: I use identity, sign-in and entitlement information to provide the service you request and administer a contract with you, where that processing is necessary for that contract (Article 6(1)(b) GDPR). If the customer is your employer or another organisation, its contract alone is not treated as a contract with every employee.
- Access for workplace members: for my separate service-administration purposes, I rely on legitimate interests in giving authorised people secure access to the workplace service (Article 6(1)(f)), subject to necessity and balancing against their rights. Workplace records themselves are processed on the workplace's instructions under its own lawful basis.
- Security, reliable delivery and troubleshooting: I use proportionate technical information, account bindings and delivery/failure records to authenticate users, prevent misuse, reconcile access and investigate failures. The relevant legitimate interests are protecting accounts and operating a reliable service. This is not permission to use workplace content for advertising or unrelated profiling.
- Customer agreement administration: I use the necessary representative/customer details and acceptance record to establish and administer the customer contract, document instructions and deal with disputes or compliance. The contract basis applies only where the individual is a party and the processing is necessary; for an organisation’s representative, the separate legitimate interests are identifying authorised contacts and documenting the agreement, subject to necessity and balancing. Accepting a contract is not consent to unrelated processing.
- Support and rights requests: I use the information needed to answer you, verify identity proportionately, investigate a problem and handle a request. Contract applies where support is necessary to my contract with you; otherwise the relevant interests are answering requests and resolving service issues. Specific data-protection duties apply to rights requests and compliance records.
- Legal obligations: I retain or disclose the minimum information required to meet applicable accounting, tax, data-protection or other legal duties (Article 6(1)(c)). A legal duty must apply to the particular processing; this is not a general justification to retain all workplace records.
Packaged provider SDKs also declare technical diagnostics and service-quality analytics, including processing at app launch. These are service-quality and technical purposes rather than an app advertising feature. Provider processing and optional email engagement are described separately below; not every SDK activity is treated as necessary for your contract.
Your workplace determines its lawful basis for attendance, coverage, checks and incident records and, if necessary, an additional Article 9 condition for special-category data. Employee consent is not assumed. Camera and notification permission are device choices, not blanket consent to processing. No solely automated decision with legal or similarly significant effects is made by this service.
If a record is disputed or inaccurate, contact your workplace administrator or support through the appropriate rights/correction route. Where appropriate, ask for it to be marked as disputed while checked; this notice does not claim the app has a dedicated dispute-status feature. Do not add medical details, speculate about a person’s condition or collect extra sensitive data merely to compensate for uncertain records. Report urgent concerns through workplace emergency procedures; a support or correction request is not an emergency alert.
These accuracy and safety limitations do not remove the workplace’s or the operator’s applicable accuracy, security and other data-protection obligations. This notice does not limit liability, waive a claim, constitute consent to tracking or replace the workplace agreement. Rights and remedies remain governed by applicable law.
Who can receive information
Authorised people at your site can access records according to their roles. Administrators manage access. Information you put in a report, poster or exported file can reach the people with whom you share it. A share/export action is not controlled by the app after the recipient receives the file.
- Google Firebase and Google Cloud: authentication, Firestore storage and synchronisation, server functions, push messaging, app attestation, logs, backup/recovery and email-delivery monitoring. Firebase sends verification and password-reset messages.
- Apple: Sign in with Apple, device attestation, Apple Push Notification service and App Store purchases/subscription events. Apple applies its own terms and privacy information to its platform services.
- Brevo: operational email sending, recipient/message processing, delivery/failure handling and email tracking. This is separate from Firebase authentication mail.
- Support mailbox provider: the support mailbox uses Apple's iCloud email service. Your mail provider also processes messages you send or receive.
The operator remains accountable for its own processing and applicable processor obligations. A provider’s involvement or a workplace administrator’s role does not by itself remove that responsibility or a person’s statutory rights.
Access by the operator or service providers is limited to service, support, security, legal and operational purposes. Information may also be disclosed where lawfully required, or to protect rights and security. We do not operate an advertising business or intentionally sell workplace records. This does not mean no provider collects technical or engagement data.
Operational email and tracking
Brevo-delivered messages may include hidden images that record message loading and rewritten links that record clicks. Depending on the mail client and provider, this can involve recipient/message identifiers, event times, link information and technical request information such as IP/device data. Privacy-proxy loading can create an event without a person reading the message.
The Brevo account is configured to use per-contact tracking consent and not track contacts whose consent is unknown. Brevo describes these controls as limiting individual open/click tracking to contacts with recorded consent. This is not a promise that every tracking image or rewritten link is removed: received test messages retained those elements, and Brevo can still perform aggregate delivery-related or security processing. Anonymous reporting alone is not a promise of tracking-free email.
MarshalUp uses delivery/failure information to monitor operational messages, not individual open/click activity for advertising, engagement scoring or personalised marketing. A load or click is not proof that a notice was read or that deletion may proceed. Any optional recipient-level engagement use must have valid separate consent or an applicable exemption before it is enabled; agreeing to service terms or receiving an operational email is not such consent. Blocking remote images or protecting your mail privacy may reduce image loading but does not ensure link-click tracking is disabled.
Storage, security and international processing
The main Firestore database is configured in the European multi-region eur3. Some functions and provider services operate elsewhere, including the United States. This is not a promise that all data stays in Ireland or the EU. Authentication, messaging, support email, telemetry and subprocessors have their own processing arrangements.
International processing is service-specific. Google publishes its Cloud Data Processing Addendum, Firebase processing terms and transfer provisions; Apple and Brevo publish their own relevant terms and privacy information. Where a transfer needs a Chapter V safeguard, the applicable mechanism must cover that particular service and destination. Contact support for the relevant arrangement and information about obtaining a copy of safeguards, subject to necessary redaction. An EU database region alone does not establish the safeguards for every provider operation.
The service uses authenticated access, role controls, encrypted transport and provider security measures. No system can guarantee perfect availability or security. Firestore can keep a persistent local cache; selected building, assembly-point and emergency-contact details are also stored on the device for offline access. Protect shared devices and downloaded files. Do not assume that deleting an account remotely erases every cache or copy on a device. Protect the device, sign out when appropriate and handle local copies securely.
Retention and deletion
Account and operational records are kept to provide site access, maintain records and deal with support, security and legal requirements. Retention must be limited to those purposes and reviewed when the data is no longer needed. The following periods and criteria distinguish workplace history, closed sites and necessary operational evidence. A commercial closure period is not itself a statutory fire-safety record-keeping period.
The standard workplace instruction is two calendar years of historical workplace records. For checks, the period starts at completion or closure of necessary follow-up; for incidents and drills, it starts when coordination ends or necessary follow-up closes, whichever is later. This includes the recorded linked log, observations and actions. Current site configuration and account access are not erased merely because they were created two years ago. A shorter necessary period, a valid earlier erasure instruction or a specifically justified legal hold can require different handling.
For a site that never became paid, the closure period is 30 calendar days after trial access ends. For a previously paid site, it is six calendar months after paid access ends. Routine final deletion is no earlier than 30 full days after the first verified final-notice delivery observation: the later deadline applies. Cancelling renewal alone does not end paid access or start the closure period. These are manual policy periods while automated cleanup is paused, not a promise that a background job erases records exactly when a timer expires.
Automatic inactive-site retention cleanup is paused. Requests and due cases are reviewed individually under the manual procedure; expiry alone is not confirmation that erasure has completed. User-requested account deletion remains available; background automatic recovery for interrupted account deletions is disabled, so interrupted requests require operator follow-up. Any legacy visitor cleanup is separate from the never-paid trial-site policy.
Successful owner deletion targets the site and its operational records and detaches other members; it does not delete other people's own login accounts. Member deletion targets the member account and associated records. Some shared historical records may still contain names or action references. Subscription-binding records are deliberately retained to prevent receipt reuse; deletion-job, email, provider and security records require separate review and handling. App deletion is not a promise to erase every copy held by a workplace, provider or recipient.
- Workplace records: the workplace determines its record-keeping duties and gives documented retention, return or erasure instructions. If it needs records beyond the agreed service period, it should keep secure independent copies or agree a necessary variation before use. Owners can prepare a workplace records PDF in Settings → Site archive, including after paid site access ends while the records remain available. It covers available checks, findings, drills and incidents, current building and check settings, and recorded attendance, zone assignments and panel duty. It is not a complete journal of every change. Photos, drawn signatures, attachment files and external links are not included in this PDF; keep required supporting evidence separately. Member/contact lists, agreements, billing and technical records are also excluded. Contact support about records you need that are not included. The PDF contains personal information and is not password encrypted: save it securely, reopen it to check its contents, and share it only with authorised people. Annual email and in-app export reminders are planned and are not yet available. Neither downloading an archive nor a customer's record-keeping duty removes the operator's own obligations.
- Account and entitlement information: account details support the account while it is used; deletion is subject to the scope below. Limited transaction/site bindings are retained for entitlement integrity and receipt-reuse prevention. Keep only the identifiers needed while the transaction can still be presented for entitlement restoration or reuse prevention, subject to documented necessity review. This does not authorise keeping a complete deleted profile.
- Agreement offers and evidence: a signing offer expires after 30 minutes, but expiry does not erase the stored offer. Unaccepted offers require necessity review after expiry or supersession; remove them once no pending acceptance, recovery or specifically justified evidence need depends on them. Accepted evidence is held with the site during the contract and agreed exit period; any separate minimal legal-case evidence requires a specific recorded purpose and review, rather than a blanket six-year archive. The existing recursive account/site deletion path removes these copies; no separate indefinite agreement archive is established. Do not assume a full employee profile must be kept to retain minimum contract evidence.
- Support, operational mail and logs: separate records can remain outside the account tree and require a separate lifecycle. The last verified Brevo setting was one month for transactional logs and no stored email previews. This does not establish erasure of older previews or a matching period for the Firestore mail queue, support mailbox or Cloud logs. Review closed support cases for removal when their support, rights or specifically justified evidence purpose ends, and remove unnecessary sensitive attachments sooner. Working exports should be removed after successful handover/verification when they are no longer needed. Mail queue and job evidence remain only while needed for delivery, retries, notice verification or an unresolved case; review them on case closure and weekly while stuck.
Scheduled Firestore backups have a seven-day retention window and point-in-time recovery is enabled with a rolling recovery window. Copies can outlive removal from the live database until they expire. Any restore must reconcile subsequent erasure requests. Local exports and recipient copies have their own retention. Provider-controlled copies and required security logs follow their applicable service controls and lawful retention criteria; the operator must assess them separately during an erasure case rather than claim that deleting a site erases every provider copy.
Your rights and choices
I aim to acknowledge routine requests within three business days (Monday to Friday excluding Irish public holidays). This does not postpone action that is required without undue delay, change a statutory deadline or promise completion within three business days. Request deadlines are recorded from the original receipt where applicable, not from acknowledgement or internal assignment.
Depending on the legal basis and circumstances, you can request access, correction, erasure, restriction, portability or object to processing. Where processing genuinely depends on consent, you can withdraw it without affecting earlier lawful processing. These rights have limits; we will explain any lawful refusal or restriction.
Contact Build Forward support or your workplace administrator. We will route requests according to the relevant controller's responsibilities and verify identity proportionately. Requests are normally addressed within one month under GDPR, with a lawful extension where necessary and notified to you. You can complain to Ireland's Data Protection Commission or your competent supervisory authority.
You can manage camera and notification permissions in iPhone Settings. Declining notifications can prevent app alerts, so use the workplace's established alarm and communication procedures. The product is intended for staffed workplaces and is not designed as a children's service. These pages contain no analytics script, cookies or third-party fonts; the hosting service may still process technical request logs.
Version and changes
Version 1.0, prepared 26 October 2026. Public information revision 1.0.1, prepared 13 November 2026, corrects the descriptions of check evidence and workplace PDF exports. This does not replace an accepted workplace agreement or its receipt. The published page identifies when this notice takes effect. Material changes will be communicated appropriately, and any required consent or agreement obtained before the affected processing. Contact support for the applicable version. A privacy notice provides information; it is not a workplace DPA or consent to optional tracking.