Privacy policy — RediON Connect and RediON portfolio

1. Publisher and contact

RediON Connect is developed by Redion Çekrezi. Questions and data-rights requests about direct communications with the publisher can be sent to the contact email below.

The legal publisher is Redion Çekrezi; the verified postal address and direct contact are provided in the Impressum linked below. The publisher has approved a six-month post-closure retention limit for all direct email and website contact enquiries, including support, project, collaboration and employment enquiries. This privacy notice takes effect on 15 October 2026. The provider-specific storage and international transfers are described below.

2. What the plugin does

The public candidate bundles instructions, reference schemas and optional local scripts. It does not include another person's project references, creator account credentials, a hosted user-project database, or a publisher-operated data-collection API. It cannot sign in to accounts or grant itself permissions.

When a person invokes the plugin, the AI host may process messages and content provided by that person or retrieved through separately authorized tools. Those operations are governed by the host and third-party provider agreements, permissions and privacy notices. The publisher does not automatically obtain copies of those conversations or connected files merely because the plugin is installed.

3. Information that may be processed

Plugin execution can involve repository files, Drive documents, user-supplied instructions, chosen demo screenshots and test artifacts inside the person's own approved environment and connected services. What is accessible depends on the actual tools, permissions and user instructions.

If you contact the publisher for support, the publisher may receive your email address, the message and any voluntarily provided diagnostic information. When you visit these web pages, the website hosting provider may process necessary technical request data such as an IP address, timestamps and user-agent information. The portfolio middleware may set a language-preference cookie.

The website contact form requests the sender's name, email, optional company, project type and message; selected language and a referenced project may also be sent. The current visible form does not request a budget. The server sends the inquiry through Resend to the publisher's configured email inbox. The server handles the connection IP for short-term abuse-rate limiting; no centrally persistent RediON contact database is part of the code. Vercel, Resend and the recipient mailbox provider process the information needed for site delivery, message transmission and security under their respective services. Provider logs or backups are not automatically deleted by removing an email from the publisher inbox.

4. Purposes and permissions

User-connected project operations are initiated under the user's host/provider authorization and for the purposes they request. Direct correspondence is used to answer support, project, collaboration or job enquiries, diagnose reported issues and handle legitimate data-rights requests. Website request processing is used to deliver and secure the site.

For enquiries about a prospective contract, necessary contact handling generally relies on GDPR Article 6(1)(b); other voluntary enquiries and protection of the website against abuse generally rely on Article 6(1)(f), subject to legitimate-interest balancing. Compliance with applicable legal duties may rely on Article 6(1)(c). The language-preference cookie supports locale routing, not advertising. The publisher has approved the same direct-contact correspondence retention rule for every enquiry category described below. The functional NEXT_LOCALE cookie is used for language navigation, not advertising or analytics; the cookie is provided to deliver the requested site language, consistent with the applicable TDDDG rules. The publisher does not use contact inquiries for an unsolicited marketing newsletter. The plugin must ask for separate permission before consequential writes, billable provider calls, hardware access, deployments or public posting.

5. Storage, providers and international processing

This skills-only package does not run a central RediON database or a mandatory remote Validator service. It does not itself store user OAuth credentials. Content and drafts saved to GitHub, Drive or other chosen accounts remain subject to those providers' storage, logging, deletion and cross-border processing rules.

The portfolio pages run on Vercel; form delivery uses Resend and the configured receiving email provider. Resend states that message content and delivery logs are stored in the United States and that EU–US transfers are covered by its Data Processing Addendum, Standard Contractual Clauses and EU–US Data Privacy Framework participation (https://resend.com/security/gdpr). Vercel also describes potential processing outside the EEA and applicable transfer mechanisms (https://vercel.com/legal/privacy-notice). Provider-side retention may differ from the publisher's mailbox deletion rule; no claim is made of exclusively EU processing or zero logging.

6. Retention and deletion

Removing a plugin does not automatically remove content from a third-party repository, Drive account, ChatGPT session, local workspace or provider storage. Users should use the relevant service's controls to delete stored content and revoke access.

All contact correspondence received directly by the publisher via email or the website contact form, including RediON Connect support, portfolio and project enquiries, collaboration requests and job offers, is kept for no longer than six months after the enquiry is closed. Closure means the request has been answered, resolved, declined or determined to require no further action. The publisher manually deletes the messages and related contact copies under their control when this period ends; a longer retention period applies where required by law. Requests for earlier erasure are assessed under applicable law. Provider-managed technical logs and independent hosting or email-provider retention are outside the publisher-controlled mailbox deletion procedure. The policy does not promise immediate deletion of provider backups. No automated deletion system is currently in place.

7. Your rights and changes

Where applicable, data protection law may provide rights to access, rectification, erasure, restriction, portability and objection. Contact the publisher about information received directly for support, or contact the relevant platform/provider about data processed within its service. You may also lodge a complaint with an appropriate data-protection authority.

The contact form is voluntary; name, email, project category and message are necessary to respond. No solely automated decision with legal or similarly significant effects is made by the publisher from contact messages. For rights requests concerning content stored solely in ChatGPT, GitHub, Drive or another connected service, contact that provider. This notice is effective from 15 October 2026 and will be updated when material practices change.