Plain-language summary
What do we receive?
Information needed for consultations, customer accounts, the newsletter, and website security.
Why do we use it?
To respond, provide services, manage projects, communicate, and maintain security.
What don't we do?
We don't sell user information or give it to others for unrelated advertising.
What choices do you have?
You can request access, correction, deletion, or unsubscription.
1. What does IranCoders mean in this policy?
In this policy, “IranCoders,” “we,” and “website” refer to the operator of irancoders.com . As final legal entity details are not included in the website's current information, no legal name, registration number, or registered address has been assumed. The contact page is the official contact channel.
2. What information may we receive?
The information depends on which part of the website you use.
Consultation form information
The current consultation form may collect your full name, mobile number, business name, type of need or service, approximate budget range, and a description of your idea, problem, or project. The time of consent and the version of the privacy policy accepted are recorded with the request. This form does not currently allow file uploads.
Please do not include highly sensitive information, passwords, banking details, access keys, other people's confidential data, or content you are not authorized to send in the initial form.
Newsletter information
The current newsletter form stores only your email address and the time you subscribed.
Customer account information
Public customer registration is available on the website and may collect your full name, email, mobile number, business name, role, and sign-in information. New accounts remain inactive until the email address is verified using a time-limited link; the verification time is also recorded in the account profile. An active account can display or record project information and status, visible milestones and reports, invoices, and support messages. File uploads are not available in the current account system.
Passwords are stored as hashes using Django's standard secure mechanism. Administrators and team members cannot view the original password. Secure password recovery through the registered email address and resending verification links for inactive accounts are available. Signed-in users can also change their password in account settings.
Meeting booking information in the Telegram bot
To book a meeting, we collect your full name, a short description of your needs, email address, and phone number so we can prepare for the conversation and coordinate the meeting. This information appears in the company's authorized dashboard, confirmation email, and company archive copy. Draft information is deleted when a selection is canceled or expires; finalized booking information is retained to coordinate and follow up on the meeting. The booking is recorded in IranCoders' internal calendar, and this information is not sent to the Google Calendar API.
Technical and security information
When you use the site, operational logs may record technical details such as the IP address visible to the network, browser and device type, request time and path, referring page, response status and errors. To limit abuse of sign-in, registration, consultation, newsletter, password recovery and email verification requests, short-lived hashed identifiers based on connection details or email are stored in temporary storage or time-windowed database counters. Durable limits use hourly windows and HMAC-protected identifiers.
Sensitive forms use IranCoders' own image CAPTCHA. Images are generated and answers checked on our servers, without sending data to Cloudflare for this purpose. Each image is bound to its browser session and form, is valid for five minutes and can be checked only once. Answers are stored as keyed hashes. Images are removed after checking; expired records are cleaned up on subsequent requests. The newsletter form does not use CAPTCHA.
Payment information
Project payments are currently made through the arrangements specified in the contract and invoice. The website does not receive or store full bank card details. The account area only displays invoice status and details; an online payment gateway is not active on the website.
3. How do we receive information?
- Information you enter directly into consultation, registration, profile, newsletter, or support ticket forms.
- Information recorded in customer accounts to manage projects, milestones, reports, and invoices.
- Correspondence related to a request or project.
- Technical information generated when you use the website.
- Information provided by an authorized organizational representative to coordinate a project.
- Necessary technical data from hosting, security, and content delivery providers.
We do not buy information from unrelated sources or collect user information for sale to others.
4. Why do we use information?
Information is used only to the extent needed for a specified purpose, including:
- Responding to consultation and contact requests, understanding initial needs, and assessing a potential engagement.
- Coordinating meetings, preparing proposals, and fulfilling written project commitments.
- Creating and managing customer accounts and displaying projects, reports, invoices, and support.
- Recording newsletter subscriptions and managing unsubscribe requests.
- Maintaining account and infrastructure security, limiting failed sign-in attempts, and preventing misuse.
- Identifying and resolving errors and meeting legal, financial, or contractual obligations.
- Improving the website experience using aggregate or anonymous information, if such reports are produced.
Information from a consultation request will not be used for unrelated advertising without your knowledge.
6. Who is information shared with?
User information is not sold or rented. It may be shared only as necessary with the following groups:
- Authorized team members who need the information to respond or deliver a service.
- Project-related contractors, where needed and subject to appropriate confidentiality commitments.
- The server and database hosting provider, to operate the website.
- Cloudflare for DNS management and domain routing; form CAPTCHA checks operate independently.
- Legal or judicial authorities where a valid obligation applies.
- A new business operator following a lawful transfer of operations, with the relevant obligations respected.
To send operational and security messages, necessary data such as your name, email address, and essential notification content passes through Google Workspace infrastructure. In the current version, form data is not sent to a separate SMS service, visitor analytics service, payment gateway, or AI service.
7. Where is information stored or processed?
Application and database information is stored on the server infrastructure used by IranCoders. Web traffic passes through Cloudflare's delivery and security network, and technical connection data may be processed across its distributed infrastructure. We therefore do not claim that all data is processed in a single country.
Infrastructure account names and confidential details are not made public. This policy must be updated if the processing location or primary provider changes materially.
8. How long is information retained?
Information is not retained longer than needed for its purpose, unless law, a contract, dispute resolution, or financial and accounting requirements necessitate a longer period.
- Consultation requests are retained for responding, reasonable follow-up, and managing the communication history.
- Account and project information remains for the life of the account and the necessary period after the engagement ends.
- Financial and contractual documents are retained according to the applicable requirements.
- Newsletter email addresses are retained until unsubscription is requested or the service stops.
- Form and failed sign-in rate-limiting data remains in the cache for no more than 15 minutes. Operational and security logs are retained only for the period needed to investigate incidents.
The software does not yet define a single numerical retention period for consultation requests, accounts, server logs, or backups. Exact periods must be set in the operational policy or each project's contract and will be added to this page once finalized.
9. How do we protect information?
We use measures appropriate to the type of data to reduce the risk of unauthorized access, disclosure, alteration, or deletion, including:
- Encrypted HTTPS connections and browser security settings.
- Hashed password storage and password validation.
- Restricting each customer to the projects, invoices, and tickets belonging to their account.
- Secure session and CSRF cookies and limits on failed sign-in attempts.
- Restricting administrative access and updating software according to operational needs.
- First-party CAPTCHA, request limits and server security settings to reduce form abuse.
No system is completely secure. If a significant security incident occurs, it will be investigated and, where necessary, users or the relevant authorities will be informed.
10. Project information and confidentiality
Information you send for initial assessment or project delivery is used only for that communication and engagement. However, the public consultation form is not a substitute for a project-specific confidentiality agreement.
If you need a confidentiality agreement before sharing project details, first use the contact page to make your request. Until an agreement is reached, do not send highly confidential information, access keys, or sensitive data about others. The precise terms for confidentiality, access, retention, deletion, or return of data are set out in the project's contract or agreement.
11. Customer accounts
Customer account users are responsible for keeping sign-in information confidential, using a suitable unique password, not sharing the account with unauthorized people, and promptly reporting suspicious sign-ins.
To maintain security, IranCoders may end suspicious sessions or temporarily restrict access. Password recovery is available through the registered email address. To close an account or resolve issues that password recovery cannot address, submit a request through the contact page.
13. Use of AI tools
In the current website version, consultation form information, customer account information, and tickets are not automatically sent for AI processing or model training. Providing AI services also does not mean your data is automatically used to train publicly available models.
If a project requires a third-party AI service, the data type, processing purpose, and limitations must be defined in that project's documents. Confidential data must not be given to a third party without appropriate authorization and assessment.
Chatting with the Telegram bot's smart consultant
Initial responses in the IranCoders website and bot chat are generated by AI. When you send a message after the short notice and link to this policy are displayed, the question text and up to four recent turns in the same conversation are sent to OpenAI to generate a response. Account information, project records, and tickets are not provided to the model. Responses alone are not quotations, contracts, or timeline commitments. Do not enter passwords, sign-in codes, banking information, or other people's confidential information in the chat.
Active conversation history is cleared after 7 days. You can delete it sooner using the command /privacy in the bot and choosing “Clear conversation history.” In the website chat, the “Clear” button is at the bottom of the window. Service backups may remain for up to 30 days and are not used to continue conversations. Consent timestamps, cost information, and duplicate-request prevention records remain independently of the conversation text. OpenAI's data retention is governed by its own policy. Requests are sent with the option store=false but this option does not guarantee that the provider retains no data whatsoever.
Referral to the team or creation of a ticket happens only after separate confirmation of the request and contact details. The full conversation history is not automatically sent to a specialist. To request deletion or raise a concern, contact support@irancoders.com .
Website and Telegram AI chat: sending your first message accepts this processing. Your question and up to four recent turns are sent to OpenAI to generate a response. The AI cannot access customer accounts, project records or tickets. Active history is cleared after 7 days and can be deleted earlier using /privacy → Clear chat history in the bot, or the Clear button in website chat; service backups may retain it for up to 30 days. OpenAI has its own retention policy; store=false is not a guarantee of zero retention. Do not send secrets or sensitive information. Human handoff requires your separate confirmation and does not automatically share the full AI history. Questions or deletion requests: support@irancoders.com.
14. What requests can you make?
- Ask for an explanation of the information retained.
- Correct inaccurate or incomplete information.
- Delete information where retention is not necessary.
- Unsubscribe from the newsletter.
- Close a customer account, where possible.
- Restrict the use of information where applicable.
- Raise concerns about the use or security of information.
To protect information, we may verify your identity or authority before acting on a request. Some information may not be eligible for immediate deletion because of legal obligations, financial records, contracts, security, or dispute resolution. In that case, we will explain the reason and the status of your request.
15. Information about children and young people
IranCoders services are designed for commissioning and managing business projects and are not offered directly to children. If we discover that information about a person who cannot give valid consent under applicable law was submitted without the necessary permission, we will follow up on a request to delete or review it.
16. Other links and services
The website may link to third-party websites, app stores, or services. Their privacy policies and practices are not controlled by IranCoders. Review their own terms and policies before sharing information with them.
17. Changes to this policy
This policy may be updated as website features, service providers, or legal requirements change. The last-updated date appears at the top of the page. Where possible, significant changes to how account holders' information is used will be communicated through an appropriate channel.
18. Contact about privacy
Use the contact page to request access, correction, deletion, or unsubscription, or to ask a privacy question. A separate privacy email address or registered address has not been defined in the project's current information, so no invented details are provided.
