Privacy Notice

This notice explains how Hasna, Inc. handles personal data when you visit Alumia, create an account, use AI and connected apps, manage a subscription, or contact support.

Where we operate. Paid plans are offered only to customers with a billing address in the United States. The free plan is available without that restriction.

Data we handle

We handle account and organization details; authentication and security records; workspace content and agent instructions; connected-service data you choose to use; usage, device, network, and diagnostic data; support messages; and pseudonymous payment, invoice, refund, dispute, credit, and ledger records. The payment processor handles card details; Alumia should not store full card numbers.

Why we use data

We use data to provide requested features, execute your instructions, maintain accounts and subscriptions, meter credits, prevent abuse, secure and troubleshoot the service, communicate about the product, meet legal obligations, and improve reliability. We do not use third-party analytics. If you sign up through a referral link, we record which link your sign-up came through, so that your sign-up is attributed to the person who referred you; this happens on our servers at sign-up and no cookie is set for it. We keep that record for 24 months from your sign-up so that referral credits can be honoured if the programme resumes, on the basis of our legitimate interest in running the referral programme (GDPR Art. 6(1)(f)). It is not used for profiling. It is not sold, and not shared outside our organisation except with the person who referred you, who sees that their code was used and when, without your identity. Our service providers process it on our instructions, and they are listed in the subprocessor list. We record first-party product usage events, kept for 180 days, to operate and improve the service.

AI and connected services

When you use AI features, your prompts and the content you submit are sent from our server to OpenRouter, which forwards them to the model provider that serves your request — or, for open-weight models, to a third-party inference host that OpenRouter selects, such as BaseTen. We require that your content is not used to train models. We do not restrict processing to a region: your content may be processed on infrastructure in other countries, including China for DeepSeek, Kimi (Moonshot) and MiniMax models. Connected services such as GitHub and Telegram receive data only when you connect them, and your use of them is governed by their own terms.

Retention and deletion

Workspace data is retained while needed to provide the service and is deleted after a valid deletion request, subject to backups and technical processing time. Where a record has to be kept, we remove your account identifier from it. If the record keeps a reference to you instead, the paragraph for that record says what kind of reference it is and whether we can link it back to you. We keep each record only for the purpose and period stated below. Security, fraud-prevention, tax, invoice, payment-event, and immutable ledger records may be kept longer where necessary to establish, exercise, or defend legal claims and meet financial obligations. Deleting an account does not rewrite retained finance history. The specific records we keep, and for how long, are set out below.

Billing and tax records. We keep invoices, payment records and the related subscription identifiers for as long as tax and accounting law requires — currently up to ten years from the end of the financial year they relate to. While your account exists these records carry your account identifier; if you delete your account we remove it and keep a keyed pseudonymous value instead, which we can re-link to you because we hold the key. Invoices and the payment provider's customer record are held by the payment provider under its own retention.

Email suppression. If you ask us not to email you, we keep your email address on a suppression list for that one purpose only, for as long as the instruction has to keep working; we delete it if you withdraw the request. If an email to you bounces or you mark one as spam, we keep your address on the suppression list so we stop sending to it, except for a sign-in or account email that you request. We keep the entry for as long as it is needed to keep not sending to that address.

Product usage events. We record first-party product events for 180 days to operate and improve the service. While your account exists these records carry your account identifier. If you delete your account, we remove that identifier and the record keeps only a workspace reference until it is deleted after 180 days.

Acceptance records. If you delete your account, we keep a record of what you accepted — the documents, their versions and digests, and the date — as evidence of the contract and for the establishment or defence of legal claims, for as long as the contract and the applicable limitation period for legal claims run, and no longer than we keep billing records. While your account exists, that record also holds the IP address the acceptance came from. When you delete your account we remove the link to it and the IP address, and the record keeps only a keyed reference, which we can re-link to you because we hold the key.

Service logs. We keep logs of requests and errors to operate and secure the service. They contain identifiers such as your account reference and are kept for 30 days, then deleted.

Backups. To recover from failures, we keep database backups for 14 days and previous versions of deleted files for 90 days, then delete them. If the database is ever shut down, a final backup is taken. It is deleted within 14 days, or within 14 days after a restore that uses it is complete.

Referral records. If you signed up through a referral link, we keep the record of which link your sign-up came through for 24 months from your sign-up and then delete it. If a referral reward was decided — issued, or withheld because the monthly limit was reached — we keep the record of that decision — the date, the number of credits, and references to the referrer, to the sign-up, and to the workspace credited. Each reference is a one-way hash of an internal identifier: while the account or the workspace exists it can be recomputed, and once both are gone our systems no longer hold the identifier to recompute it from, apart from backups and logs until they expire. We do not keep the person's name or email address in that record.

Access log. Access by our team to referral and billing records is logged: who opened which view, when, and how many rows, and for detail views the account or workspace the view is about. The log is kept for 24 months.

Security

We use access controls, tenant scoping, encrypted transport, secret handling, signed webhooks, and audit records appropriate to the preview. No internet service can promise absolute security. Please report concerns through our Security page.

Your choices and rights

You can ask to access, correct, export, restrict or delete personal data, object to processing based on our legitimate interests, and withdraw consent. Where local law gives you additional rights, those apply too. We may need to verify your identity and may retain data where the law permits or requires it.

You can ask us to restrict how we use your data, or object to a use based on our legitimate interests, by writing to [email protected]. We answer within one month. If a request is complex we may extend that by up to two further months, and we tell you within the first month if we do. If you cannot sign in, or cannot receive our email, write to [email protected] and we will handle the request the same way — within one month, and asking only for information already in your account to confirm it is you.

Contact

Privacy requests: [email protected].