What it is
This policy describes what this instance of MoDee SEO Engine stores, why it stores it, where it goes, and how long it is kept. It covers this hosted instance only. Self-hosting, where the software and the data both sit on your own machine, is not available yet; this policy describes the hosted service, which is what you can use today.
It is written to match what the software actually does, which is why several points below are specific about things that are not collected.
What is collected
| What | Why, and how long |
|---|---|
| Account details: email address, display name, password | To sign you in and isolate your data from other tenants. The password is stored only as a PBKDF2-HMAC-SHA256 hash with 260,000 iterations; the plaintext is never stored or logged. Kept until you delete the account. |
| API keys | To authenticate programmatic access. Stored as a hash; the plaintext is shown once at creation and never again. Kept until revoked or deleted. |
| Crawl results: URLs, titles, meta descriptions, headings, link graphs, word counts, issue lists | This is the product. It is what you asked the platform to collect from the sites you pointed it at. Kept until you delete the project. |
| Keyword, ranking, forecast and citation data | To produce the analysis and reports you request. Kept until you delete the project. |
| Queue job records | To run work reliably, retry failures and show progress. Finished jobs are purged after 7 days by a scheduled retention job. |
| Session records | To keep you signed in. Sessions expire after 14 days and expired sessions are purged by the same retention job. |
What is deliberately not collected
- No analytics or telemetry. No third-party analytics, session recording, error reporter or advertising script is loaded on any page of this site, and the software sends nothing to us or anyone else about your use of it.
- No IP addresses. The application does not store the IP address of visitors or API callers. Note that a reverse proxy in front of the service may keep its own access logs; that is outside the application.
- No tracking cookies. One cookie is set, and only after you
sign in: a session cookie that keeps you logged in. It is
HttpOnly,SameSite=Lax, and markedSecurewhen the instance is served over HTTPS. Anonymous visitors to the public pages get no cookie at all, which is why no cookie banner appears. - No third-party fonts or assets. Pages use your operating system's own fonts, so simply loading a page does not contact any other company.
Where the data goes
By default, nowhere. A stock install uses the heuristic language model and a synthetic search-data provider, so it needs no external API keys and sends nothing off the machine.
If you configure an integration, data goes to that provider and no further. Each one is opt-in, and each is something you enable deliberately:
- Search-data providers — DataForSEO, ValueSERP or Ahrefs receive the keywords and domains you ask them to look up.
- IndexNow (Bing, Yandex, Seznam) and the Google Indexing API receive the URLs you submit for indexing.
- OpenAI or Anthropic receive prompts if you switch the language model away from the local heuristic. Those prompts can contain page content, so treat enabling this as sending that content to that provider.
- Slack or SMTP receive alert and digest messages if you configure notifications.
We do not sell data, and we do not share it with anyone except the providers you have configured yourself.
Your rights and choices
You can export your data at any time, in CSV, JSON or NDJSON, from the project export endpoint or the dashboard. You can delete API keys yourself. To have your account and all associated projects deleted, ask the operator — the request is actionable because everything is scoped to your organisation and deletes with it.
If you are in the UK or EU, you have rights of access, rectification, erasure, restriction, portability and objection under the UK GDPR and GDPR. The export and deletion paths above are how those rights are exercised here.
Security and retention
Passwords and API keys are hashed, never stored in recoverable form. Every record is scoped to an organisation, and a request for another tenant's data returns "not found" rather than confirming it exists. CORS refuses to combine a wildcard origin with credentialed requests. The security and privacy page has the detail.
Retention is enforced by a scheduled job, not just described here: finished queue jobs are purged after 7 days, and expired sessions as soon as they lapse. Project data is kept until you delete it, because it is yours and deleting it on a timer would destroy work you did not ask us to remove.
This is a starting point, not legal advice. It describes the software's real behaviour, which is the part we can verify. Before relying on it commercially, have it reviewed and add the operator's legal entity and address, plus any jurisdiction-specific terms. Questions: modees700@gmail.com.