Privacy Policy

Effective date: 10 July 2026

This policy explains what data PIJ Logger (“the Service”, log.pijcore.com) processes and why. The data controller is Roman Pysarskyi (Писарський Роман), Ukraine — [email protected].

1. Data we process

• Account data — your email address and account metadata (creation date, subscription plan).
• Project & configuration data — project names, retention settings, and token metadata. Project tokens are stored only as a SHA-256 hash; the raw token is shown once, at creation.
• Log data you send — the level, message, source, and metadata of each log record. You control this content; please do not send passwords, secrets, or personal data you have no basis to process.
• Technical data — IP address, timestamps, and request details, processed by our server and our CDN (Cloudflare) for security, rate-limiting, and delivery.

2. Cookies & local storage

We use only strictly necessary storage — no advertising or tracking:

• refresh_token — HttpOnly cookie that keeps you signed in (authentication).
• csrftoken — protects form submissions against CSRF.
• Cloudflare cookies (e.g. __cf_bm, cf_clearance) — set by our CDN for security and bot mitigation.
• Browser localStorage — stores your theme preference (pij_theme) and your cookie acknowledgment (pij_cookie_ack). These stay on your device.

Because these are essential to running the Service, they are used to provide the functionality you request.

3. How we use data

• to provide and operate the Service (store and stream your logs);
• to authenticate you and secure the Service;
• to enforce plan limits and prevent abuse;
• to communicate with you about your account.

4. Retention

Log records are deleted according to each project’s retention setting. Account and project data are kept while your account exists; contact us to delete your account and associated data.

5. Sharing

We do not sell your data. We share it only with infrastructure providers that operate the Service on our behalf (e.g. hosting and Cloudflare as our CDN), and where required by law.

6. Security

Traffic is served over HTTPS. Passwords and project tokens are stored hashed. Access to your logs requires your account or a valid project token. No system is perfectly secure, but we take reasonable measures to protect your data.

7. Your rights

Subject to applicable law, you may request access to, correction of, or deletion of your personal data. To exercise these rights, contact [email protected].

8. Children

The Service is not directed to children under 16 and is intended for professional/developer use.

9. Changes

We may update this policy; the effective date above will change. Continued use after an update means you accept the revised policy.

10. Contact

Privacy questions: [email protected]. See also our Terms of Service.