Effective October 10, 2026 · 2026-10-10-privacy-1
Privacy Policy
Quick explanation
PropertyWatch helps homeowners and tenants organize properties, rent records and property conversations. When an authorized homeowner separately connects a rent Gmail inbox, the rent-email feature processes supported transfer notifications to help identify payments. Google sign-in alone does not connect an inbox.
We do not move rent money, collect banking passwords, sell personal information, use Gmail data for advertising, or use it to train general-purpose AI models. Connected inbox access is read-only, but Google’s permission is broader than just rent emails. Our software applies payment-candidate checks within that permission. Necessary providers operate parts of the service, and some information is processed outside Canada.
Account deletion, removing a tenant, disconnecting Gmail and signing out are different actions. Some rent information can remain for a continuing homeowner’s justified recordkeeping; that information is still personal information. The detailed rules and current limitations appear below.
1. Who operates PropertyWatch and what this policy covers
PropertyWatch is operated by Azeem Rana, referred to here as “PropertyWatch,” “we,” “us” or “our.” Azeem is responsible for the privacy contact above. The operator is not the homeowner or property manager using the service, and this policy does not describe PropertyWatch as an incorporated company.
This policy covers personal information processed through the PropertyWatch app, its backend, propertywatchapp.com, account communications and support interactions. It covers people using an account and people whose information an authorized user supplies, such as an invited tenant or a person named in a payment notification.
The initial launch is planned for Canada. Federal and provincial privacy requirements can apply differently depending on the activity and location. This policy does not assume that one rule applies to every Canadian request, or that it authorizes a worldwide launch. It does not remove any applicable privacy, consumer or tenancy right.
Google, Apple, banks, email providers, app stores and other third parties also operate their own services. Their policies govern their independent processing. Their involvement does not remove our responsibility for the information we process.
2. Current development status and feature availability
PropertyWatch currently uses controlled testing, not open public registration. The separate production backend and account-email delivery are configured, and production Google login and initial Gmail connection have been checked. Public Gmail verification has not been completed.
At this policy’s publication, production payment-email intake, automatic app-event push delivery, permanent account-deletion execution and scheduled retention/disposal execution remain gated off. Their implementation and tests are not the same as live availability. A connected Gmail inbox or a successful initial synchronization does not mean production rent detection has been activated.
Controlled rehearsal availability update — October 11, 2026: Payment-email intake remains disabled by default. With the participating homeowner’s authorization, we may temporarily enable a supervised Gmail rehearsal for one expressly selected inbox. The ordinary rehearsal admits only new payment-candidate messages received during a bounded test window. Alternatively, the homeowner may expressly select one existing email for an exact-message rehearsal; this does not search or import a historical inbox or admit other messages. Other inboxes are excluded in both modes. The window expires automatically after at most 24 hours. Bank-email authenticity checks still apply, and first-name automatic recording remains off: the homeowner reviews and assigns any supported detected payment. A pending transfer is not treated as a deposited payment. This limited test is not public availability, Google approval or proof that a payment was deposited. It does not enable the other gated features above. The Gmail access, storage, sharing, disconnect and retention disclosures below also apply to this rehearsal.
When a feature described below is disabled, we must explain that limitation instead of displaying a false completion or claiming its cleanup schedule is running. Final production activation and this policy’s effective version must be aligned before public use. For a privacy or deletion request while self-service execution is unavailable, contact the privacy email; do not assume that signing out deletes your account.
Demo mode is distinct from a connected account. It uses sample information and is not evidence that a demo action created a cloud account, sent a message or changed a real rent record.
3. Information we collect and where it comes from
We collect information you provide, information authorized participants provide about their shared property or tenancy, information obtained from separately permitted integrations, and technical information needed to operate the service.
Category: Account and identity
Examples and source: Email, name, account identifiers, verification and sign-in information; supplied by you or your selected identity provider
Main purpose: Authenticate you, protect accounts and display the correct identity
Category: Property and portfolio
Examples and source: Property address/name/type, units or rooms, capacity and ownership/membership records; supplied by authorized homeowners/managers
Main purpose: Organize properties and control shared access
Category: Tenant and invitation
Examples and source: Tenant name/contact, assignment, invitation token, invitation status, rent schedule and dates; supplied by authorized users or the invited person
Main purpose: Join the intended property and maintain tenancy records
Category: Rent and payment
Examples and source: Amounts, dates, rent changes, credits, arrears, recorded payments and review decisions
Main purpose: Present rent history and reconcile records
Category: Conversations
Examples and source: Messages, reactions, conversation participation and read information
Main purpose: Provide authorized property communication
Category: Property-cover photos
Examples and source: Optional uploaded image, object identifiers and cover associations
Main purpose: Display the same property photo in authorized home/property/message views
Category: Connected Gmail
Examples and source: Selected inbox identity, provider identifiers, encrypted authorization tokens, scope, watch/history state and connection status
Main purpose: Maintain the separately authorized rent-email connection
Category: Payment-email evidence
Examples and source: Candidate email information and derived transfer fields described in section 7
Main purpose: Detect, verify, deduplicate and reconcile supported notifications
Category: Device and notification
Examples and source: Push token, random installation identifier, platform, timezone, preferences and delivery state
Main purpose: Deliver eligible alerts to the correct account and device
Category: Security and operations
Examples and source: Request/error status, audit identifiers, authentication events, rate-limit and job records
Main purpose: Protect access, diagnose failures and operate the backend
Category: Privacy/support requests
Examples and source: The request you send, relevant correspondence, verification outcome and response record
Main purpose: Answer your request, investigate an issue and document the outcome
Category: Website requests
Examples and source: Request information processed by hosting infrastructure, potentially including IP address and browser/security details
Main purpose: Serve and protect the public website
Some information is personal even when it does not contain a name. A property identifier, account-linked digest, payment history, small-portfolio total or device token can still relate to a person. We do not describe these records as anonymous merely because we removed an obvious identifier.
We do not ask for a banking password, payment-card number, Social Insurance Number, passport, precise device-location permission or a copy of a lease to make Gmail scanning work. Do not place unnecessary identity documents or unrelated sensitive information in a property chat or support message. This is not a guarantee that a user-supplied message or photo cannot contain such information.
4. Why we use information
We use information to create and secure accounts; maintain authorized portfolios and assignments; show rent schedules, paid amounts and outstanding records; support property conversations and optional photos; operate the permitted rent-email feature; send account verification/reset communications and eligible alerts; prevent duplication, unauthorized access and abuse; investigate user-reported errors; answer privacy requests; and meet applicable legal requirements.
Payment matching is a property-recordkeeping feature, not a credit score, tenant-screening decision, lending decision, legal finding of debt or eviction decision. PropertyWatch does not decide who is entitled to housing. Homeowners must verify records and comply with their separate obligations before acting on them.
We do not treat creating an account, accepting service terms or requesting support as blanket permission for unrelated uses. A new use that requires consent must be disclosed and authorized before we begin it.
5. Account login is separate from Gmail permission
You may use an implemented account sign-in method such as Google, Apple or email authentication. Google identity login can supply your verified account email and profile name; Apple may supply a private relay email. Those identity choices do not authorize us to read Gmail.
An authorized homeowner must separately select and consent to the Gmail inbox that receives the relevant rent transfer notices. The login email and rent inbox can be different. Tenants do not need to grant rent-inbox access simply to participate as tenants. An invitation or portfolio membership does not grant access to another person’s Google account.
Account-email verification and password-reset messages are also separate from Gmail reading. We use our sending provider for those account messages; we do not send them through your connected rent inbox.
6. What Gmail access means and how consent works
The rent-email integration requests https://www.googleapis.com/auth/gmail.readonly. That permission can let the application read Gmail messages and associated information across the account. Google does not limit this permission to rent emails. Our code limits its processing through inbox-change and payment-candidate checks, but those checks are not a narrower permission enforced by Google.
We request access to support the visible rent-notification detection and reconciliation feature. Message bodies are needed to distinguish transfer states and derive payment fields; metadata-only access would not provide those details. This integration does not request Gmail sending, editing, deleting or settings-management permission, and it cannot move money.
The app explains this purpose immediately before the separate Google consent request. A privacy-policy link alone is not the in-app disclosure. Consent requires an affirmative action in Google’s flow. Returning to the app, pressing Back, cancelling, signing in or accepting ordinary terms is not Gmail consent. An incomplete permission attempt returns to the connection step rather than silently granting access.
You can decline. That prevents the Gmail feature from operating and, where a usable portfolio rent connection is required by the current homeowner onboarding, may prevent completion of that setup. We do not claim there is a manual-tracking bypass that is not actually offered. Do not connect an inbox you are not entitled to authorize, including a work inbox contrary to your organization’s rules.
Google or a Google Workspace administrator may restrict access, require reconnection or revoke authorization. We cannot remove Google’s warnings or promise that an integration will always be available.
7. How rent-email processing works
When enabled, the backend follows changes in the connected inbox using Gmail message/history identifiers and mailbox-watch notifications. It first retrieves candidate metadata, including sender and subject, to decide whether a message may be a supported transfer notification. This first pass can encounter metadata for unrelated inbox messages.
For a candidate, the code can fetch the original raw email, subject to a size bound, to verify authenticity and parse the same content that was verified. Raw email includes headers and encoded message parts and may include incidental attachment content. The parser ignores attachment parts when extracting the supported text. The application is not an attachment browser, does not request separate attachment retrieval for this feature, and does not intentionally save attachments as property files. We therefore do not claim it never receives attachment bytes.
The supported authenticity checks examine message signatures and framing before trusting payment content. A message being in Gmail or having a familiar display name is not enough. Unsupported or malformed candidate messages may yield a failure/unsupported result instead of a rent entry. An authenticity check is not independent confirmation from the bank that money has cleared.
The code processes raw candidate content transiently. The payment-source table does not store the full raw email or raw message body. Messages classified as ignored return before insertion into that table. Candidate failures can still create limited diagnostic/source metadata and a digest; “ignored” is not the same as “unsupported candidate.” We must not put raw emails, tokens or unnecessary financial details into general logs or support tickets.
Stored derived evidence can include provider message/history identifiers, event/parser version and outcome, sender/payer name or matching identifier, amount, currency, transfer reference, received/deposit date or status, content/signature digests and bounded authenticity results. These fields remain personal or Google-derived information where they relate to people.
Where enabled, matching considers the authorized portfolio’s tenant/payment records and configured matching rules. Ambiguous identities, conflicts and pending/unsupported states require review rather than guessed attribution. A name match alone does not establish a legal payment obligation. Corrections must preserve accurate audit and financial history, not rewrite original bank evidence to hide an error.
One supported, separately enabled option is unique-first-name auto-recording for verified completed deposits. It requires exactly one eligible active tenant with the matching first name and the other database safeguards to pass; duplicate names or conflicting remembered payer information must not become a guessed payment. This is not a promise that every notification includes a usable surname or that the app always identifies a person from their full legal name. The review interface and independent bank checks remain important.
Synchronization can run on our backend when the app is not open. Recovery after a lost history cursor can request supported inbox candidates within the code’s recovery window; it is not described as an unlimited historical mailbox import. Production activation of recovery/intake remains subject to section 2.
8. Google information: restricted purposes and access
PropertyWatch’s handling of information received through Google APIs, including information derived from it, will follow the Google API Services User Data Policy (https://developers.google.com/terms/api-services-user-data-policy), including its Limited Use requirements, and the applicable Google Workspace data policy (https://developers.google.com/workspace/workspace-api-user-data-developer-policy).
Google-derived information is used for the disclosed rent feature and its permitted operational, security and legal needs. With the inbox authorizer’s consent to the disclosed shared feature, derived rent/payment information is presented to the appropriate authorized portfolio participants described in section 9, not to every app user. We do not sell it, provide it to advertising/data-broker businesses, use it for advertising, assess creditworthiness or lending eligibility with it, or train general-purpose AI/ML models with it. The scanner uses supported parsing and verification rules; it does not send rent-email bodies to an AI model for interpretation.
Transfers are limited to the permitted feature with consent, necessary security work, legal requirements, or an ownership transaction with the required prior explicit consent. Human access to restricted data is limited to specific user-authorized assistance, necessary security work, legal requirements, or genuinely aggregated and anonymized internal information. Ordinary support permission is not permission to browse an inbox. These restrictions also bind people or contractors acting for us. Portfolio-linked totals are not automatically eligible for an anonymized-data exception.
This statement is our policy commitment, not a claim that Google has approved the app. A policy cannot replace required security practices, consent or verification.
9. Who can see property, rent and conversation information
Authorized homeowners and appropriately authorized managers can access the portfolio information needed for their role. A co-homeowner invitation grants shared portfolio access, not ownership of the physical property, bank access or permission to read the connected Gmail account independently of PropertyWatch.
Tenants receive their applicable assignment/rent information and conversations they are authorized to join. They do not receive a homeowner’s Gmail authorization tokens or a general mailbox viewer. Joining a property does not grant access to unrelated portfolios. Owners should invite only people entitled to the shared information and should explain information they supply about tenants who do not yet have accounts.
Conversations are available to authorized participants. The service is not represented as end-to-end encrypted such that only participants possess the decryption keys: the backend processes information to provide the feature, subject to access controls and the restrictions in this policy.
Participants may already have read, copied or screenshotted information, or received it in an alert. Editing, unsending, leaving a property or deleting an account cannot erase independent copies on someone else’s device or outside our service. This does not permit us to keep unnecessary server copies indefinitely.
10. Optional property photos and device permissions
Property-cover photos are optional. Owners and specifically authorized photo managers can add/replace a cover; tenants and read-only participants cannot upload covers. The same stored cover may appear in the property card, home overview and property-conversation image for authorized users.
The app asks for relevant camera/photo permission when you choose a source. Permission denial must be handled clearly; a property can exist without a photo. We receive the image you submit, not an unrestricted upload of your whole photo library.
Covers use private Storage and temporary display links, not a publicly browsable photo bucket. Existing links or cached images can remain usable until their expiry or cache removal; a membership change is not a promise that every previously issued link disappears instantly. A valid recipient can still keep a copy.
Do not upload images you lack permission to use, confidential documents, visible account numbers or unnecessary identifying images of tenants. Photos can contain identifying scenery or metadata. We do not promise that every image’s location/EXIF metadata is stripped unless that has been verified for the actual upload path.
11. Notifications, device sessions and local information
When permitted and enabled, we use the device’s push token, installation identifier, platform, timezone and preferences for eligible message, payment and rent-reminder alerts. Notification delivery providers process the payload needed to deliver an alert. An alert can reveal information to someone viewing your lock screen; manage previews and permissions in your phone settings.
Disabling a phone permission or app alert preference is not account deletion. Delivery may be delayed, suppressed or fail. The service should not be used as an emergency channel or the sole legally required notice method.
If you choose to remember a native account session, the app stores session information through the device’s secure storage. Otherwise session handling uses memory for that purpose. Non-secret preferences/install markers can use ordinary local storage. Secure storage is not protection against every compromised/unlocked device. App/operating-system caches and user-created screenshots can have their own lifecycle.
Signing out clears the applicable session and attempts to unregister the device through the implemented flow; it does not erase the cloud portfolio or financial history. Authentication providers and phone operating systems also control their own sessions and storage.
12. Necessary service providers and overseas processing
Provider/service: Supabase
Role in PropertyWatch: Authentication, database, private photo storage and server functions
Data involved: Account, portfolio, rent, chat, photo and integration/operation records
Provider/service: Google
Role in PropertyWatch: Identity login, separate Gmail permission and synchronization infrastructure
Data involved: Identity data, permitted mailbox data, OAuth/watch/history information
Provider/service: Apple
Role in PropertyWatch: Native identity and iPhone/app distribution and notification services
Data involved: Identity/relay information and applicable platform/delivery data
Provider/service: Expo and device push services
Role in PropertyWatch: App delivery infrastructure and eligible push transport
Data involved: Build/platform information, device tokens and notification payloads
Provider/service: Resend
Role in PropertyWatch: PropertyWatch verification and password-reset email delivery
Data involved: Recipient addresses, temporary-code message content and delivery records
Provider/service: Vercel
Role in PropertyWatch: Public informational website hosting
Data involved: Website requests and applicable security/hosting metadata
Providers may use subprocessors under their own arrangements. Listing a provider is not a claim that all of its features or subprocessors receive every category of PropertyWatch data. For example, rent-email content is not routed through Resend by the account-email integration, and account messages are not sent through your Gmail mailbox.
The production database is configured in Supabase’s Canadian region. That is not a guarantee that identity, email, notification, support, hosting or provider operational records remain in Canada. Resend describes customer-data storage in the United States; selecting its sending region does not make all of its storage Canadian. Overseas courts or authorities may have lawful access under their own rules.
We remain responsible for appropriate provider use and must review protections, processing purposes and relevant changes. We do not transfer Google-derived information under broader permissions than section 8 allows. Providers’ independent account/billing records may be governed by separate policies.
13. Account communications and support
Verification and password-reset emails serve account security, not marketing. They can contain temporary codes. Never send a code, password or API key to support. Resend has no rent-inbox permission through this sending integration.
If you contact support, we process the information you choose to send and the limited related records needed to answer. For Gmail-related support, we obtain specific authorization before examining restricted data unless a permitted security/legal exception applies. We should use sanitized examples where possible rather than request an entire inbox export.
We keep appropriate case/outcome records to manage requests and demonstrate their handling. Information about other people must be separated or redacted where appropriate. A request is not permission to publish your information or provide it to an unrelated AI service.
14. Disconnecting Gmail and withdrawing permissions
Use the app’s rent-email connection controls to request disconnection. This stops the relevant local integration and removes its usable local credentials through the disconnection workflow. Provider cleanup may require retry if Google/network access fails. We must distinguish local disconnection, pending revocation and confirmed revocation instead of saying every provider action succeeded from a button press alone.
A Google grant can support more than one continuing authorized connection. We do not revoke another valid shared dependency indiscriminately. Account deletion/disconnection handles the departing connector and the remaining owners separately. You can also revoke PropertyWatch access through your Google Account connections (https://myaccount.google.com/connections); that may interrupt every connection relying on that grant.
Disconnecting stops future authorized scanning for that connection; it does not delete emails from Gmail, erase every previously derived financial record or delete your PropertyWatch account. Previously obtained records remain subject to the purpose/retention rules below and to your applicable rights. Contact us if you want information deleted in addition to ending access.
15. Removing a tenant, leaving a portfolio and deleting an account
Removing a tenancy: A homeowner’s removal ends the app assignment/access as implemented. It does not delete that person’s independent login or erase prior rent/payment history. It does not itself end a legal lease or authorize eviction.
Leaving shared ownership: A departing homeowner loses their portfolio access; continuing homeowners retain their own authorized portfolio. Another homeowner cannot treat a co-owner’s presence as permission to delete the co-owner’s independent account. The app’s shared-access rules are not a physical-property ownership decision.
Permanent account deletion: The designed self-service flow is Profile → Delete account, followed by confirmation and appropriate recent authentication. It is not currently enabled for production execution. While that limitation exists, use the privacy contact to request assistance. The service must not claim a request is completed merely because a session ended, a timeout occurred or an account no longer appears in the UI.
When the reviewed deletion workflow is enabled, it is designed to remove the departing account’s login/profile and device access, remove their authored messages/reactions/uploads, handle their relevant provider grants, and retain only justified continuing records. Authored property photos can be removed even from a continuing shared portfolio; another owner’s independent content remains. Deletion does not erase the same words in somebody else’s independently authored message or a recipient’s off-platform copy.
A tenant’s deleted account can remain identified in the homeowner’s financial/management views until assignment removal and the applicable retention/disposal stage. Their name, paid amounts and prior obligations may be retained; an “Account deleted” or “Former tenant” label is not anonymization. Unpaid displayed balances remain informational and can be disputed. Removing the assignment stops future app schedule contribution as implemented but does not rewrite earlier months.
A sole homeowner’s portfolio closure removes that portfolio’s properties, covers and shared access through the approved workflow, including associated financial aggregates/replay markers. Tenants’ access to it ends, but their independent accounts are not globally deleted. A portfolio with another continuing homeowner is preserved rather than silently closed.
Unresolved provider revocation, dependencies or interrupted cleanup must be reported as pending/blocked, with a support route—not false success. Apple grant handling may require instructions to remove the app’s authorization through Apple where automatic revocation cannot be completed. Existing privacy requests, legal restrictions and narrowly documented holds must be considered without imposing an arbitrary perpetual account-retention rule.
16. How long we keep information
We keep information for the disclosed purpose and applicable obligations, not simply because storage is available. Exact removal depends on the record category, active relationships, justified holds, provider lifecycle and the enabled cleanup process.
Record category: Active account/profile and usable integration credentials
Selected rule or retention criterion: Needed while the applicable account/connection remains active; subject to deletion/disconnection
Important limit: Pending provider cleanup is not permission to continue ordinary access
Record category: Property/assignment, conversations and covers
Selected rule or retention criterion: Needed for the authorized active feature; affected by content removal, account deletion or portfolio closure
Important limit: Other participants’ records and independent copies are distinct
Record category: Identifiable rent details and linked payment evidence
Selected rule or retention criterion: Canada-first product baseline: six full years after the latest relevant tax year, with justified longer need for active tenancy/dispute/request/legal obligation
Important limit: Not a universal legal minimum for every datum; production disposal is not enabled
Record category: Unlinked or unsupported payment candidates
Selected rule or retention criterion: Limited review/diagnosis purpose; their separate bounded disposal rule still needs finalization
Important limit: Do not automatically apply linked-tenancy financial retention or keep them forever
Record category: Older financial trend totals
Selected rule or retention criterion: Portfolio/month contributions may remain after eligible individual details are removed
Important limit: Portfolio-linked totals are not guaranteed anonymous; sole-owner closure removes the portfolio
Record category: Minimal financial replay/restore markers
Selected rule or retention criterion: Needed while the portfolio can process old payment emails or be restored safely
Important limit: Digests remain derived data; not original names/amounts/bodies; removed on applicable portfolio closure
Record category: Expired Gmail setup/OAuth state
Selected rule or retention criterion: Cleanup eligibility one day after original expiry
Important limit: Not the same as an active grant or unresolved revocation
Record category: Expired push bookkeeping
Selected rule or retention criterion: Cleanup eligibility 30 days after event expiry
Important limit: Not a 30-day rule for every payment or message
Record category: Completed deletion-job bookkeeping
Selected rule or retention criterion: Cleanup eligibility 30 days after durable completion and prerequisite checks
Important limit: Pending/blocked jobs do not qualify; minimal attribution/restore markers are separate
Record category: Resend account emails and logs
Selected rule or retention criterion: Provider currently states 30 days on Free; backups persist seven days
Important limit: Provider account termination/independent records have separate rules; not immediate erasure on app-account deletion
Record category: Support, privacy-request and security records
Selected rule or retention criterion: Necessary period for the case, applicable rights, investigation and legal obligation, with documented review/holds
Important limit: A general support case must not hold an entire portfolio indefinitely; final operational schedule still requires adoption
Record category: Operator backups and other provider logs
Selected rule or retention criterion: Service-specific and controlled recovery/expiry procedure
Important limit: No single provider’s retention period applies to all copies; final portable backup schedule is not yet adopted
The financial baseline uses the relevant record year, not six years from account signup or deletion. Later entry/reconciliation or a later applicable tax year can postpone eligibility. The current financial implementation supports a confirmed Canadian calendar-tax-year basis; another fiscal year or country is not silently treated as equivalent. Records with unclear dependencies or applicable holds are protected from premature disposal and require review. A product baseline alone is not a lawful reason to deny every deletion request: earlier removal or reduced identifying detail must be considered when applicable law or Google’s data rules require it. A homeowner’s preference to keep information is not, by itself, an unlimited retention exception.
Once eligible detailed records can be removed, monthly contributions are preserved without pretending an individual breakdown remains. Deduplication markers help prevent old messages or backups from recreating an erased payment and inflating totals. This is not permission to keep an unlimited full mailbox archive.
These are selected rules and safeguards, not promises that disabled production cleanup is already running. Bounded jobs can take additional time to complete an eligible backlog. Homeowners remain responsible for independent records appropriate to their own tax/tenancy duties; PropertyWatch is not their guaranteed complete tax archive.
Resend’s published processing and retention description (https://resend.com/security/gdpr) is a provider statement. Earlier message removal may require contacting it. We must distinguish provider assistance, deletion requests and verified completion.
17. Holds, backups and recovery
A hold must have a specific legitimate purpose and limited scope, such as an unresolved request, dispute or legally required investigation. It must be reviewed; an expired review date does not itself prove the hold is no longer justified. We should release a hold when its reason ends and not silently retain everything indefinitely.
Recovery copies can contain older records, credentials or state. Deleting live data does not necessarily erase every backup immediately. Before a restore reopens access, completed deletions, ended access and archived financial information must be reconciled so an old copy does not reactivate a deleted account or recreate erased details.
The current local recovery work includes protected development captures and source-code checkpoints. It is not a promise of a continuously updated, fully portable production backup. Database exports alone do not include every photo’s bytes. Final off-device custody, expiry and restore procedures remain prelaunch work, and no customer data should be placed in a public repository or an unprotected USB copy.
18. Security and incident response
Implemented protections include server-verified account/role access, private integration tables, encrypted OAuth credentials, private photo storage with temporary links, encrypted network connections, secure native session storage when used, constrained invitations, bounded operations and denial of unauthorized actors. These controls reduce risk but do not guarantee perfect security or independently establish certification.
Access is limited to the permitted purpose and appropriate role. Administrative access must not be used casually to inspect private information. Shared links, user copies, compromised accounts, lost devices and provider outages can create risks outside a simple database-permission check.
If an incident occurs, we investigate and preserve necessary evidence, contain the affected access, assess the impact, and provide legally required notifications. Where PIPEDA applies, a breach posing a real risk of significant harm requires regulator reporting and affected-person notification as soon as feasible; records of breaches must be kept for the applicable 24-month period from determination. Other applicable laws can add obligations. This policy is not permission to conceal an incident or delete evidence on an ordinary expiry timer. Contact the privacy email promptly if you suspect unauthorized access. Do not send secrets as proof.
19. Access, correction, deletion requests and complaints
Contact Azeem Rana at the privacy email to ask about information held about you, its sources/uses/recipients, obtain an appropriate copy, challenge an error, request deletion or withdraw optional permission. You can make a request even if you no longer have an active tenancy or never created an account but your information was supplied by someone else.
We use proportionate identity verification and limit disclosure to the verified person. Knowing a tenant’s name, address, payment amount or invitation code is not enough to obtain their private records. Do not send passwords, one-time codes or unnecessary government identification. A lost/deleted account needs a safe verification alternative, not automatic restoration from a name match.
We must respond within the applicable legal time requirements. Where PIPEDA governs an access request, the ordinary substantive-response period is 30 calendar days; permitted extensions require appropriate notice. Acknowledging receipt alone is not the final response. Different provincial requirements may apply.
Other people’s privacy, a lawful restriction or a justified recordkeeping obligation may limit a request. We should explain applicable reasons and provide the part that can properly be separated, rather than denying everything because one field cannot be disclosed. Factually inaccurate information should be corrected through the appropriate process, with an unresolved challenge recorded when necessary. Corrections are not permission to falsify bank/source evidence.
You can raise unresolved concerns with the Office of the Privacy Commissioner of Canada (https://www.priv.gc.ca/en/report-a-concern/) or the appropriate provincial privacy authority. This policy does not waive that right or impose mandatory arbitration for a privacy complaint.
20. Website, children and future changes
propertywatchapp.com currently provides information, this Privacy Policy and review Terms, not a public account-registration form. The current static site does not include an app-added advertising tracker, analytics script or chat-based sign-in form. Vercel can still process hosting/security request information; “no added tracker” does not mean no provider logging.
PropertyWatch is not designed as a children’s service. It has not established an age-verification or parental-consent program. It should not be advertised to children or treat this policy as parental permission to read a child’s Gmail. Contact us if information about a child may have been provided inappropriately. Any minors-related launch requirement needs a deliberate review; this policy does not invent an age-verification program.
Future Android availability, paid plans, new integrations, analytics, advertising, new countries or new data purposes are not authorized by broad wording in this policy. If introduced, they must be reviewed, disclosed and implemented with any required permissions and protections before use.
21. Policy changes and contact
An adopted version must identify its effective date and be available through the app and controlled public website. Material changes require appropriate notice and any newly required consent; a new policy cannot retroactively authorize an undisclosed collection or erase statutory rights.
This version takes effect for controlled testing on October 10, 2026. Before public launch, feature availability and outstanding operational rules must be aligned with the verified service and reflected in the applicable policy. Approval by Google or an app store is not guaranteed by policy wording. The service must actually meet the commitments it makes.
For questions or requests, contact Azeem Rana — reachonlinewithus@gmail.com. Do not send passwords, authorization codes, full mailbox exports or unnecessary financial documents. The app and website publish the same policy version. The applicable Google consent link must point to this controlled website policy.
Google data restrictions: Google API Services User Data Policy, including Limited Use. Privacy complaints: Office of the Privacy Commissioner of Canada.