Privacy Policy

This policy explains how Albireus (“we”) collects, processes and uses personal data. Contact: support@albireus.com. This policy applies together with the Terms of Service, the Cookie Policy and the AI features notice.

Statutory notice

In accordance with the Personal Data Protection Act of the Republic of China (Taiwan), we inform you as follows:

• Name: Lin Chen Yu (operator of the Albireus service; contact email above).
• Purposes of collection: providing accounts, the knowledge workspace, transcription, the AI assistant and team collaboration; reviewing beta applications; billing and account administration; and operating the service.
• Categories of data: identification data (account, email, name); content (docs, audio, images, scans); usage records (usage counts, not content); and transaction data (plan, billing period, payment status, point deduction records).
• Period of use: for as long as your account exists; after you delete your account, as described under “Account deletion and data retention” below; and for any period required by law, for tax purposes or to handle disputes.
• Place of use: the Republic of China (Taiwan), and processing locations outside Taiwan where necessary to provide the service (see “Processors” below); payment data is processed by Paddle in the United Kingdom and elsewhere.
• Who uses the data and how: us, our processors, and the people you choose to share with.
• Your rights: to inquire about and review your data, obtain copies, supplement or correct it, ask us to stop collecting, processing or using it, and ask us to delete it. See the end of this policy for how to exercise them.
• If you do not provide the data: you cannot create an account or use features that require sign-in.

What we collect

• Google sign-in: your Firebase Auth user ID, email address, display name and profile picture.
• Beta applications: your display name, username, intended use and other questionnaire answers (when you submit an application).
• Content you create: docs, notes, database files, calendar entries, boards, canvases, presentations, transcription results and AI conversations.
• Audio and video: files you upload or record live, and the text transcribed from them.
• Usage statistics: number of requests, token counts, seconds transcribed, AI point deduction records and similar data, not including prompts or the text of your docs.
• Referral program: to prevent self-referrals and similar abuse, we store salted hashes of the IP address and of a randomly generated per-browser identifier (never the raw IP address). They are used only to tell whether an invite comes from the same device or network, never for tracking or advertising. A referrer's hashes are deleted 90 days after they were last seen; an invited person's hashes are only compared at sign-up and not stored. The random identifier lives in your browser and is removed when you clear site data.
• Transaction data: the plan you chose, billing cycle, current billing period, payment status, order number, payment currency and amount, billing country, and your Paddle customer and subscription IDs.

Payment and billing data

Payments are processed by Paddle.com Market Ltd (United Kingdom), the Merchant of Record for these transactions (earlier subscriptions were processed by NewebPay). Paddle processes the billing details you provide at checkout in accordance with its own privacy policy. Your card number, expiry date and security code are collected directly by the payment provider; we never receive or store them. We keep only the order number, amount, payment status and the corresponding plan period, for reconciliation and handling complaints. Billing records that tax law requires us to keep are retained until the statutory period ends, even if you delete your account.

Database scans and OCR

Scans and image-to-text requests are sent to our processing service, and some image enhancement may be performed by a processor. During this process, your images leave your browser.

Voice and video transcription

• Source audio files in the job queue are usually deleted once transcription is complete; the transcribed text stays in the job or doc.
• Audio or video you attach to a doc yourself is not deleted automatically.
• Live recordings use Google Cloud Speech-to-Text; file and YouTube transcription use the speech model services we integrate with.
• If you provide cookies to download from YouTube or capture a page that requires sign-in, they are used for that single capture only and are not kept as long-term credentials.
• Before uploading a file that contains other people's voices, please make sure you have the right to record and process it.

AI, conversations and memory

By default, text and image generation runs through our cloud model channel, which may send the docs, attachments or transcripts you select as context. See the AI features notice for details.

API keys you bring yourself are stored only in the browser on this device and are never written to the Albireus cloud database. Requests pass through our servers to the provider you specify; how those providers use the data is governed by their own terms.

Teams and public sharing

Teams you join and public links you turn on let people with access see the corresponding content; a public link can be viewed even without signing in. Please decide carefully how widely you share.

Processors and international transfers

To provide the service, data may be processed by Google Cloud and Firebase, Cloud Run, Vertex AI, Google Speech-to-Text, speech transcription providers, Paddle.com Market Ltd (United Kingdom, Merchant of Record; earlier subscriptions were processed by NewebPay in Taiwan) and email delivery services, and some of this processing takes place outside Taiwan. We engage processors only to the extent necessary to provide the features.

GIF search in team chat is provided by GIPHY (United States): the search terms you type are forwarded by our servers to GIPHY to get results; we do not give GIPHY your account or chat content. GIF images load directly from GIPHY's servers, so when a GIF is shown GIPHY receives your device's IP address and standard connection details. GIF search is unavailable offline.

Push notifications are delivered through Firebase Cloud Messaging (Google) to the devices where you turned them on; we store only each device's push token and delete it automatically when the device stops accepting pushes. You can turn pushes off under Notifications & privacy.

Cookies and similar technologies

We currently use only the technologies needed to keep you signed in and to run the interface; see the Cookie Policy for details. We do not use third-party tracking for advertising.

How to exercise your rights

Under Article 3 of the Personal Data Protection Act, you may ask to inquire about, review or obtain copies of your data, or to have it corrected, stop being processed, or deleted. You can delete your account yourself in the product (Settings → Account → Delete account; see the next section). For any other request, please email support@albireus.com from the address you registered with, and we will respond within a reasonable time. For export options, see Data export & portability.

Account deletion and data retention

• You can delete your account yourself at any time under Settings → Account → Delete account in Albireus (on the website, the desktop app and the mobile apps); no email is needed. To protect your account, you may be asked to sign in again first.
• Once you confirm, your account is disabled immediately and signed out on every device; it can no longer sign in or sync.
• The data in your account, including docs, notes, canvases, databases, transcripts and job records, uploaded files and media, collaborative document states, search indexes, settings, your wallet and remaining points, and the sign-in account itself, is permanently deleted from our live systems within 14 days of your request and cannot be restored. Please export anything you want to keep before deleting.
• After deletion from our live systems, copies may remain in backups: daily backups of collaborative documents are kept for at most 30 more days and then expire automatically, and our cloud provider’s file recovery features may briefly keep deleted files, for no longer than those 30 days. These copies are used only for disaster recovery; they are never used to restore a deleted account or for any other purpose.
• If you have an active subscription, we cancel its auto-renewal through Paddle when you delete your account (within one day at the latest), and you will not be charged again; any earlier NewebPay recurring payment is terminated as well. Fees already paid for the current period are not refunded automatically because of the deletion; you can request a refund under the Refund Policy. Remaining points are deleted with the account and are not kept or converted to cash. If the payment system temporarily cannot cancel it, we resolve the subscription first and then complete the deletion, aiming to stay within the 14 days above.
• Share links and access you granted stop working, and your membership entries in other people’s documents, folders or teams are removed. Content you left in shared spaces owned by others (such as their documents, team channels or direct messages) belongs to that space and may remain available to its other members.
• What is not deleted with your account: billing records that tax law requires us to keep (see “Payment and billing data” above) are retained until the statutory period ends; we also keep a deletion record that contains no personal data (a hash that cannot be turned back into your account, the request and completion times, and how many items of each kind were deleted) to show that the deletion was completed.

Users outside Taiwan

If you are in the European Economic Area, the United Kingdom or another region with similar rules, you also have the right to data portability, to restrict processing, to object to processing, and to lodge a complaint with your local data protection authority. Our legal bases for processing your data are the performance of our service contract with you (account, content, payments), compliance with legal obligations (billing and tax records), and our legitimate interests in keeping the service secure and improving it. For cross-border transfers, we rely on safeguards such as the standard contractual clauses offered by our processors. You can exercise these rights in the same way as described above.

Security and limitations

We use reasonable access controls and protect data in transit, but we cannot guarantee that our systems will never be interrupted or breached. Operations staff access system logs only when this is genuinely necessary to fix a problem.

Minors

The service is intended only for users aged 18 or older. If we find an account belonging to someone under 18, we may stop providing the service to it.

Changes to this policy

When the Privacy Policy or the Terms of Service change materially, we increase the version number and ask you to confirm again the next time you enter the workspace. Purely editorial changes that do not affect how your data is used may not require renewed consent.