1. Scope and contact
This notice covers visitors to savie.cc and users of SAVIE Crew Connect. The operator and controller for website operation, individual accounts, support, service billing and platform security is Max Nowak, Edi-Finger Straße 4, 1210 Vienna, Austria. Contact: max.nowak@savie.cc. You may use this address for all privacy requests without creating an account.
2. Customer workspaces and independent crew accounts
Customer organisations determine the purposes of processing in their workspaces, including personnel administration, assignments and timesheets. SAVIE processes those workspace records on their documented instructions under the data-processing agreement included in the B2B terms. For independent crew accounts and cross-organisation platform functions, SAVIE determines the purposes of the account service. An organisation remains responsible for its own use of a crew member’s information.
3. Data and sources
We receive information from you when you register, maintain your profile, contact us or use the service. Customer administrators may also create or import crew records, invite users and enter assignment information. Records can include names, contact details, profile information, equipment skills, availability, rates, booking history, communications, timesheets and billing information. Your account also stores the app language you choose (German or English), so that we can show the app and send you emails and notices in that language (Article 6(1)(b) GDPR). If you connect an invitation sent to another address with your existing profile, we record the organisation, both profile identifiers, accepting account, time and categories of workspace records reassigned. Optional portfolio records can include production titles, venues, dates, roles, descriptions, equipment, photos, photo descriptions and your publication choice. A public-profile inquiry includes the sender's name, email address, optional company, message, language, verification and delivery times, and the recipient profile identifier. A crew request includes the sender's name, email address, optional company, the requested trade, city, days and message, language, verification, review and delivery times, and which technicians were alerted and which of them answered. For public profiles we keep daily totals of profile views, appearances in the technician search and on city pages, and delivered inquiries; these totals contain no information about individual visitors, no IP addresses and no search terms. Certificates you choose to show on your public profile are published with their name, issuer, expiry date and, where an organisation verified them, that fact. A reference request includes the name and email address of the person asked, optional company, project, time and personal note entered by the freelancer; a given reference adds the text, name, optional role and company its author entered and the time it was given. If you choose Google sign-in, we receive your verified email address, name and Google's stable account identifier. Technical records include IP addresses, browser information, access and security logs, and account identifiers. Where an organisation supplied your information, you can ask us to identify that source and the relevant controller. For new self-registered freelancer accounts we also keep one account-linked activation record: the registration date, a bounded signup-entry category, German or English registration language, and the first email-verification, useful-profile, publication and sharing-tool timestamps. This record contains no visitor IP, browser fingerprint, profile URL, search terms or message content. Platform reports show aggregate registration-cohort counts. A sharing action does not establish a visit or booking. When a customer books a supplier company (subcontractor), the workspace stores the company's details and its contact person's name, email address and phone number and, for each booking, the names and optional phone numbers of the supplier's people and their working hours per day, as entered by the supplier or the customer. Customer organisations can store their own customers' contact persons in their workspace (name, role, email address and phone number) and free-text notes on a customer, to plan and invoice projects with those customers. SAVIE processes this information on the organisation's documented instructions under the data-processing agreement; the organisation is the controller. Crew do not receive these contact details. A project inquiry may also include requested dates or dates to be agreed, city, role, optional venue, planned local shift times and time zone, equipment and offered budget terms. We store hashes of random verification and retry keys and the last verification-send time to support safe retries and rate-limited resends. Public date searches use only availability the freelancer chose to publish; a private calendar or a day without information is not treated as available. Requested search dates are not added to profile statistics. A customer workspace can ask a freelancer with a public profile to join its crew; we store the workspace, the requesting user, the time, the freelancer's answer and its time. When a technician answers an inquiry in SAVIE, we store the kind of answer (interested, not available, question or offer), the message, an offered amount and unit, and the time, as well as when the technician first opened the inquiry, whether the sender closed it, and a random value from which the sender's status link is derived. If a technician gives an Option (a provisional hold on dates) or confirms a firm booking on an inquiry, we store the held days, the deadline, whether and when the sender asked to book firmly or was asked to confirm, the booking time, and whether the technician wants a reference request after the job and when it was sent.
4. Purposes and legal grounds
We process account and service information to provide the service requested by the contracting individual and take requested pre-contractual steps (Article 6(1)(b) GDPR). When you explicitly connect a workspace invitation to an existing profile, the invitation proves access to the invited address and your authenticated session proves the account; SAVIE reassigns only that organisation's roster and operational references and keeps an audit record to provide, secure and support the requested identity link. A sender asks SAVIE to verify and deliver a public-profile inquiry and consents to that specific processing under Article 6(1)(a); the message is not disclosed to the technician until the sender verifies control of the reply address. A sender likewise asks SAVIE to verify, check and forward a crew request and consents to that processing under Article 6(1)(a). Sending crew request alerts to technicians with a public profile is part of the profile service (Article 6(1)(b)); alerts can be switched off in the settings or through the link in every alert. When a technician answers a crew request, SAVIE passes their name, profile link and email address to the sender at the technician's request (Article 6(1)(b)). Reviewing a sender's first crew request before it is forwarded and keeping profile totals rely on our legitimate interests in preventing misuse and in showing freelancers how their public profile is found (Article 6(1)(f)). Showing a certificate on a public profile relies on your consent (Article 6(1)(a)) and can be withdrawn at any time by switching it off; medical certificates and uploaded documents are never published. A freelancer who asks for a reference provides the contact details of a person they worked for and asks SAVIE to send that person one email with a link (Article 6(1)(b) for the freelancer and Article 6(1)(f) for the person asked, based on the legitimate interest in obtaining a reference from a business contact). Showing a given reference with its author's name, role and company relies on the author's consent (Article 6(1)(a)), which can be withdrawn at any time through the link in the confirmation email or by contacting us. Administration of business contacts, support, security and abuse prevention relies on our legitimate interests in operating a reliable service and communicating with business users (Article 6(1)(f)); this includes representatives who are not themselves the contracting party. Accounting and legally required disclosures rely on Article 6(1)(c). Publishing an optional freelancer profile or portfolio entry relies on your consent under Article 6(1)(a). A profile stays private until you publish it in the account or, if you registered yourself and accepted the notice shown at sign-up, until it has a headline, a city and a trade; portfolio entries stay private until you publish them. Both can be withdrawn in the account. Customer workspace processing follows the customer’s instructions and lawful basis. Required registration information is needed to create and secure an account; without it we cannot provide that account. Optional profile and portfolio fields are not a condition of visiting the website. Passing a workspace's request to join its crew to a freelancer with a public profile is part of the profile service (Article 6(1)(b)); the workspace is added to the freelancer's workspaces only when the freelancer accepts. Answering an inquiry in SAVIE and showing the sender its status are part of the profile service for the technician (Article 6(1)(b)) and part of the inquiry service the sender asked for (Article 6(1)(a)). The same applies to Options, firm bookings and the notices about them. A reference request after a booked job is sent only if the technician chose it when confirming the booking (Article 6(1)(b) for the technician and Article 6(1)(f) for the sender, as for other reference requests).
5. Matching and human decisions
SAVIE compares recorded skills, equipment requirements, availability and relevant booking information to help dispatchers assess candidates. Scores and suggestions support a human decision; SAVIE does not itself decide who is hired. Incorrect profile or availability information can affect suggestions. You can correct your information and ask the organisation responsible for an assignment to review its decision. Crew requests are matched automatically by trade, city (home city or a published availability in that city) and, where a technician publishes a calendar, whether all requested days are shown as busy; private calendar entries are not used. Matching only decides who receives an alert, at most 30 technicians per request. It has no legal or similarly significant effect: the sender and the technician decide themselves whether to work together, and a person checks each sender's first request before it is forwarded.
6. Recipients and service providers
Information is available to authorised users of the relevant workspace and to organisations involved in your assignments as required for those workflows. Technicians alerted about a crew request receive the sender's name, optional company, the request and its message, but not the sender's email address. The sender receives a technician's name, profile link and email address only when that technician answers. A workspace that asks a public freelancer to join its crew sees no contact details and cannot send job requests until the freelancer accepts; it learns whether the request was accepted or declined, and after acceptance it sees the contact details like those of other people in its crew. The sender of an inquiry receives the technician's answers by email and on a status page that only its personal link opens (shown after the email is verified and included in SAVIE's emails); the page does not show whether the technician has read the inquiry. For every answer except "not available", the email lets the sender reply to the technician's email address. Days under an Option or a firm booking appear on the technician's public calendar, if they publish it, as partly busy or busy, never with the sender's name. A given reference is visible to the freelancer and, if they choose to show it and their profile is public, to all visitors of the public profile. Infrastructure and backup providers process data for hosting and recovery; helloly GmbH (Austria) processes recipient addresses and message content for account and service email via mail.savie.cc. Hetzner Online GmbH (Germany) provides the application infrastructure and EU backup services. Google processes authentication and device/network information when the Google sign-in option is loaded or used. Stripe processes payment and subscription information when you use paid services and may act as a separate controller for its own fraud-prevention and regulatory purposes. Professional advisers and public authorities receive information where required for accounting, legal claims or a legal obligation. We do not sell personal data. Contact max.nowak@savie.cc for information about the providers relevant to your account and the customer subprocessor register.
7. Transfers outside the EEA
Primary platform hosting is in the EU. This does not imply that every authentication, payment or communications provider processes all information exclusively in the EEA. International processing by a provider must have an applicable GDPR Chapter V basis, such as an adequacy decision covering the recipient or standard contractual clauses with any necessary supplementary safeguards. You can request information about the recipient, applicable mechanism and a copy of relevant safeguards at max.nowak@savie.cc. Google’s privacy information is available at https://policies.google.com/privacy and Stripe’s at https://stripe.com/privacy.
8. Customer integrations
When an organisation enables an ERP integration, data is exchanged to provide its requested workflow. For the easyjob booking-address workflow, SAVIE sends the crew member’s name and email to the customer’s ERP; this creates a record controlled by that customer. A SAVIE erasure request does not automatically erase independent copies in the customer’s ERP. We will assist with requests within our role; contact the customer for its separate records. Information about linked easyjob records is included in the available export. Other enabled integrations must be assessed against their actual configuration and the customer’s instructions.
9. Retention and deletion
Account and workspace information is retained while needed for the service and the controller’s instructions. Identity-reconciliation records are retained with the related workspace records so the link can be explained and reviewed; the accepting-account reference is removed when that account is erased unless another legal ground requires it. A portfolio entry and its stored photo are removed when you permanently delete the entry; withdrawing publication immediately removes public access while retaining the private entry in your account. An inquiry verification link expires after 30 minutes; unverified inquiry records are deleted after seven days and delivered inquiry records after 180 days. Requests to join a workspace's crew are deleted 180 days after they were answered or lapsed. Answers to an inquiry are deleted together with the inquiry. The same applies to Options and firm bookings; an inquiry with a firm booking is kept until 180 days after the last booked day, so that the booking does not disappear before the job. The same periods apply to crew requests: unconfirmed requests are deleted after seven days, all others, including the record of alerted technicians and their answers, 180 days after the last requested day. Daily profile totals are kept while the profile exists and are deleted with the account. A reference link is valid for 30 days; unanswered or declined reference requests are deleted seven days after the link expires. Given references are kept until the freelancer deletes them, their author withdraws them or the account is erased. Closing an account does not necessarily erase invoices, evidence needed for legal claims or records another controller must retain. Accounting records are generally retained for seven years from the end of the relevant calendar year under Austrian tax law, and longer where an ongoing proceeding requires this. The standard cleanup periods are 90 days for soft-deleted crew records, 365 days for audit logs and seven days after expiry for invitation/reset tokens; erasure requests are assessed separately and may be acted on sooner. Database backups rotate after 14 days and are restricted to recovery purposes. Restored data remains subject to the applicable deletion instructions. Ask us for the retention period or criteria applicable to your particular records. Activation records are deleted 90 days after registration by the periodic cleanup and are removed when the linked account is erased. They are included in your personal-data export. Phone numbers of a supplier's people are deleted 30 days after the last day of the booked work; their names and confirmed working hours remain part of the customer's booking and billing records. A customer can remove a supplier contact person's details at any time. A customer organisation can change or remove the details of its customers' contact persons at any time; otherwise they are deleted with the workspace.
10. Browser storage and external resources
SAVIE uses browser storage for authentication, language choices and necessary interface preferences. Authentication is stored locally in the browser; signing out removes the active login. Where configured, account and invitation pages load Google Identity Services for Google sign-in, which can disclose your IP address and browser information to Google. Public marketing pages offer optional Google Analytics measurement only after you explicitly allow analytics. Before consent, after rejection and on account, invitation, directory and individual profile pages, this public measurement is not loaded. It measures public page views, demo-link clicks and worksheet-download clicks; a click is not a completed inquiry. Google receives device and network information and analytics identifiers. We do not send names, email addresses, account identifiers, invitation tokens or form contents through these events. Pages with query strings or fragments are excluded; search-engine referrers are reduced to an allowed origin and other referrers are omitted. Analytics storage and processing rely on your consent, which can be withdrawn through Analytics preferences on the public website. Your decision and the analytics cookies created by this implementation expire after at most 180 days. The current GA4 property retains event-level data for two months and user-level data for 14 months, with the user period reset by new activity; these settings do not govern most aggregated standard reports. Withdrawal stops future measurement and removes these analytics cookies from this browser; it does not automatically erase data previously received by Google. Google Analytics is provided by Google Ireland Limited and may involve processing outside the EEA as described in section 7. Google privacy information: https://policies.google.com/privacy. Analytics is not used in the signed-in application. Browser controls can remove stored preferences and older cookies. Removing necessary storage may sign you out. Fonts are served locally.
11. Your rights
Subject to the conditions in the GDPR, you can request access, correction, erasure, restriction and portability of your data. You may object to processing based on legitimate interests on grounds relating to your situation; you may object to direct marketing at any time. Where processing relies on consent, you may withdraw it at any time by contacting us; withdrawal does not affect processing lawfully carried out before withdrawal. Contact max.nowak@savie.cc or use the account’s privacy functions. We normally respond within one month; where a lawful extension is necessary, we explain it within that month. We may request proportionate information to verify identity. For customer-controlled records, we assist the responsible organisation with your request.
12. Complaints
You may complain to a supervisory authority, in particular in the country of your habitual residence, place of work or alleged infringement. In Austria, contact the Österreichische Datenschutzbehörde: https://www.dsb.gv.at. You do not have to contact us first in order to exercise this right.
13. Security and updates
Measures include encrypted transport, access controls and security logging. Identity reconciliation requires both a one-time invitation and an authenticated existing account, explicit confirmation, and stops when records are ambiguous. Public-profile inquiries use rate limits and a hashed, single-use verification token; a technician's email address is not included in the public profile or inquiry response. Crew requests use the same protections, and links that answer, unsubscribe from, close or decide on a request only act after a click on the page. Uploaded portfolio photos are decoded, resized and re-encoded to remove embedded metadata before storage. No system can guarantee absolute security. This notice is dated 29 September 2026, version 1.10. Material changes to purposes or processing will be communicated as required before they take effect.