SEO for Pro
Privacy Policy
Effective date: 14 October 2026 (GMT).
1. Who we are
SEO for Pro, available at seoforpro.com, helps website owners identify SEO issues, review evidence and plan improvements. This policy explains how information is handled when you use our website, create an account, run audits or connect Google services.
Operator: SEO for Pro, Egypt. For privacy requests, use our support form and identify your request as a privacy request. You can also email tecics@gmail.com. This is our receiving address for privacy requests.
2. Information we collect and why
| Information | Purpose |
|---|---|
| Account name, email address, account identifier, preferences and authentication records. | Create and secure your account, manage your plan and send essential account messages. |
| Password credentials for email registration. | Authenticate you. Passwords are stored as salted hashes, rather than readable passwords. Google sign-in does not give us your Google password. |
| Project domains, crawl URLs, publicly accessible page content and metadata, links, technical responses, screenshots, audit results and recommendations. | Perform website checks, generate reports, show evidence, keep audit history and reuse saved results. |
| Google connection credentials and selected property metadata, when you choose to connect a service. | Maintain the connection and associate the Google property you select with your project, as explained below. |
| Your name, email, topic and message when you contact support; delivery and abuse-prevention records. | Deliver, respond to and troubleshoot support requests and prevent duplicate submissions or abuse. |
| Website usage events, browser/device information and operational or security logs. | Understand product use, diagnose errors and protect the service. |
Only submit websites and information you are authorized to use. Public pages can contain personal information; avoid including confidential material in support messages or audit inputs.
3. Connecting Google services
Google sign-in and Google data connections are separate. You may create an account without connecting Google Analytics or Search Console. Each data connection requires your authorization.
- Google Analytics: we request read-only access to list accessible Analytics accounts and GA4 properties so you can choose a property for your project.
- Google Search Console: we request read-only access to list accessible verified site properties and their permission information so you can choose a site for your project.
- Current scope of the feature: the connection stores your selection. It does not currently retrieve Analytics traffic reports or Search Console search-performance reports. Any future use will be explained before it is introduced, with additional consent where required.
We store access and refresh tokens encrypted on the server, together with the selected property and connection status. Refresh tokens allow the connection to continue without asking you to sign in each time. These read-only connections do not authorize us to change your Analytics settings or Search Console site settings.
Google data commitment: SEO for Pro’s use and transfer of information received from Google APIs will follow the Google API Services User Data Policy, including its Limited Use requirements. Connected Google data will be used only for the disclosed user-facing features; it will not be sold, used for advertising, or supplied for general AI model training. Human access will be limited to your explicit permission, necessary security investigations or legal requirements.
You can disconnect either service in your project. This removes that project’s stored connection credentials and selection from the active application database. It does not delete your Google property or automatically disconnect other projects. You can also revoke the application’s access in your Google Account connections.
4. Service providers and sharing
External services process information needed to provide particular features:
- Google: sign-in, optional Analytics/Search Console connections, PageSpeed checks using submitted page URLs, and website usage analytics.
- OpenAI: selected audit evidence and website content used to generate suggested fixes. The current Google connection flow does not send connected Analytics or Search Console data to OpenAI.
- Search and backlink data provider: submitted domains used to retrieve search-visibility and backlink information.
- Mailgun and our support mailbox provider: recipient addresses and message content for account verification, password resets, welcome emails and support delivery.
- Hosting and infrastructure providers: application storage, processing, backups and service operation.
We may disclose information where necessary to comply with applicable law or investigate security incidents. The Google-data restrictions described above continue to apply to connected Google information.
5. Cookies and website analytics
We use session mechanisms to keep you signed in and browser storage to remember preferences and application state. We also use Google Analytics to measure visits and actions such as registration, opening projects, completing audits and viewing reports.
Our custom analytics events are designed to exclude names, email addresses, submitted website URLs, report text, passwords, API responses and connection credentials. Google Analytics can still process technical information and use cookies under its own service settings. Website analytics is separate from a customer’s connected Analytics property.
The current analytics implementation checks Do Not Track, Global Privacy Control and the application’s analytics-consent setting before enabling tracking. You may also control cookies through your browser; blocking essential storage can affect sign-in. You may contact us with questions about analytics or your privacy preferences.
6. Retention and deletion
We keep account information, projects and saved reports to provide your workspace, audit history and cached results. Archiving a project is not permanent deletion. Support messages can remain in the support mailbox after delivery.
Disconnecting Google removes the relevant project’s active connection record as described above. Revoking Google access prevents further authorized use of that grant. To request account or report deletion, contact support; we may need to verify your identity.
Saved accounts and reports do not currently have a fixed automatic expiry. Deletion requests are handled through support. We assess the data covered by your request, any records needed for security or legal obligations, and copies in backups, and explain any retention that remains necessary. Deletion from the active service does not mean every backup copy is removed immediately.
7. Security
Safeguards include HTTPS, hashed passwords, encrypted Google connection tokens and account/project access checks. No online service can guarantee absolute security. Please keep your sign-in credentials secure and report suspected unauthorized access to support.
8. Your choices and rights
You can edit supported profile details, change your password, disconnect Google services and control browser storage. Depending on applicable law, you may have rights to access, correct, delete or receive a copy of your personal information, restrict or object to processing, withdraw consent, or complain to a supervisory authority. Contact support to make a request. Identity verification may be required to protect your account.
We process information to provide the service you request, protect and maintain it, meet applicable legal obligations, and, where required, with your consent. The applicable basis depends on the purpose and the law that applies to you.
9. International processing
Our providers may process information in countries other than your own. This includes processing outside Egypt by international providers. Contact us for information about the providers and arrangements relevant to your data.
10. Changes to this policy
We will update this policy when our practices change and show its effective date. Material changes, particularly new uses of connected Google information, will be disclosed before those uses begin, with renewed consent where required.