Privacy Policy

Protecting your personal data is particularly important to us. We therefore process your data exclusively on the basis of the applicable statutory provisions (GDPR, TKG 2021). In this privacy notice, we inform you about the most important aspects of data processing in connection with our website.

Controller

The controller responsible for data processing within the meaning of the GDPR is BeeSaver GmbH, Zell-Pfarre 34, 9170 Zell, Austria, email: contact@beesaver.at.

Personal Data

Personal data that you transmit electronically on this website, such as name, email address, postal address, or other personal details, will only be used for the stated purpose, kept securely, and not passed on to third parties. The provider automatically collects and stores information on the web server such as the browser used, operating system, referring page, IP address, time of access, etc. This data cannot be attributed to specific individuals without checking additional data sources, and we do not analyze this data further unless unlawful use of our website is detected.

Form Data and Comments

When website visitors leave comments or form entries, the data entered and their IP addresses are stored. This is done for security purposes in case someone submits unlawful content (insults, left- or right-wing extremist propaganda, hate posts, etc.). In such cases, we have an interest in identifying the author.

Form data (e.g. from contact forms) is collected, processed, and stored for the purpose of making contact. This includes the IP address. If users do not agree with this, we ask them to refrain from using the forms on the website.

Newsletter

If you sign up for our electronic newsletter, you will regularly receive information by email. To send electronic mail, data is automatically collected, stored, and processed. If you no longer wish to receive information, you can unsubscribe at any time via a link in the newsletter.

Privacy Policy for the Use of Mailchimp

We use MailChimp to send our newsletter. MailChimp is a service of The Rocket Science Group, LLC, 512 Means Street, Ste 404 Atlanta, GA 30318. When you register for our newsletter, the data you provide during registration is transmitted to MailChimp and stored there. After registration, you will receive an email from MailChimp to confirm your subscription ("double opt-in"). MailChimp offers extensive analysis options regarding how newsletters are opened and used. These analyses are group-based and are not used by us for individual evaluation. MailChimp also uses the analytics tool Google Analytics and may integrate it into newsletters. Further details on Google Analytics can be found in the section "Web Analytics via Google Analytics." More information about MailChimp and data protection at MailChimp can be found at: http://mailchimp.com/legal/privacy/

Integration of Third-Party Services and Content

It may occur that within this online offering, third-party content is integrated, such as videos from YouTube, map material from Google Maps, RSS feeds, or graphics from other websites. This always requires that the providers of such content (hereinafter referred to as "third-party providers") can see the user's IP address. Without the IP address, they would be unable to send the content to the user's browser. The IP address is therefore necessary for displaying this content. We endeavor to use only content whose providers use the IP address solely for delivering the content. However, we have no control over whether third-party providers store the IP address for statistical purposes. Where this is known to us, we inform users accordingly or anonymize the IP address to the extent technically possible.

Cookies

Cookies are small files that allow this website to store specific, user-related information on the visitor's computer while our website is being visited. Cookies help us determine the frequency of use and the number of users of our website, and to make our services convenient and efficient for you. We use session cookies, which are temporarily stored only for the duration of your use of our website, as well as permanent cookies to retain information about visitors who repeatedly access our website. The purpose of using these cookies is to offer optimal user navigation and to recognize visitors, presenting an attractive website and interesting content upon repeat visits. The content of a permanent cookie is limited to an identification number. Name, IP address, etc. are not stored. No individual profiling of your usage behavior takes place. Our services can also be used without cookies. You can disable the storage of cookies in your browser, restrict it to certain websites, or configure your web browser (Chrome, IE, Firefox, etc.) to notify you whenever a cookie is sent. You can also delete cookies from your PC's hard drive at any time. Please note, however, that in this case you may experience a limited display of the page and restricted user navigation.

You can manage your current cookie settings here:

Use of Web Fonts

This website uses external fonts — Google Fonts. Google Fonts is a service of Google Inc. ("Google"). These web fonts are integrated via a server call (typically a Google server in the USA). This transmits to the server which of our web pages was visited. The IP address of the visitor's browser is also stored by Google. For more information, please refer to Google's privacy notices, available at:

www.google.com/fonts#AboutPlace:about
www.google.com/policies/privacy/

Note: According to Google Inc., no personal data — with the exception of the IP address — is stored or processed for the provision of Google Fonts. Google Fonts is fundamentally decoupled from other Google services.

Privacy Policy for the Use of Google Analytics

This website uses Google Analytics, a web analytics service provided by Google Inc. ("Google"). Google Analytics uses so-called "cookies," text files stored on your computer that enable an analysis of your use of the website. The information generated by the cookie about your use of this website is generally transmitted to and stored on a Google server in the USA. If IP anonymization is activated on this website, your IP address will be shortened by Google within member states of the European Union or in other contracting states of the Agreement on the European Economic Area beforehand. Only in exceptional cases will the full IP address be transmitted to a Google server in the USA and shortened there. On behalf of the operator of this website, Google will use this information to evaluate your use of the website, to compile reports on website activity, and to provide other services related to website and internet usage to the website operator. The IP address transmitted by your browser within the scope of Google Analytics will not be merged with other data held by Google. You can prevent the storage of cookies by adjusting your browser software settings; however, please note that in this case you may not be able to use all features of this website to their full extent. You must first accept the collection by the cookie of data generated relating to your use of the website (including your IP address) and the processing of this data by Google.

For more information on terms of use and data protection, please visit http://www.google.com/analytics/terms/de.html or https://support.google.com/analytics/answer/6004245?hl=de. Please note that on this website, Google Analytics has been extended with the code "gat._anonymizeIp();" to ensure anonymized collection of IP addresses (so-called IP masking).

Social Media Plugin "Shariff Wrapper"

We offer the option to use so-called "social media buttons" on our website. To protect your data, we rely on the "Shariff" solution for implementation. As a result, these buttons are only integrated on our page as static graphics containing a link to the respective provider's website. By clicking on the graphic, you are redirected to the respective provider's website, just as with regular links. Only when the provider's website is accessed does it receive information about you, such as your IP address. If you do not click on the button graphics, no data exchange takes place. Information on the collection and use of your data on social networks can be found in the respective terms of use of the respective providers. More information about the plugin and the Shariff solution can be found here: https://de.wordpress.org/plugins/shariff/

We offer buttons on our website for the following services/companies: Facebook, Instagram

Error Management Tool "Sentry"

We use Sentry for our app, a tool for analyzing errors, stability, and performance. The service provider is Functional Software, Inc. ("Sentry"), 45 Fremont Street, San Francisco, CA 94105, USA. The data is processed in the EU region (Frankfurt data center, Germany). We transmit only sanitized error reports limited to the necessary data, as well as performance data relating to the uploading of voice recordings: upload outcome and duration, file size, recording duration, platform, and network type-not the contents of the recording. To ensure that an upload interrupted when the app closes remains identifiable, the app records the start of the upload on your device and reports such an interruption the next time it starts. Personal content such as IP addresses or email addresses is removed before transmission. A data processing agreement with Standard Contractual Clauses (Art. 46 GDPR) is also in place. The app sends this data only if you have enabled error analysis in the app's privacy settings; the legal basis is your consent (Art. 6(1)(a) GDPR, Section 165(3) TKG 2021), which you can withdraw there at any time. We process error data from our server on the basis of Art. 6(1)(f) GDPR (legitimate interest in the stability and error-free operation of our service). Further information: https://sentry.io/privacy/.

Payment Processing via Stripe

For the processing of payments (app subscriptions and the purchase of beehive scales and their service fees), we use the service Stripe from the American technology company Stripe, Inc., 510 Townsend Street, San Francisco, CA 94103, USA. For customers within the EU, Stripe Payments Europe Ltd., 1 Grand Canal Street Lower, Grand Canal Dock, Dublin, Ireland is responsible.

When you choose Stripe as your payment method, you will be redirected to the Stripe Checkout page, where your payment is processed directly through Stripe. We ourselves do not receive or store complete payment data such as credit card numbers.

What data does Stripe store?

When using Stripe, personal data is transmitted to and stored by Stripe. This includes in particular transaction data such as payment method (credit or debit card), bank sort code, currency, amount, and date of payment. In addition, name, email address, billing address, and for fraud prevention purposes also technical data (e.g. IP address, device information) may be collected. Stripe does not sell this data to independent third parties; disclosure only occurs to internal departments, a limited number of external partners, and to comply with legal requirements.

As part of the payment process, Stripe also sets cookies, including:

CookiePurposeStorage Duration
mDetection of the device used (PC, tablet, smartphone)2 years
__stripe_midStorage of session ID for credit card transactions1 year
__stripe_sidStorage of ID for the payment processEnd of session

How long and where is the data stored?

Personal data is generally stored for the duration of service provision. To fulfill legal and regulatory obligations, Stripe may retain data beyond this period. Since Stripe operates globally, data may also be stored outside the EU, particularly in the USA.

Legal Basis

Data processing is carried out on the basis of Art. 6 para. 1 lit. b GDPR (performance of a contract), as payment processing is necessary for the execution of the purchase or subscription contract. Where your consent is required for the use of Stripe cookies, processing is based on Art. 6 para. 1 lit. a GDPR.

Stripe is an active participant in the EU-US Data Privacy Framework and additionally uses standard contractual clauses pursuant to Art. 46 para. 2 and 3 GDPR to ensure secure data transfers to the USA. Further information can be found at: https://commission.europa.eu/document/fa09cbad-dd7d-4684-ae60-be03fcb0fddf_en

You can delete, disable, or manage Stripe cookies at any time in your browser (see section "Cookies"). For questions about data processing by Stripe, please contact: https://support.stripe.com/contact/email

Further information on data protection at Stripe can be found in the privacy policy at https://stripe.com/at/privacy.

Image Credits

Image credits for externally purchased/integrated images are listed directly in the respective posts or pages.

Revocation, Changes, Corrections, and Updates

Users have the right to request free information about the personal data stored about them. In addition, users have the right to correction of inaccurate data, blocking, and deletion of their personal data, insofar as no statutory retention obligation conflicts with this.

Disclaimer

This disclaimer is to be considered part of the internet offering from which this website was referenced. Should any parts or individual formulations of this text fail to comply, no longer comply, or not fully comply with current legal requirements, the remaining parts of the document shall remain unaffected in their content and validity.

Liability for Content on This Website

The content of our pages has been created with the greatest care. However, we cannot guarantee the accuracy, completeness, or currency of the content. As a service provider, we are responsible for our own content on these pages under general law. We are not, however, obligated to monitor transmitted or stored third-party information or to investigate circumstances that indicate unlawful activity. Obligations to remove or block the use of information under general law remain unaffected. Liability in this regard is only possible from the point at which we become aware of a specific legal violation. Upon becoming aware of such violations, we will remove the relevant content immediately.

Liability for Links to Third-Party Websites

Our website contains links to external websites. We have no influence over the content of these external websites and therefore cannot provide any guarantee regarding that third-party content. The respective provider or operator of the linked pages is always responsible for their content. Linked pages were checked for possible legal violations at the time of linking, and no unlawful content was apparent at that time. However, ongoing monitoring of linked pages is not reasonable without concrete indications of a legal violation. Upon becoming aware of legal violations, we will remove such links immediately.

Copyright

The operators of this website endeavor to respect the copyrights of others and to use self-created or license-free works. The content and works created by the site operators on this website are subject to copyright law. Third-party contributions are identified as such. Reproduction, editing, distribution, and any kind of use beyond the limits of copyright law require the written consent of the respective author or creator. Downloads and copies of this site are permitted only for private, non-commercial use.

The layout of this website, the graphics used, and texts and images are protected by copyright. The copyright for published self-created images, graphics, etc. remains solely with the respective author. These elements may not be reproduced, transmitted, made available, performed, presented, translated, edited, or processed without express written consent.

Hosting and Server Operation (Hetzner)

Our app, its associated application programming interface (API), and data storage are hosted by Hetzner Online GmbH, Industriestr. 25, 91710 Gunzenhausen, Germany. All server and object storage resources are located exclusively in the Nuremberg data center (Germany), and thus within the EU or EEA. A data processing agreement under Art. 28 GDPR is in place with Hetzner. The legal basis is Art. 6(1)(b) GDPR (performance of a contract).

Operation of This Website (World4You)

This website and the sending of emails from the contact form are hosted by World4You Internet Services GmbH, Hafenstraße 47-51, 4020 Linz, Austria. Processing takes place in Austria (Linz and Vienna), and thus within the EU or EEA. A data processing agreement under Art. 28 GDPR is in place. The legal basis is Art. 6(1)(f) GDPR (legitimate interest in the secure and stable operation of the website).

Sending Service Emails (Mailjet)

To send service- and contract-related emails (e.g., registration and notification emails from the app) and as the delivery route for emails we write to you from contact@beesaver.at, we use Mailjet, a service of the Sinch Group (Mailjet SAS, Paris, France). Mailjet processes the data in the EU (data centers in Frankfurt, Germany, and Saint-Ghislain, Belgium). A data processing agreement under Art. 28 GDPR is in place with Mailjet. The legal basis is Art. 6(1)(b) GDPR; for our other correspondence, Art. 6(1)(f) GDPR (legitimate interest in answering and handling inquiries).

Mailjet notifies us when an email could not be delivered or was reported as spam. If an address is permanently undeliverable or an email was reported as spam, we switch off the sending of product news by email for app users; you can switch it back on in the app under "Einstellungen" (Settings) > "Profil" (Profile) > "Bearbeiten" (Edit). Alerts and other service notifications are unaffected. We display undelivered emails and spam reports internally in Slack (see "Internal Operational Notices (Slack)"), only with a shortened address (first character and domain). The legal basis is Art. 6(1)(f) GDPR (legitimate interest in learning that an email did not arrive and in no longer sending emails to undeliverable addresses).

Internal Operational Notices (Slack)

For internal notices from our server to management, we use Slack, a service of Slack Technologies Limited, Dublin, Ireland (Salesforce Group). Operational events are reported: alerts from the hive scales (event with apiary and hive name), configuration changes to the scales, logins to the administration area (with IP address), changes to and expiry of subscriptions (with user name), uploaded diagnostic logs (with user name or IP address), ratings of the voice assistant (without their content), and undelivered emails and spam reports (shortened address, user identifier, and error details from Mailjet). We do not transmit notes, recordings, or other content of your beekeeping records. Slack stores the data in the USA. The transfer is based on the EU-US Data Privacy Framework, in which Slack participates through Salesforce, and on standard contractual clauses (Art. 46 GDPR) in the data processing agreement under Art. 28 GDPR. The notices are deleted after 90 days. The legal basis is Art. 6(1)(f) GDPR (legitimate interest in the secure and trouble-free operation of our service). Further information: https://slack.com/trust/privacy/privacy-policy.

Reminders and Calendar Subscription

You can create reminders for future beekeeping activities. We store the reminder text, the due date with optional time and time zone, the optionally selected hives, and the reference to an originating activity, as well as the times of creation, modification, notification, and completion. Apiaries are derived from the selected hives; a reminder is also possible without any assignment. We also store your notification channel, the time of the one-time calendar offer, and, if the calendar feed is enabled, its secret access token. The legal basis for processing your own data is Art. 6(1)(b) GDPR (performance of a contract). For information about other people, the limits and rights under "Information for People Mentioned in Beekeeping Records"; sensitive personal information about other people must not be entered.

The calendar feed is switched off by default. In your profile you can enable it and subscribe to the secret calendar address in a calendar service of your choice. That service retrieves the open reminders; what is transmitted is the text, the due date and, where applicable, the time zone, apiary/hive names, event and change identifiers, and a link back to the reminder in BeeSaver. For this purpose the calendar service also receives the secret feed URL. It does not process the data on our behalf. The place of processing and any further storage depend on the service you choose and its privacy terms; we cannot promise exclusive processing within the EEA for this.

Anyone who knows the complete feed URL can read all your open reminders without any further login. You should therefore pass this address on only to the calendar service you want. You can renew it in your profile or revoke the calendar feed; the previous address then allows no further retrievals. Deleting your account also ends access. Calendar copies already retrieved remain with the provider after renewal, revocation, or account deletion and are not deleted retroactively by BeeSaver. Additionally remove the subscription and any stored content in your calendar service. Changes, completions, and deletions only become visible in a still-active subscription on the next retrieval; your calendar service determines when that retrieval takes place.

Your account data export includes your reminders and settings, but not the secret feed token or the feed URL derived from it.

Push Notifications (Firebase Cloud Messaging)

To deliver push notifications to the app, we use Firebase Cloud Messaging from Google Ireland Limited (Gordon House, Barrow Street, Dublin 4, Ireland) or Google LLC (USA). This involves processing a device token and the notification content; processing may also take place outside the EU, particularly in the United States. Google is certified under the EU-US Data Privacy Framework and additionally uses Standard Contractual Clauses (Art. 46 GDPR). Device tokens that are no longer used are automatically deleted after 270 days.

Service notifications, such as alerts about your beehives, due reminders, or the result of a voice recording you initiated, are part of the service you requested. The legal basis for processing your own data is Art. 6(1)(b) GDPR (performance of a contract); storing and reading the push registration on your device is strictly necessary for this service that you expressly requested (Section 165(3) TKG 2021). Consent is not required for this. For information about mentioned third parties, the limits stated above apply. You control these notifications through your device's notification permission and in the app under "Einstellungen" (Settings) > "Profil" (Profile) > "Bearbeiten" (Edit), where you can choose between push, email, and "aus" (off) for each notification type. For reminders there is a separate setting, with push as the default. If push is selected but no device is registered, the message is sent through our email service Mailjet; selecting "aus" (off) prevents it from being sent. Reminder notifications are also stored, with their content and a link back, in your notification list. Deleting the reminder does not automatically remove this content.

Promotional messages (e.g., product updates) are separate from these. They are based on your consent or on the requirements for permissible direct marketing (Art. 6(1)(a) GDPR, Section 174 TKG 2021) and can be unsubscribed from in the app independently of service notifications.

Voice Assistant (Mistral AI SAS)

In the app, you can record activities and changes at your apiaries and ask spoken or typed questions about your own data. A recording starts when you expressly instruct it to start in the app or through the iOS and Android system controls described below, insofar as they are provided on your device. BeeSaver does not operate its own continuous wake-word detection outside an active recording. Voice recordings are transmitted to Mistral AI SAS, 15 rue des Halles, 75001 Paris, France, for speech recognition. To generate proposed changes or text responses, we transmit the request text and a limited extract of your existing records. For follow-up questions, the stored conversation history, including previous responses, is also transmitted again. A proposed change is displayed to you and applied to your existing records only after your express confirmation; a text-only response does not change those records.

Recording While the Screen Is Locked on iOS and Android

These additional controls apply insofar as they are provided on your particular device; they are not available in the browser. BeeSaver starts recording only after your instruction to start and does not operate its own continuous wake-word detection beforehand.

iOS: Starting Through Siri

On supported iPhones running iOS 18 or later, Siri, Shortcuts, or system controls can trigger the instruction to start, for example, "Hey Siri, starte BeeSaver Assistent" (Hey Siri, start BeeSaver Assistant). Apple recognizes and processes the Siri instruction according to your device settings and the Siri privacy notice; this is distinct from the subsequent BeeSaver recording. We do not promise exclusively local processing for Siri.

Once started, BeeSaver can continue recording while the screen is locked and in the background. A Live Activity shows the ongoing recording and a stop button. Start and stop tones may provide additional feedback. The recording ends through the stop button or an available stop shortcut, through a detected stop word, or automatically, for example, when the maximum duration is reached, storage is low, or an audio interruption lasts for an extended period. Silence does not stop the recording. Therefore, check whether the recording has actually stopped, and do not rely solely on a spoken stop command.

To detect a stop command such as "Aufnahme Ende" (end recording), the audio signal is analyzed during the ongoing recording using Apple's on-device speech recognition. This requires the corresponding permission and an available local language model; a model may first be downloaded from Apple. There is no fallback to server-side speech recognition for this stop-word detection. If it is unavailable or does not recognize the command, the recording continues until another reason for stopping occurs. The stop command may remain in the recorded file.

Android: Starting Through Quick Settings

The "BeeSaver Assistent" (BeeSaver Assistant) tile in Quick Settings starts a recording; tapping it again stops it. Depending on the Android version, unlocking first may be required. No dedicated start function through Gemini has been set up. A microphone foreground service records even while the screen is locked and subsequently transfers the recording in the background. Its notification shows the recording time and a stop button. Starting with Android 16, the system may highlight it as a Live Update; otherwise, the normal notification remains. Swiping it away stops neither the recording nor the upload.

Starting with Android 13, the ongoing audio signal is additionally passed to the on-device speech recognition service to detect "Aufnahme Ende" (end recording). If the system service for local recognition is available, BeeSaver uses its on-device recognition. If the device does not specify such a service, stop-word detection remains off; BeeSaver does not connect another recognition service. Language models may require a download. Unavailable or faulty recognition does not stop the recording; use the stop button in that case. Here too, the stop command may remain in the audio.

Stopping, Automatic Sending, and Local Storage on Both Platforms

Silence does not stop the recording. When it ends, a usable lock-screen recording is automatically uploaded to BeeSaver for processing; no additional confirmation to send is provided. This also applies when it stops automatically, for example, after the maximum duration specified by the server (normally three hours), when storage is low, or in the event of an audio malfunction or interruption. Recordings shorter than one second are discarded. Check whether a recording has actually stopped instead of relying solely on the stop word. The upload may take place in the background and may be retried later if there is no connection. The recording is transmitted along with association and operational data, such as recording time, duration, language, device/recording type, and, on Android, the way the recording was started, the reason it ended, the availability of stop-word detection, and the number of potential stop words detected. The processing by Mistral described above then applies. This does not replace the separate confirmation required before a generated proposed change modifies your existing records.

For this process, the app stores the recording and association data in private app storage; iOS also temporarily keeps an upload file. Upload credentials are stored in the iOS Keychain or, on Android, encrypted with a key in the Android Keystore. When you log out, the app removes this native copy of the credentials; transfers already requested are not automatically recalled as a result. The information under "Retention Period" applies to local files; they must be distinguished from our server-side copies.

Processing at BeeSaver and Mistral

Depending on the request, the extract includes names and descriptions of your apiaries and hives, location details where applicable, queen markings, year and number, and the color and age derived from them; historical activities with date and type, notes, quantities and units, harvest batch, treatment products and dosage, as well as inspection data and changes in the number of frames; weight and weight changes, time since last contact, battery, diagnostics and events, as well as weight, temperature, and sound-level time series. Sound levels are not audio recordings. Historical activity queries may also include archived hives and apiaries. Read access is limited to your own data and tool-specific limits; nevertheless, notes may contain information about other people or sensitive content.

Only Mistral's EU endpoint is used; processing takes place in the EEA (subprocessors in Sweden, Norway, and the rest of the EEA). A data processing agreement under Art. 28 GDPR is in place with Mistral. The use of your data to train AI models is contractually excluded and technically prevented through a corresponding account setting. No speaker identification takes place: we do not create voice profiles or compare voices with one another; processing serves only to handle the spoken content.

Insofar as the processing concerns you as our contracting party, the legal basis for carrying out your spoken or typed request-recording and transcribing where applicable, creating a proposal and applying it after your confirmation, or answering your question through limited read access and a text response-is Art. 6(1)(b) GDPR (performance of a contract). This includes stored responses and their use in the conversation history for follow-up questions. Personal information about other people is subject to the separate purposes, legal basis, and rights in the section "Information for People Mentioned in Beekeeping Records". Your contract with us is not a legal basis for every piece of information about another person. Inform the people mentioned in accordance with the supplementary beta agreement before their information is processed with the voice assistant; sensitive personal information about other people must not be entered.

The stateless endpoints used for transcription and chat completions operate with Zero Data Retention (ZDR): the provider does not store or log inputs and outputs for longer than required to generate the output. This is distinct from the exclusion of training and from the storage of your session data, including text responses, at BeeSaver.

In addition, we retain the voice recording, technical recognition data, and transcripts corrected by you for a limited period and analyze them to improve recognition of beekeeping terminology and dialect forms. The legal basis for this is our legitimate interest in the quality of this function (Art. 6(1)(f) GDPR): recognition errors lead to incorrect entries about your beehives, so the improvement is also in your interest. You can object to this retention at any time (Art. 21 GDPR) -in the app under "Einstellungen" (Settings) > "Sprachassistent: Datenschutz" (Voice Assistant: Privacy), separately for voice recordings and for the analytical data derived from them. An objection takes effect immediately, deletes existing recordings, and does not restrict use of the voice assistant.

Please note that a recording may contain the voices of people present who are unaware of it. Please do not record in such situations, and stop any recording already in progress. This applies especially to longer recordings and when the screen is locked. We do not attribute incidentally recorded voices to anyone or search recordings for people; server-side recordings are deleted in accordance with the periods specified below.

The voice assistant is an artificial intelligence system: recognition, proposals, and text responses are generated by machine and may be incorrect, incomplete, or outdated. Check responses against your source data before relying on them. Confirmation safeguards only the application of proposed changes, not the accuracy of a response. We do not generate artificial speech output or analyze your voice to determine emotional states or personal characteristics.

In addition, a copy of the recording may remain on your device , for example, for later playback or export. Transmission for processing and the local file that remains afterward must be distinguished. We have no remote access to files remaining separately on your device. An objection to our retention deletes our copy, not automatically the one on your device. For details, see "Retention Period."

You can also rate a completed session or an individual proposed change directly-with a thumbs-up or thumbs-down, an indication of what was wrong, and an optional short comment. By submitting the rating, you consentto our storing and analyzing it together with this session to improve the assistant (Art. 6(1)(a) GDPR). The consent statement appears in the rating dialog opened by either thumb-directly above the "Bewertung senden" (Send Rating) button; it is sent only when you tap "Bewertung senden." You can withdraw your consent at any time by deleting the session-the rating is deleted along with it. The rating is not tied to an objection: it is a separate consent, not a consequence of retention.

If you have objected to the retention of your recordings and your device still has a session's recording, when submitting a "falsch verstanden" (misunderstood) rating you can additionally consent to sending this one specific recording to us again, so that the recognition error can be investigated. This consent is also voluntary, is given only for this one clip (the box is not checked), and can be withdrawn at any time-by deleting the session, through the regular deletion period, or by deleting your account. No new speech recognition takes place; the recording is retained exclusively for error analysis in secure EU storage.

Information for People Mentioned in Beekeeping Records

This notice is intended for you if another person records information about you in BeeSaver or processes it with our voice assistant. You do not need a BeeSaver account or a contract with us for this. This notice is not a request for consent.

Who is responsible and where the information comes from: The controller responsible for the processing by BeeSaver described here is BeeSaver GmbH, Zell-Pfarre 34, 9170 Zell, Austria, contact@beesaver.at. The information comes from a user's entries and beekeeping records, not directly from you. If a user provides you with this notice, they should make clear that it concerns their records. You can contact us with questions about the specific source.

What information and for what purpose: This may include your name or another designation, as well as information about your involvement, observations, or statements in connection with a beekeeping activity, including the date and the associated apiary or hive. We store the records and enable the user to retrieve and understand them in their beekeeping context. At the user's request, the voice assistant can read relevant notes or descriptions, search for names appearing in them, and generate responses from them. Older records relating to archived hives may also be included. Responses may contain information about you and may be processed again for follow-up questions. They are generated by machine and may be inaccurate. Personnel administration, evaluation of individuals, or automated decision-making about you with legal or similarly significant effects is not the purpose of this function.

Legal basis: We process ordinary personal information on the basis of Art. 6(1)(f) GDPR insofar as this is necessary for our legitimate interest and the user's legitimate interest in understandable beekeeping records and answers to the user's questions about them, and your interests and fundamental rights do not override those interests. The contract with the user does not constitute consent from you. Sensitive personal information about people, for example, relating to health, religion, or sex life, is not intended for this function and must not be entered by the user. Such content does not become permissible merely because of this notice.

Recipients and place of processing: The records and stored responses are stored with our processor, Hetzner Online GmbH, in Germany. To generate responses by machine, we transmit the request text, relevant limited data extracts, and, where applicable, the previous conversation history to our processor, Mistral AI SAS, France. The search itself runs in our database; Mistral receives the selected results, not the entire notes archive as a whole. This data flow is processed in the EEA. Mistral may not use the data for model training and does not store inputs and outputs of the stateless endpoints used beyond the generation of the output. Storage at BeeSaver is independent of this. The results are available to the respective user. If a reminder contains information about you, it may also reach Firebase Cloud Messaging or Mailjet in the notification content and, in the case of a calendar subscription set up by the user, that user's calendar service. The places of processing and limits in the sections "Push Notifications", "Sending Service Emails", and "Reminders and Calendar Subscription" apply to this; the calendar service is not a processor of BeeSaver.

Retention period: The underlying records remain stored until they are deleted, at the latest until the user account is deleted. Questions and responses remain stored until the session is deleted, at the latest until the account is deleted. Changing the original note does not automatically change a response that has already been stored. Read results are not separately stored on a permanent basis; content incorporated into responses is retained with those responses. Database backups expire according to schedule, after approximately three months at the latest. Rights to any necessary earlier rectification or erasure remain unaffected.

Your rights and contact: You can contact contact@beesaver.at without logging in and, subject to the statutory requirements, request access, rectification, erasure, or restriction of processing. You may object, on grounds relating to your particular situation, to processing based on Art. 6(1)(f) GDPR (Art. 21 GDPR). We will then stop processing the information concerned unless we can demonstrate compelling legitimate grounds that override your interests, rights, and freedoms, or need the information for the establishment, exercise, or defense of legal claims. If possible, identify the user or activity so that we can locate the information; we do not disclose other people's accounts without verification. Independently of this, you can lodge a complaint with a data protection supervisory authority, in particular the Austrian Data Protection Authority, Barichgasse 40-42, 1030 Vienna, www.dsb.gv.at.

Cellular Connectivity for Beehive Scales (EMnify)

The beehive scales transmit their measurements over a cellular connection. The necessary SIM and connectivity management is provided by EMnify GmbH, Würzburg, Germany. This generates connection and usage data (including SIM identifiers, IP address, connection and session logs, and data volume). This connection data is processed within the EU or EEA and-when arranging roaming-in Switzerland, for which the European Commission has issued an adequacy decision. A data processing agreement under Art. 28 GDPR is in place. The legal basis is Art. 6(1)(b) GDPR.

Map Display and Place Search in the App (Google Maps Platform)

In the app, we use Google Maps Platform from Google Ireland Limited or Google LLC to display maps, search for addresses and places, and perform geocoding. Your IP address, entered search terms, and location data are transmitted to Google and may also be processed in the United States. Google is certified under the EU-US Data Privacy Framework and uses Standard Contractual Clauses. The legal basis is Art. 6(1)(b) GDPR or your consent.

Protection Against Spam and Abuse (Google reCAPTCHA)

To protect our forms against automated abuse, we use Google reCAPTCHA (version 3 with version 2 as a fallback) from Google Ireland Limited or Google LLC. For this purpose, reCAPTCHA analyzes various characteristics (including IP address, time spent on the site, and interaction behavior). Data may be transmitted to the United States; Google is certified under the EU-US Data Privacy Framework and uses Standard Contractual Clauses. The legal basis is Art. 6(1)(f) GDPR (legitimate interest in preventing spam and abuse). Further information: https://policies.google.com/privacy

Storage Duration

We store personal data only for as long as necessary for the respective purposes or as required by statutory retention obligations:

  • Account, usage, beehive, and scale data: for the duration of the user account; it is deleted after the account is deleted.
  • Reminders: until individually deleted, at the latest until the account is deleted; no separate expiry date. Marking a reminder as done does not delete it and does not create an activity. Even when an assigned hive, apiary, or originating activity is deleted, the reminder remains; only the respective assignment is removed.
  • Calendar and notification settings and account-related notification entries: for the duration of the user account. Renewing or revoking the calendar feed invalidates the previous feed token. This does not apply to calendar copies already retrieved at the provider; see "Reminders and Calendar Subscription".
  • Device tokens for push notifications: automatic deletion after 270 days of nonuse.
  • Internal operational notices in Slack: 90 days.
  • Voice assistant voice recordings: see "Voice Recordings and Transcripts" below.
  • Invoice- and payment-related data: in accordance with statutory retention periods (generally seven years in Austria).
  • Backup copies: After an account is deleted, data may remain in encrypted backup copies until they expire according to schedule-after approximately three months at the latest. If a backup is restored, deletions made in the meantime are reapplied. Voice recordings are not included in backup copies.

Voice Recordings and Transcripts

If the voice assistant is used, separate periods apply to the data generated in the process:

  • The voice recording is retained after transcription until the last day of the following month and then automatically deleted-depending on when the recording was made, this is four to eight weeks. If you have objected to retention, it is deleted immediately after transcription.
  • An objection (Art. 21 GDPR), deletion of the session in the app, or deletion of your account deletes existing recordings immediately, without a waiting period. Exception: a recording that you expressly attached to a rating (consent, see above) remains until the regular deadline-an objection does not delete a recording retained with consent; deletion of the session or account does.
  • Voice recordings are not included in backup copies. Deletion is therefore permanent and cannot be undone by restoring a backup.
  • Transcripts, typed questions, and text responses remain stored until you delete the session in the app, at the latest until your account is deleted. Deleting a session removes these messages, proposals, and recordings from active data storage. Source activities, apiaries, and hives that have been read, as well as entries adopted from them, remain as part of your other data and follow the deletion periods applicable to that data.
  • Read results used to generate responses are processed only temporarily in memory and are not stored separately. Insofar as a response incorporates content from them, it is retained with the response. Responses are included in normal database backups; deleting a session does not remove them from those backups immediately. Backup copies expire according to schedule, after approximately three months at the latest.
  • Derived analytical data (transcript pairs corrected by you, error metrics, technical recognition data) contains no voice recording and is retained in de-identified form for longer, for as long as necessary for quality analysis.
  • We log every read access to a retained voice recording.

These must be distinguished from local copies on your device. Copies managed in the app's normal recording area are used for playback and export. They are located in app storage, excluded from device backups (iCloud, Android backup), and not removed by our server-side deletion periods or by an objection. For these managed copies, you can select 30, 90, or 365 days (default), or unlimited, in the voice assistant's privacy settings; they are deleted after the selected period. There you can delete the managed recordings together, or individually in the conversation history. Deleting a session also removes the local recording associated with it there.

Lock-screen recordings on iOS and Android: When you open or return to the app, completed recordings are transferred to the managed recording area under the associated account. Those already sent are associated with the session; those not yet successfully sent are queued in the outbox for another attempt. Native source files are cleaned up only after successful transfer into the managed area is ensured; the deletion functions and periods described above then apply to the managed copy. Other accounts do not take over these files. An upload still in progress is not initially sent again; after two hours without completion, the app may take over a retry.

Files remaining separately on the device: Lock-screen recordings not yet transferred into the managed area or left incomplete by an interruption, together with their metadata, may remain in the native recording folder. Recording folders are excluded from device backups. iOS removes its additional upload file when the background transfer is completed; the recording itself is cleaned up only when it is transferred into the managed area by the app. No automatic deletion period is configured for residual files that have not been transferred into the managed area. You can remove local app data through device settings; completely deleting the app from the device also removes the recording files stored there -this does not mean merely offloading the iOS app. Logging out, server-side deletion of a session or account, and an objection to our retention do not automatically delete these separately remaining files. Device storage does not extend any server-side retention period.

Data Storage by Beehive Scales and App

The data collected from the beehives is available to the user, the BeeSaver team, and the processors listed above that are used for the respective service. It is stored for evaluation and analysis and disclosed to third parties in anonymized form only for research purposes. This statement concerning research does not constitute permission for secondary evaluation or training using responses or read results from the voice assistant. Users also have the option of sharing parts of their data with others.

Registration for BeeSaver Services (Beehive Scales and App)

On our websites, we offer users the opportunity to register by entering personal data in an input form. The data is transmitted to us and stored; the processors listed above are used for the respective services. If you wish to delete your account, go to "Einstellungen" (Settings) > "Profil" (Profile) > "Bearbeiten" (Edit) in the app and select "Löschen" (Delete), or contact us at contact@beesaver.at.

Competitions

The information collected for competitions is used only for the selection of winners. In addition, participants agree by participating that the names of the winners may be published.

Your Rights

With regard to your data stored by us, you generally have the rights of access, rectification, erasure, restriction, data portability, withdrawal of consent, and objection. If you believe that the processing of your data violates data protection law or that your data protection rights have otherwise been infringed in any way, you can contact us at contact@beesaver.at. Independently of this, you have the right to lodge a complaint with the competent supervisory authority. In Austria, this is the Austrian Data Protection Authority (Barichgasse 40-42, 1030 Vienna, dsb@dsb.gv.at, www.dsb.gv.at).

The following also applies to the voice assistant: You can object at any time and independently to the retention of your voice recordings and to the analysis of data derived from them for improvement purposes (Art. 21 GDPR)-in the app under "Einstellungen" (Settings) > "Sprachassistent: Datenschutz" (Voice Assistant: Privacy). The objection takes effect immediately, requires no justification, and does not affect use of the voice assistant. These switches do not concern the answering of your questions, the read access required for that purpose, or the stored text responses. You remove the latter by deleting the session or your account; you remove the copy of a recording on your own device through device settings.

Access under Art. 15 GDPR and data portability under Art. 20 GDPR also include your voice data: session and transcript data, including typed questions and stored text responses, as well as voice recordings still retained at the time the request is processed. Recordings undergoing processing that will be deleted immediately after transcription are not included. A pending access request does not extend the deletion periods stated above; the access response indicates for each recording whether it was included, still being processed, or already deleted. To request this, contact contact@beesaver.at.

Contact

Via contact form or at contact@beesaver.at

Source: Created with the imprint generator from firmenwebseiten.at