Data policy
PrivacyPolicy
How Rent A Farm collects, stores, uses, and safeguards personal information submitted through this pre-launch website.

- Legal operator: to be confirmed before launch
- Privacy officer: to be confirmed before launch
- Designated privacy email: to be confirmed before launch
1. Scope and purpose
This Privacy Policy explains how Rent A Farm collects, stores, uses, and safeguards personal information provided by individuals who browse this website, submit household growing space applications, or submit landowner partnership inquiries.
This website does not accept payments, process credit cards, or execute commercial contracts. Any future customer subscription contracts, billing agreements, or commercial land leases will be governed by dedicated commercial agreements and separate operational privacy schedules.
2. Information we collect
We collect personal information directly when you voluntarily complete our application forms:
- Household applicants: full name, email address, optional telephone number, preferred contact method, city, postal code, province or region, requested growing area preferences, seasonal crop interests, and optional budgeting ranges. We do not request complete street delivery addresses at this initial interest stage.
- Landowner applicants: full name, email address, property municipality, approximate available acreage and units, relationship to property (owner or representative), and optional parcel characteristics (zoning, ALR status, water availability, electrical service, terrain, and heating infrastructure).
- Track and inquiries: reference identifier and email address used to view submission status or withdraw your interest.
- Contact messages: name, email address, subject, and message content submitted through the contact form. These messages are stored in our private database only and are not copied to the application sheet.
- Account messages and support: once you have a verified account, our dashboard can show notices about your applications and direct messages an operator sends you, and you can open a support conversation. We store the message text, the sender and recipient, the time, and when each message was read. Support conversations are plain text; file attachments are not supported. Direct messages to a group of applicants are stored as a separate row per recipient so that each account only sees and manages its own.
- Saved shortlist: the crops you select are saved to your account so the list follows you between devices. Signing out or deleting your account clears the account copy.
- Administrator access records: when an authorized operator uses our internal admin panel, we record the operator, the action taken, the record affected, the time, and a keyed hash of the network address. We do not store the raw network address in this audit trail.
3. How information is used
We process your information strictly for the following purposes:
- Evaluating geographic demand clusters to plan regional greenhouse locations.
- Conducting initial agronomic and logistical feasibility reviews.
- Contacting qualified applicants to discuss pilot growing opportunities or arrange private land evaluations.
- Maintaining immutable compliance and consent audit records.
- Administering applications through an internal panel under our legitimate interest in operating the service and keeping a security audit trail.
4. Marketing consent and CASL compliance
In accordance with Canada's Anti-Spam Legislation (CASL) and provincial applicable privacy legislation:
- Marketing communications opt-in is presented as a separate, optional, unchecked checkbox.
- Refusing marketing consent does not prevent or impair your application submission in any way.
- We record the precise timestamp, consent status, and wording version of your consent choice.
- You may withdraw your application at any time using our Track Application portal. To withdraw marketing consent separately, contact us through the contact form. Withdrawing an application is not the same as deleting its records.
5. Data retention and security
Applications, contact messages, and consent histories are stored in Hostinger MySQL. Our server accesses the database; browsers cannot connect directly. Public form traffic uses HTTPS. Form submissions are not sent by email; the database record is the operational copy. We use Google Sheets for a private operational copy of household and landowner applications, and Cloudflare Turnstile to help prevent automated abuse. Contact messages are not copied to the application sheet. These providers may process information outside Canada under their own service terms.
We retain application records, contact messages, consent histories, and the private sheet copy until an authorized operator deletes them. There is currently no automatic application-expiry job. Account confirmation, password reset, password-change and login-code emails are sent through our SMTP mail provider. Unsent security email bodies are encrypted in the retry queue and blanked after sending or expiry; email providers and mailboxes can retain their own copies. Rate-limit counters contain keyed hashes rather than raw IP addresses and are removed by the worker after 24 hours. Turnstile receives a verification token and client IP address for abuse prevention.
Signed-in applicants can remove a withdrawn or closed application from their dashboard. That only hides the card: the application record, consent history and private sheet copy are kept, and an authorized operator can still delete them as described above.
A verified account is required to submit either application. We store a password hash, verification state and session records, including device labels, last activity and a keyed hash of the IP address. Essential Secure, SameSite cookies keep you signed in and protect requests. Remember this device uses a cookie lasting up to 30 days; otherwise it is a browser-session cookie with a server-side maximum of 24 hours. You can review and revoke devices on the account security page. Browsers may restore session cookies after restart.
Form drafts are saved in this browser using a limited field list, never passwords or verification tokens, and cleared on successful submission, sign-out or account deletion. Account deletion requires your password and removes the account, sessions, tokens, codes and shortlist. Application and consent records remain as business records without an account link. Request separate erasure of retained applications and the private Sheet copy through our contact form, subject to legal obligations and backup retention.
Status lookups require both a random reference and the applicant email. Application API responses are marked no-store. Operational logs are designed not to contain form contents. These safeguards reduce risk but cannot guarantee absolute security. Deletion requests must also be applied to the private sheet and relevant email copies, subject to legal recordkeeping obligations and backup retention controlled by the hosting provider.
Account notices, direct messages and support conversations are stored in the same private MySQL database. Each account can read and delete only its own copy, and one user cannot see another user's threads. Message length is capped and sending is rate limited. Status changes create an in-dashboard notice by default and do not send email. Deleting your account removes its inbox messages, its support thread and messages, and its saved shortlist.
The internal admin panel is limited to accounts that an operator has explicitly granted the administrator role. Signing in requires the account password plus a time-based one-time code; an elevated administrator session lasts at most eight hours and the account role is re-checked from the database on every request. The panel masks applicant email addresses and phone numbers by default. An operator must re-enter their password to reveal those details, and every reveal is written to the audit trail. Audit entries are append-only: the application has no code path that updates or deletes them, and the database rejects such changes. We retain the audit trail for as long as needed to investigate security events and meet legal obligations, after which an operator may remove older entries at the database level. The audit trail contains no application message contents and no raw IP address.
6. Access, correction, and deletion rights
Under Canadian privacy law, you have the right to request access to the personal data we hold about you, request corrections to inaccurate records, or request complete deletion of your application file.
To exercise these rights, submit your request through our contact form or email our designated privacy contact.