Legal / Dirextalk
Dirextalk Privacy Policy
Last updated:
This policy covers this static website and information handled through Dirextalk project-controlled support and safety channels. It does not replace the privacy notice of an independent Dirextalk or Matrix node operator.
Dirextalk is operated by an individual developer. The developer is responsible for personal information handled through this website and project-controlled channels. Privacy requests can be sent to liyananinsh@outlook.com.
1. Scope and responsibility boundaries
Dirextalk provides software and documentation for owner-controlled, Matrix-backed communication nodes. Independent node operators choose their hosting, users, rooms, moderation, logs, retention, backups, integrations, and purposes. Their processing is governed by their own notices and applicable obligations.
Using an independently operated node does not, by itself, send its room history to this website or project support. Project maintainers may still be responsible for processing they actually determine or carry out; responsibility depends on the facts and cannot be excluded by a label.
2. Website requests and current tracking practices
The current website is a static website. The published code does not include project-operated analytics, advertising trackers, marketing cookies, account registration, contact forms, or embedded social feeds. We do not use the site to profile visitors for advertising.
A production host, content-delivery network, DNS provider, or security provider may automatically receive request data such as IP address, timestamp, requested path, referrer, browser or device information, and security signals, and may retain security logs. The specific production vendors and retention settings must be disclosed when deployment is finalized.
Outbound links, including GitHub repository links, take you to third-party services. Those services receive your request and apply their own terms and privacy practices.
3. Information you send and why it is used
If you email liyananinsh@outlook.com, Outlook and its service providers may process your email address, message, routing metadata, attachments, and any support, privacy, safety, or troubleshooting details you choose to provide. Please send only what is necessary and never send server keys, administrator credentials, access tokens, private keys, or unrelated personal information.
We use this information to answer requests, diagnose reported issues, protect people and project-controlled systems, document decisions, establish or defend legal claims, and comply with applicable obligations. Depending on the jurisdiction and context, processing may be necessary to respond to your request, based on legitimate interests in support and security, required by law, or based on consent where consent is the appropriate lawful basis. This is not a claim that one legal basis applies everywhere.
- Contact data: email address, display name, and reply details you provide.
- Message data: the request, report, attachments, and contextual identifiers you provide.
- Technical data: diagnostic details you provide and ordinary email delivery or website security metadata.
- Request records: verification, correspondence, resolution, and safety or legal records created while handling the matter.
4. Retention
We keep project-controlled support and rights-request material only while reasonably needed to handle and document the request, maintain security, meet applicable recordkeeping duties, or resolve disputes. Routine support material should be reviewed for deletion when the matter is closed and no continuing security, legal, or operational need remains.
Safety, fraud, security incident, legal-claim, or rights-verification records may be retained longer when reasonably necessary for those purposes. Hosting and email providers may keep logs or backups under their own schedules. A precise production retention schedule must be completed after the operator and vendors are confirmed.
Independent node operators control their own retention and backup schedules. Deleting data on one node may not erase copies already delivered to other participants through federation.
5. Recipients, federation, and international handling
Project-controlled information may be handled by people who need it for support, safety, security, legal, or infrastructure work and by the relevant email, hosting, content-delivery, DNS, or security providers. We do not describe those providers as sellers of your information.
Matrix federation can deliver room events and technical metadata to independently operated participating nodes. Those operators are separate recipients and may retain data under their own rules. The Dirextalk project cannot erase data controlled by another operator merely because that operator uses Dirextalk software.
Email, GitHub, hosting, federation, and support may involve international processing. Applicable transfer requirements and safeguards depend on the operator, vendor locations, participants, and the people whose information is involved; those requirements must be assessed from the actual processing rather than assumed by this policy.
6. Your choices and rights
You may contact liyananinsh@outlook.com to ask about project-controlled personal information or request access, a copy, correction, supplementation, restriction, objection, deletion, or withdrawal of consent where the requested right applies. A parent or guardian may submit an appropriate request for a minor. Contact the relevant independent node operator for data it controls.
We may request proportionate information to verify identity, authority, or guardianship and to protect another person's data. We will respond within the period required by applicable law, explain a refusal where required, and provide information about an applicable complaint or appeal path. Rights vary by jurisdiction and may be subject to lawful exceptions.
7. Security and incidents
We use measures appropriate to the project-controlled information and the systems currently used, including limiting access to people who need it and minimizing the information requested. No transmission or storage method is guaranteed secure.
Report a suspected security incident involving this website or a project-controlled channel to liyananinsh@outlook.com. We will investigate credible reports, contain and document incidents within our control, and notify affected people or authorities when applicable law requires it. For an independent node incident, contact that node's operator first.
8. Children, changes, and contact
Project-operated interactive services and support are not offered to users under 18. If we learn that a person under 18 sent personal information to a project-controlled channel, we will limit further use, assess any safety or legal preservation need, and delete or otherwise handle the information as applicable law requires.
Questions and requests can be sent to liyananinsh@outlook.com. We may update this policy when facts or practices change and will update the date above. Material changes should be communicated in a manner appropriate to the affected processing; where law requires consent, a policy update alone is not a substitute for obtaining it.