The inbox is read by a person who replies.
Fdo. has no contact form, no chatbot, no support queue. Just an email that the person maintaining the project reads. This page sums up how to write so the reply is useful.
hola@fdo.app — for anything general: questions, suggestions, use cases, integrations.
seguridad@fdo.app — for security reports. More detail on the security page and in the security.txt.
Response time
- Business day
- Same day. If you write in the morning, usually before the afternoon.
- Weekends and holidays
- The next business day.
- August
- Up to 5 days. It's Spain, August is August.
- Security reports
- Acknowledgement within 24h, also on weekends.
What to put in the email
Replies come faster and more useful if the email makes clear:
- What for: professional (firm, office, HR) or personal.
- What's happening or what you want: if it's a bug, the steps to reproduce and the browser. If a suggestion, the real case behind it.
- Approximate volume: how many PDFs, how often. Helps to prioritise.
No template needed — a plain email works. The only ask: don't send real PDFs with personal data as attachments. If a specific PDF is the problem, send a sanitised one with made-up data.
Languages
Spanish, Catalan, English. If you write in another language, you'll get a reply — but in one of these three after going through a translator.
What doesn't get a reply
- SEO pitches, link-building, marketing agencies.
- Offers to "scale the business" with investment.
- Outsourcing spam.
Not out of unfriendliness — they just don't apply: Fdo. is a small, self-managed project not chasing aggressive growth.
Postal address
If you need the operator's postal address for a formal procedure (data processing agreement, GDPR, etc.), ask for it by email and you'll get it in the reply. It is not published openly to avoid physical-mail spam.