How Novalify handles property documents and personal data
Where property documents are stored, who can open them, and how access to inquiries, meetings and internal notes is separated by role.
Novalify OÜ
Documents are private by default
Property documents uploaded to Novalify are stored in a private bucket. They are not served from a public URL — access is granted per request, for the people entitled to see that document, and links expire.
Access follows roles, not convenience
The platform separates what different people can see:
- Clients see their own inquiries, their own meeting requests, and the documents shared with them.
- Team members see the workspace records assigned to them, including coordination details.
- Internal coordination notes and staff assignment live in a separate team-only area, so an internal remark is never exposed on a client-facing record.
- Administrators additionally see audit history: who changed a booking or a lead, and when.
These rules are enforced in the database itself, not only in the interface — so a request that bypasses the UI is refused the same way.
Meetings and rate limits
Meeting requests require a signed-in account, are limited per hour, and duplicate submissions within a short window are rejected. This keeps the coordination queue usable and reduces spam against public forms.
Audit trail
Booking and lead changes are written to an append-only audit log: actor, action, record and timestamp. Administrators can review it; nobody can quietly edit it.
Your data
Read the Privacy Policy for what is collected and why, the Terms for platform rules, and the Disclaimer for the limits of the information published on this site.