Use cases / Companies processing Russian citizens personal data
Email with Russian data residency (152-FZ)
Broadcasts and transactional email with data stored in Russia — no Cloudflare, no US transit
Western email providers store personal data in the US and reject Russian cards. Sendersy runs on servers in Russia and the EU: contact lists and email logs stay in-region, payment works with RU cards and SBP.
Pain points
- 1.Russian 152-FZ law requires storing citizens personal data on servers in Russia — SendGrid, Mailchimp and Resend cannot offer that.
- 2.Paying for western services with a Russian card is impossible.
- 3.Sanction risk: a western provider can suspend the account overnight.
How Sendersy solves it
- Servers and databases in Russia (Moscow) + EU replica (Estonia).
- Payment with Russian cards or SBP (UnitPay), accounting documents for legal entities.
- Self-hosted infrastructure: own SMTP (Postal), no Cloudflare, no US proxies.
What the integration looks like
sh
# Отправка письма — данные не покидают РФ/ЕС
curl -X POST https://api.sendersy.com/v1/emails \
-H "Authorization: Bearer sk_live_..." \
-H "Content-Type: application/json" \
-d '{
"from": "Магазин <noreply@shop.ru>",
"to": "client@example.ru",
"subject": "Ваш заказ подтверждён",
"html": "<p>Спасибо за заказ!</p>"
}'Frequently asked
Where are the servers physically located?
Primary infrastructure is in Russia (Moscow), inbound mail and replicas in the EU (Estonia). No Cloudflare or US CDNs are used at all.
Do you provide documents for 152-FZ compliance?
Yes — agreement and data-location description are available on request at support@sendersy.com.
Do you accept payments from legal entities?
Yes: card, SBP, and invoices for legal entities with accounting documents.