Legal
Privacy Policy
Last updated:
On this page
This Privacy Policy explains what information Fair Fractal Corp. ("Company", "we" or "us") collects when you read P2P Blog (the "Blog") or use its admin panel as an author or editor, how we use it, who we share it with, and the choices you have. You can read the Blog without an account. It has no comments, newsletter sign-up or contact forms, and it does not use analytics or advertising.
1. Information We Collect
When you read the Blog
- Request information. Like any website, the Blog receives the information your browser sends with each request: your IP address, the page, image or feed you ask for, the time, your browser’s user agent and language settings, and the address of the page that linked you to it. The Blog’s own code does not save this information to its database. Our hosting provider, Railway, may record request details in its service logs.
- Language and country. When you open the home page or a list of posts without having chosen a language, we use your browser’s language settings to show the Blog in English, Portuguese or Spanish. If the network in front of the Blog adds a country header to the request (for example Cloudflare’s CF-IPCountry), we use that country as a fallback when your browser’s languages do not match one of ours. The country is used only to choose the language for that request and is not stored.
- Searches. The words you type into the search box are sent to our server as part of the page address (for example /blog/search?q=…) and used to find matching posts. We do not save searches, but like any page address they may appear in our hosting provider’s logs.
Cookies and browser storage
- Language cookie (blog_locale). Set only when you pick a language with the EN · PT · ES switcher, so the Blog does not switch you back to your browser’s language later. It contains only the language code and expires after one year.
- Theme setting (blog-theme). When you use the light/dark theme button, your choice is saved in your browser’s local storage. It stays on your device and is not sent to us.
- No tracking. The Blog sets no analytics, advertising or tracking cookies. Its pages are configured to load scripts, fonts, images and other resources only from the Blog itself, so reading a post does not send your information to third parties. The Blog does not embed videos or posts from other sites.
When you use the admin panel (authors and editors)
- Account details. An administrator creates your account with your email address, name and a password. We store your password only in hashed form. Your account also records your role and whether it is active or revoked. There is no public sign-up, and the Blog sends no email.
- Public author profile. Your name, and the bio and photo you choose to add, are shown publicly with your posts, on your author page, in the Blog’s RSS feeds and in the structured data that search engines read. Your email address is not shown on the Blog.
- Content you create. The posts you write, including their drafts and earlier versions, and the images you upload, which are recorded as uploaded by you.
- Sign-in and security. Signing in sets a session cookie (payload-token) that lasts up to 7 days, and we keep a record of your active sessions and of failed sign-in attempts, which lock the account for 5 minutes after 5 failures. To slow down password guessing, the server also counts sign-in attempts per IP address in memory for 5 minutes.
- Audit log. Account changes (creating an account, changing a password, role or status, and deleting an account) are recorded with who made the change, the account affected and its email address, the time, and the IP address the request came from.
- Admin preferences. The admin panel may save interface preferences, such as theme, language and list settings, in cookies (payload-theme, payload-lng), in your browser’s local storage and in our database. Previewing a draft sets a draft-mode cookie (__prerender_bypass) in your browser.
2. How We Use Information
- To run the Blog. To deliver its pages, images, search results and feeds.
- To show the Blog in your language. To choose a language on your first visit and remember the language and theme you pick.
- To publish and attribute posts. To let authors and editors sign in, write and publish posts, and to credit authors by name.
- To keep the Blog secure. To protect accounts from password guessing, keep a record of account changes, investigate misuse and fix problems.
- To comply with the law. To meet legal obligations and respond to lawful requests.
We do not sell personal information, we do not use it for advertising, and we do not build profiles of readers.
Legal bases
- Legitimate interests. Where the law allows it, we process request information, language and security records because we have a legitimate interest in running a secure, multilingual blog, and we manage author and editor accounts because we need them to publish it. The language cookie and theme setting are used only to provide a feature you asked for.
- Legal obligations. We process information where we must do so to comply with the law or a lawful request from an authority.
- Other bases. Where your local law does not recognise legitimate interests, we rely on another basis that law permits.
3. How We Share Information
- Service providers. Railway hosts the Blog, its database and the storage bucket that holds uploaded images, and so processes the information described above on our behalf. If we route the Blog through a content delivery or security network, such as Cloudflare, that provider also processes requests to the Blog.
- Sites you choose to visit. The share buttons open WhatsApp, Telegram or X with the post’s title and link, and the follow links lead to our Discord and other social channels. Nothing is sent to those services until you click, and once you do, their own privacy policies apply. The same is true of other links on the Blog, such as P2P.me’s compliance pages and links inside posts. When you follow a link to another site, your browser tells that site only that you came from the Blog’s domain, not which page.
- The public. Author names, bios and photos, and published posts and images, are public.
- Legal and safety reasons. When required by law, court order or a lawful request from an authority, or when needed to protect the rights, property or safety of our readers, authors, the public or the Company.
- Business transfers. If the Blog is transferred to another organization, the information described here may be transferred with it.
4. Retention
- In your browser. The language cookie expires after one year, and the admin session cookie after at most 7 days. The theme setting stays in your browser until you clear it.
- Request information. Sign-in attempt counts are held in memory for 5 minutes. Request details in our hosting provider’s logs are kept for the period its service provides.
- Admin accounts. We keep account details while the account exists. A revoked account is kept, with its bylines, until it is deleted. When an account is deleted, its posts and images are reassigned to the administrator who deleted it. Audit log entries are kept as a security record and cannot be changed or deleted from the admin panel.
- Published content. Posts and images stay online until they are unpublished or deleted. Up to 50 earlier versions of each post are kept.
5. Your Choices and Rights
- Cookies and storage. You can block or delete cookies and local storage in your browser settings. The Blog still works; it will simply not remember your language or theme.
- Your author profile. Authors can change their own name, bio, photo and password in the admin panel. An administrator can change your email address or delete your account.
- Access, correction and deletion. You can ask for a copy of the personal information we hold about you, or ask us to correct, update, delete or transfer it, or to restrict or stop using it, by writing to compliance@p2p.me.
Depending on where you live, you may have additional rights under local data protection law, such as Brazil’s LGPD, the data protection laws of Argentina, Colombia, Peru and other countries, India’s Digital Personal Data Protection Act 2023, or the GDPR in the European Economic Area and the United Kingdom. We will respond within the time that law requires. If you are not satisfied with our response, you can complain to your data protection authority, such as Brazil’s ANPD, Argentina’s AAIP, Colombia’s Superintendencia de Industria y Comercio, Peru’s Autoridad Nacional de Protección de Datos Personales, the Data Protection Board of India, or the supervisory authority where you live in the European Economic Area or the United Kingdom.
6. Security
The Blog is served over encrypted connections (HTTPS). Passwords are stored only in hashed form, sign-in attempts are limited, account changes are logged, and uploaded images are kept in a private storage bucket and served through the Blog itself. No method of transmission or storage is completely secure, so we cannot guarantee absolute security.
7. Children
The Blog is a general-audience publication and is not directed at children. Reading it does not require giving us any personal information, and admin accounts are only for members of the team that runs the Blog. We do not knowingly collect personal information from children. If you believe a child has given us personal information, contact us and we will delete it.
8. International Transfers
Our hosting provider may store and process the Blog’s data in a country other than the one you live in, whose data protection laws may differ from yours. Where your local law requires safeguards for transfers abroad, we take the steps it requires. You can ask us for details at the address below.
9. Changes to This Policy
We may update this Privacy Policy from time to time, for example if the Blog starts collecting new information. When we do, we will update the date at the top of this page, and we will announce material changes on the Blog.
10. Contact Us
Questions, requests and complaints about this Privacy Policy or your personal information should be sent to compliance@p2p.me.