What we do with your data.
Artrelo handles tenant contact details, property records, vendor relationships and money. This page describes how each of those is protected — and, at the bottom, what we deliberately do not claim yet.
Accounts and sessions
- Passwords are hashed with bcrypt at cost 12. We never store them in a readable form and cannot recover one for you.
- Sessions use HTTP-only cookies, so page scripts cannot read your session token. They are marked Secure in production and restricted to our own site with SameSite=strict.
- Access tokens are short-lived and refreshed separately, and the refresh cookie is scoped to the single endpoint that consumes it.
Access control and isolation
- Every account carries a role — landlord, tenant or vendor — and each endpoint checks it before doing any work.
- Handlers scope their queries to the authenticated account rather than filtering afterwards, so one operator cannot read another operator’s portfolio.
- A vendor sees only the job they were offered. A tenant sees only their own requests, and never what the work costs.
Vendor access without accounts
- Vendors work from a private link to a single job. There is no vendor account and no shared password to leak.
- Those links carry 256 bits of randomness and are stored only as a SHA-256 hash. The raw value is never written to the database and never written to a log.
- A link stops working when its job closes.
Tenant privacy
- Vendors never receive a tenant’s phone number or email. Before accepting a job they see only the issue, photos and city; after accepting, the address, access details and the tenant’s first name and last initial.
- Tenants are never shown what a repair costs, and vendors are never shown your budget for it.
- Photos and videos submitted with a request are stored with our media provider and attached to that request only.
Payments
- Stripe holds the money and handles vendor identity verification. We store a reference to the Stripe account and nothing else.
- No card number and no vendor bank detail is ever stored in our database.
- Payment webhooks are verified against the raw request body before they are trusted, so a forged callback cannot move money.
Infrastructure
- Traffic is served over HTTPS. The database is hosted on MongoDB Atlas, which encrypts data at rest.
- Standard HTTP hardening headers are applied to every response, and cross-origin access is limited to an allowlist rather than left open.
- Public endpoints — the contact form, the vendor portal, and tenant request intake — are rate limited per IP and in aggregate.
Who else processes your data
Artrelo is built on services that each handle one part of the job. These are all of them.
- MongoDB Atlas
- Application database
- Stripe
- Vendor payouts and payment custody
- OpenAI
- Request triage and categorisation
- Cloudinary
- Photo and video storage
- Resend
- Transactional email
- Twilio
- Automated emergency phone calls to property managers
- Sentry
- Error reports, scrubbed of request contents and contact details
- Railway
- Application hosting
What we don’t claim yet
Artrelo is an early-stage company. Plenty of vendors imply certifications they do not hold, so here is the list of things we have not done. If one of these is a requirement for you, tell us and we will give you a straight answer about timing rather than a vague one.
- —SOC 2 or ISO 27001 certification
- —A formal GDPR or PIPEDA compliance programme
- —Guaranteed data residency in a particular country
- —A third-party penetration test
- —A contractual uptime SLA
Security questions, or a vulnerability to report? Email [email protected]. See also our privacy policy.
Bring us your hardest questions.
We would rather answer them on a call than have you guess from a page. Book a demo and ask.