Privacy Policy

Who handles information

Mohammadreza Farsizadeh handles the information described here. Customers in Iran reach him on +98 917 474 7368; international customers on +374 98 809 757. He works remotely from Shiraz, Iran and Yerevan, Armenia, and communicates in writing by email, so no street address is published. Email: hello@rezafarsi.com. The suspended Armenian individual entrepreneur (ԱՁ) is mentioned only because older records may refer to it; it does not operate this site. This policy explains the public site and the separate processing of optional providers and linked tools.

Inquiries and correspondence

Submitting a project inquiry sends your name, email, language, service category and brief, together with a request reference, timestamp and a content hash, to the website backend. An allowed campaign/source category may accompany it when usage counting is enabled. We use this information to assess and respond to the request. Email or messaging correspondence is handled in the service you choose and may become part of a separately agreed project record. Please provide only information needed to discuss the work.

Newsletter and scorecard

Subscribing to the AI Visibility newsletter or requesting the scorecard checklist stores your email address, the page you signed up from (newsletter, scorecard or audit), the date and your consent in the site's Cloudflare D1 database. We use it only to send the newsletter and measure interest; we do not sell or share it. You can unsubscribe or request deletion at any time by emailing hello@rezafarsi.com. The current setup does not send automated email; if a third-party delivery provider is added, it will be named here before the first send.

Measurement and security

The site's own measurement code records aggregate page and event categories, language, and allowlisted campaign/source categories. It does not use an analytics cookie or persistent visitor ID. `?metrics=off`, DNT and GPC suppress this first-party collector and optional inquiry attribution; they do not disable Cloudflare security or Cloudflare's separate performance measurement. Cloudflare's RUM beacon collects browser performance measurements and page/referrer information. Its documentation says the beacon uses no browser storage; the request's source IP is discarded at the nearest Cloudflare data centre, and RUM data is generally processed there, which may be outside your country. The current automatic RUM setup excludes visitors connecting through the listed EEA/EU data centres. Hosting, abuse prevention and Turnstile may process network information such as an IP address. Verification may load when you open the assistant or interact with an inquiry form.

Optional assistant

The optional project assistant requires you to manually check an initially empty consent box before the first submission; it remains checked for further questions until you clear the conversation. On submission, the site sends your current question, up to three earlier questions in that conversation, and the selected language to the DeepSeek API. DeepSeek returns topic identifiers; the site uses those identifiers to show reviewed, prewritten answers. The site does not store the question text as an inquiry; the conversation remains in the open browser tab until cleared or the tab is closed. Do not submit personal, customer, confidential or secret information. DeepSeek's Open Platform Terms require developers to disclose their processing and have consent or another legal basis. Those API terms do not specify a retention period, whether downstream users' prompts are used to train models, or the processing location for those prompts. DeepSeek's general Privacy Policy says that data it covers can be retained as needed for the service and improvement/training and is processed and stored in China, but it expressly excludes end-user data sent through applications built on the Open Platform. We therefore cannot confirm an API-specific retention period, training use, processing location or transfer safeguard for questions submitted here, and make no promise of zero retention or Armenia-only processing. Read the https://cdn.deepseek.com/policies/en-US/deepseek-open-platform-terms-of-service.html and https://cdn.deepseek.com/policies/en-US/deepseek-privacy-policy.html

Retention and providers

The website database is configured for daily cleanup of inquiry and trial-feedback records older than about 90 days; aggregate marketing and trial records have the same cleanup target. This is a configured target, not a guarantee that every copy is erased on that schedule. Email, project/accounting records, security or diagnostic logs, provider records and recovery copies may be kept separately for different periods where needed for the service, legal duties or dispute handling. Cloudflare provides website hosting, Workers, database, security verification and the RUM service described above. Zoho hosts domain email. DeepSeek receives assistant questions only when you submit them after consent. Social and messaging providers receive information if you follow their links or contact them there. Data may be processed outside Armenia; no Armenia-only storage claim is made. For DeepSeek API questions, the public API terms do not identify the processing region or specific cross-border safeguards, and its general privacy notice excludes downstream end-user prompts.

Browser tools and requests

The separate SVG editor uses local browser storage for session recovery and recent imports; clearing site data for svg.rezafarsi.com can remove those copies. The Cookie Policy describes the observed browser behavior and its limits. You may email hello@rezafarsi.com to request access to, correction or deletion of personal information, or to object to or restrict processing where applicable. We will assess and respond under applicable law and may ask for information reasonably needed to verify your identity. You can stop an optional assistant submission before sending by leaving the consent box unchecked; for a request about information already sent, contact us. Clearing the browser conversation does not delete information already received by a provider. Do not email identity documents unless a secure and necessary verification method has been agreed. Mandatory rights remain unaffected.