Privacy Policy

Last updated:

Belgi is operated by:

Begaiym Adylbek Kyzy
IČO: 11667079
Varšavská 715/36
120 00 Praha – Vinohrady
Czech Republic
Email: begaiym.adylbek@gmail.com

Special categories of personal data — prohibited use

Uploading, entering, collecting or processing special categories of personal data under Article 9 GDPR through Belgi is prohibited, including in source PDF files and images, form definitions, manual submissions and voice input. This includes data revealing racial or ethnic origin, political opinions, religious or philosophical beliefs, trade union membership, genetic data, biometric data used to uniquely identify a person, health data, and data concerning sex life or sexual orientation. Consent or another Article 9 exception does not override this contractual prohibition. Ordinary personal data may be processed subject to GDPR and these terms. Applicable provider restrictions also continue to apply. Uploading, entering, collecting or processing personal data relating to criminal convictions and offences under Article 10 GDPR through Belgi is also prohibited across the same inputs and processing routes. This contractual prohibition applies even where such processing could otherwise be authorised by law.

The application owner is responsible for form content, the purposes and lawfulness of processing, a valid legal basis, privacy notices, access permissions, retention and handling data subject requests. Belgi retains its own applicable obligations. This is a contractual restriction: Belgi does not guarantee technical recognition, filtering or blocking of prohibited data; manual input is subject to the same prohibition as AI features.

If prohibited data is accidentally transmitted, stop further entry and processing of that data and promptly contact the application owner and Belgi at begaiym.adylbek@gmail.com. Identify the application, approximate time and affected records without repeating the prohibited content or attaching it to the message. The owner and Belgi will coordinate appropriate access restriction, correction or deletion using available tools and documented instructions, assess any incident and applicable notification duties, and explain any limits involving subprocessors or backups. Automatic detection or automatic deletion is not promised. Existing retention periods, backup limitations and legal preservation duties continue to apply.

1. Scope and who is responsible

This policy explains how personal data is handled on belgi.io, in Belgi creator accounts, and in applications created and published using Belgi.

Belgi is the data controller for its own website, creator accounts, support, and service administration. When someone uses a published application to collect information for their own purposes, that application owner is normally the controller of the information submitted to it. Belgi processes such information on the owner's behalf as a processor. The application owner is responsible for providing an appropriate privacy notice, establishing a legal basis, and setting retention rules. Our Data Processing Agreement describes the relevant processing arrangements.

2. Creator accounts

You can sign in using Google, GitHub, or another sign-in option offered on the website. Depending on the provider and your settings, we receive your account identifier, name, email, email-verification status, and profile picture. We retain the account information needed to provide Belgi, including linked sign-in providers, account creation details, and acceptance of our terms.

We do not receive your Google or GitHub password or request access to Gmail messages, Google Drive files, or private GitHub repositories. Signing in does not automatically subscribe you to marketing messages.

3. Source documents, camera, and form drafts

When you choose to analyse a document or camera image, its contents are sent to an AI service to identify sections, fields, labels, and other form elements. Any personal data visible in the source may be included in that processing. The image remains in your browser until you confirm analysis; camera access is requested only when you use the camera feature.

Belgi does not archive the original uploaded PDF or image in its application database. The resulting form structure, your edits, and published form versions are saved to your account and may themselves contain personal data.

Use blank or redacted templates where possible. Do not submit sensitive personal data to AI features where applicable provider conditions prohibit it. You are responsible for ensuring that any personal data you submit can lawfully be processed.

4. Publishing applications

To create and operate your application, we process its name, address, form configuration, selected hosting and AI regions, deployment status, technical identifiers, and information needed to troubleshoot errors. The published application runs on hosting infrastructure with its own database. We send the owner an activation email after deployment. On successful publication, we also record the publishing user, application, confirmation time and version of the accepted GDPR processing restrictions as part of our service administration records.

5. Accounts and access within published applications

Published applications store user email addresses, roles, securely protected passwords, invitation and password-reset information, optional two-factor authentication details, and session information. Administrators can invite users and manage their access. Invitation links ordinarily expire after 48 hours; password-reset links expire after 30 minutes. Application sessions have a maximum lifetime of seven days, unless ended earlier.

Your Belgi creator account and your accounts in published applications are separate. Keep invitation links and authentication information confidential.

6. Voice input, submitted records, and PDF exports

Voice input is optional; users can fill in forms manually. If you enable the microphone, audio is sent to a speech-recognition provider, and the transcript and relevant form field descriptions are processed by an AI service to suggest values for the appropriate fields. Review and correct suggested values before submitting.

The original audio recording is not saved in the application's database. To help recover from interrupted requests, full transcripts and suggested values may be stored encrypted for a 15-minute retry period. Expired data is removed through subsequent automated cleanup, which may not occur at the exact moment the period ends. Temporary data may also exist in browser or server memory.

Submitted values, submission time, record identifier, and submitting user are saved in the application's separate database under the application owner's retention rules. Administrators can view application records; ordinary users can view their own records. PDF exports are generated in the browser from the record already loaded there, without sending it to a separate PDF conversion provider. Downloaded or shared copies are not erased when the original record is deleted.

Microphone permission does not replace any legal basis or notice required to record or process another person's data.

7. Why we process information

When Belgi is the controller, we process personal data as needed to:

  • Provide the service and administer accounts and applications — performance of a contract where applicable (GDPR Article 6(1)(b)); for an organisation's representatives, our legitimate interest in serving that organisation (Article 6(1)(f)).
  • Answer support requests, protect the service, prevent misuse, and resolve technical issues — our legitimate interests (Article 6(1)(f)), or contractual necessity where applicable.
  • Comply with legal obligations — Article 6(1)(c).

Application owners determine and explain the legal basis for information collected through their applications. Device permissions alone are not GDPR consent. Belgi does not sell personal data or use it for advertising or unrelated marketing. AI features assist with form extraction and data entry; they are not designed to make solely automated decisions with legal or similarly significant effects.

8. AI providers and processing regions

Source-document analysis uses AI model inference in the EU, subject to provider availability and required privacy safeguards. If an eligible EU route is unavailable or cannot be verified, analysis does not continue in another region.

When publishing an application, you can select its database and server region and separately its AI processing region (EU or US). Voice transcription and field extraction are directed to the selected AI region. These choices do not mean all network traffic, hosting operations, emails, support, diagnostics, logs, or backups stay in that region.

For AI requests handled through our AI gateway, we require Zero Data Retention (ZDR) and prohibit use of prompts for model training; requests fail if an eligible route is unavailable. These gateway conditions do not apply automatically to direct speech-recognition requests, and they do not erase saved forms, submissions, backups, or operational metadata. AI provider rules and legal exceptions may still apply. You should not treat ZDR as a substitute for a legal basis or safeguards for international transfers.

9. Cookies, device permissions, and technical data

We use essential authentication and security cookies to support sign-in. A first-party BELGI_LOCALE cookie remembers a language you select for up to 365 days; it stores only the language code and is not used for advertising or analytics. Without this cookie, we choose a supported language using your browser preferences. You may change the language or delete the cookie in your browser.

Belgi does not currently use advertising trackers or optional analytics cookies. Hosting, authentication, and security services may handle IP addresses, browser and request information, timestamps, and error diagnostics as needed to operate and protect the service. You can revoke camera and microphone permissions in browser settings, but doing so does not delete data already transmitted.

10. Providers and sharing

We use Vercel for hosting and AI gateway services, Neon for databases, Google Cloud for regional speech recognition, Resend for operational emails, and Upstash for rate limiting. Google and GitHub may process information when you choose their sign-in services. AI inference providers receive the content necessary for the requested task through the applicable routes. The precise provider can vary.

See our Subprocessors page for further details. We share information with these providers only as needed to deliver and protect the service, and when disclosure is required by law or necessary for legal claims. Application owners and authorised administrators can access information within their applications according to their roles.

11. International transfers

Some providers may process information outside the European Economic Area. Where GDPR transfer requirements apply, the responsible parties must use an appropriate transfer mechanism, such as an adequacy decision or standard contractual clauses and other required safeguards. A selected server or AI region does not guarantee that every related processing activity occurs exclusively there. Contact us for details relevant to a particular use case.

12. How long we keep data and how deletion works

We keep creator accounts, saved forms, deployment information, and related administration records while needed to provide the service, unless an applicable legal obligation or justified retention requirement applies. Original uploaded documents and audio recordings are not archived in our application databases. Submitted records remain subject to the application owner's retention instructions; the service does not currently offer automatic per-record retention schedules or all deletion/export controls.

An unpublished draft without deployed resources can be deleted directly. An application owner may request deletion of a published application; its access is blocked once the restriction is confirmed, and permanent deletion is scheduled after 30 days. The owner can cancel within that period, provided final cleanup has not begun. Deletion removes the dedicated application hosting and database, including users, invitations, sessions, and submissions, along with the corresponding application content. Limited administrative and legally required records may be kept for a longer period.

A creator may also request deletion of their profile and its owned applications, with a 30-day cancellation period. Application cleanup takes place before final profile deletion. Access restrictions, restoration, and final deletion may take time to complete; scheduled dates are not guarantees of execution at a precise moment.

Backups, provider logs, records retained by law, and copies downloaded or shared by users may remain under separate retention periods. Deleting an account does not automatically erase those copies. Contact us or the relevant application owner to request access, export, correction, or deletion not offered in the interface. Retrieve necessary information before requesting deletion because application access is restricted during the cancellation period. More information is available on Data deletion.

13. Your rights

Subject to GDPR conditions and exceptions, you may request access, correction, deletion, restriction, or portability of your personal data; object to processing based on legitimate interests; and withdraw consent where consent is the legal basis. Withdrawal does not affect processing already carried out lawfully.

For Belgi creator account information, contact us at the address above. For information collected by another person's published application, contact that application's owner first; Belgi assists them where required. We may verify your identity before responding. We normally respond to GDPR rights requests within one month, subject to permitted extensions. You may lodge a complaint with your competent data protection authority, including the Czech Office for Personal Data Protection (ÚOOÚ).

14. Support and security

When you contact support, we process your email and message to respond. Our email delivery and security providers may process the information necessary to deliver messages and prevent abuse. Please do not send passwords, API keys, authentication secrets, or unnecessary sensitive information. We use access controls, protected credentials, and other appropriate technical and organisational measures, but no online service can guarantee absolute security.

15. Changes and contact

We may update this policy as our services or processing change. We will update the date above and communicate material changes where appropriate. Updating this policy does not replace any consent required by law.

Questions about privacy, providers, retention, or processing arrangements: begaiym.adylbek@gmail.com or the postal address above. See also our Terms of Service, Data Processing Agreement, Subprocessors, and Data deletion.