Privacy Notice
Version: privacy-2026-11-09 · Version date: 9 November 2026 · English translation
This English version is a translation of the German privacy notice. It describes the same processing; selecting English does not change the controller, purposes, legal bases or applicable data-protection law.
1. Controller
NEWAYS Management und Beratungs GmbH, Reiherweg 14, Priel, 9431 Wolfsberg, Austria, FN 159425 z, Regional Court Klagenfurt, VAT ID ATU 42733306. Contact for privacy requests: info@getskald.ai.
For privacy and security questions, you can also contact security@getskald.ai.
2. Website, account and contract
We process technical access data, IP address, time, URL, browser/client information and security logs, as well as account data such as email address, display name, password hash, verification status, roles, technical IDs, licence, payment, device and usage status. Purposes include providing and securing the website and apps, authentication, contract performance, billing, abuse prevention, support and statutory evidence.
Legal bases include Art. 6(1)(b) GDPR (contract and pre-contractual steps), point (c) (legal obligations) and point (f) (secure, stable and auditable operation). Acknowledging this notice is not consent.
The website and account use only technically necessary cookies or equivalent storage for sign-in, security, language and limited purchase status. Skald currently uses no marketing or audience-measurement cookies requiring consent.
3. Payments and email
We use Stripe for checkout, payment, invoices, refunds, fraud prevention and payment evidence under Stripe’s own and contractually agreed privacy terms. Skald does not store full card details.
Transactional emails are sent through Postscale. Recipient address, subject, content and technical delivery data are processed.
For purchases through the Apple App Store, Apple processes payment under the terms applying there. Skald processes purchase and subscription evidence supplied by Apple and technical association identifiers to assign entitlement and reflect its duration, renewal, revocation or refund. Skald does not receive full payment-instrument details through this process.
4. Audio and text processing
- Fully local transcription: audio and transcript are processed on the end device unless the user initiates transfer or sharing.
- BYO Azure: audio and/or text are sent to the Azure environment configured by the user or organisation. Responsibility and processing also depend on that customer configuration.
- Skald EU: audio and/or text are processed for the selected function through Skald infrastructure and configured Microsoft Azure services in the Sweden Central region.
Depending on the selected cloud function, audio, the input text required for the task, active dictionary terms and optionally supplied participant or context hints are transmitted through the selected processing route. With fully local transcription, audio and transcript remain on the end device. If a cloud function is subsequently used for text polishing or translation, the required input text is sent to the selected service. Name suggestions derived from conversation content are not biometric identity verification. Account, billing and operational data are processed separately for the purposes described in this notice.
Audio and text data processed through Skald EU are not used to train AI models. This commitment applies to Skald EU; Azure services configured by the user or their company are governed by the respective customer agreements and settings.
Temporary Skald EU artefacts are generally scheduled for deletion within 24 hours. Usage and cost metadata are generally retained for 365 days and audit evidence for 730 days, unless a longer statutory duty or a specific security/legal case applies. Backup retention may delay physical deletion until the operational deletion cycle completes.
4a. Optional storage and retrieval with Skald Relay
Skald Relay stores transcript and result text that you explicitly transfer, together with associated information such as title, language and timestamps, in your personal Relay area. Relay is separate from temporary audio and text processing; the 24-hour period stated for that processing does not apply to content deliberately stored in Relay. This Relay function does not store audio files.
The purpose is to make content available and transfer it, at your request, to agents or other recipient programs you authorise. The legal basis is performance of the requested service under Art. 6(1)(b) GDPR; technical security and delivery evidence serves the legitimate interest in secure and auditable operation under point (f). NEWAYS does not use Relay content to train AI models.
Content remains stored until you delete it, an authorised recipient program confirms successful receipt, or your account is deleted. A download alone is not a receipt confirmation. Following successful deletion or confirmation, the content is removed from active Relay storage. Local originals and copies already transferred to recipients are unaffected. Expiry of upload entitlement alone does not delete existing content; authorised access to retrieve and delete it remains available in the existing account, unless security or legal grounds prevent this.
Content-free technical identifiers and delivery/deletion status remain until deletion of the associated account to handle repeated transfers and confirmations safely. They contain neither transcript text nor titles. Manual account deletion, including associated Relay content, agent keys and delivery/deletion markers, follows the existing account-deletion procedure within five working days (Monday to Friday, excluding Austrian statutory holidays); legally required evidence is excepted. Separate operational and security evidence is not automatically removed by this deletion of Relay content; the purpose-based retention rules described in section 7 apply to that evidence.
Relay content is encrypted in active storage. Authorised recipient programs receive the content needed for processing; this is therefore not a promise of end-to-end encryption. Recipients you authorise may process data further in their own environments. Their storage locations and deletion procedures depend on your selection and the terms applying there. Deletion or key revocation in Skald does not recall copies already transferred.
Removal from active Relay storage is not a promise of immediate physical erasure from backups. Backups expire under the operational backup cycle; they are not a routine access route for users or agents.
5. Local data and diagnostics
Desktop and mobile apps store settings, protected session and access information, device information, histories and exports locally. Users control local deletion through app and operating-system functions. Voluntary bug reports may include descriptions, diagnostics and screenshots explicitly selected by the user.
6. Recipients and transfers
Recipients may include hosting, infrastructure, email, payment and cloud providers and customer-configured BYO providers. Where data are processed outside the EEA, we use legally prescribed transfer mechanisms and additional safeguards where required.
7. Retention
Account, contract, payment and licence data are stored during the contract and afterwards according to statutory retention, warranty, limitation and evidence duties. Security logs are retained only as long as required for protection, investigation and evidence. Legal acceptance evidence is retained for the contract term and relevant limitation and evidence periods.
8. Rights
Data subjects have rights under the GDPR to access, rectification, erasure, restriction, portability and objection. Consent may be withdrawn for the future. Complaints may be submitted to the Austrian Data Protection Authority, Barichgasse 40–42, 1030 Vienna.
9. Required and optional processing
Skald cannot be provided without data required for the account, licence, security and contract. Cloud routes are active only where required by the package or selected and configured by the user or organisation.
10. Updates
A new versioned notice will be provided for material changes. Where required for continued app use, receipt will be acknowledged online again.