Skip to content
TUNRO

TUNRO · TRUST & TRANSPARENCY

Privacy Policy

What Tunro handles, why it is needed, who can see it, and how to exercise your choices. This notice covers the current US service.

Effective October 14, 2026 · Version 2026-10-14

Who handles your information

DevScape LLC operates Tunro. We determine how account, security, support, billing, and marketplace information is processed for our service. For tenancy records a landlord supplies or manages, we generally process information to provide that landlord’s workspace, while the landlord is responsible for their own purposes, lawful collection, notices, permissions, and retention. A landlord’s separate privacy practices and Stripe’s processing are not replaced by this Policy. Contact us if you need help identifying the responsible property team.

Information collected

Account information includes name, sign-in and contact email, phone when provided, portal role, authentication/session information, and agreement-acceptance versions and timestamps. Property and tenancy records may include addresses, units, adult occupant contacts, lease dates, rent amounts, charges, payment references, requests, complaints, visits, messages, preferences, and documents you or your property team provide. Professional information includes business profile, trade, service area, availability, quotes, jobs, messages, photos, reviews, reports, and work records. Support and administration records include feedback, correspondence, access records, and actions needed to operate and protect the platform. Hosting and security providers may receive IP address, request time, browser/device information, and error metadata when you connect. We do not need Social Security numbers, government ID images, full card numbers, or unrelated sensitive medical information in Tunro fields or uploads.

Sources and purposes

We receive information from you, your landlord or property team, other authorized participants in your household or job, our authentication and payment providers, and your browser’s requests. We use it to authenticate accounts; organize homes and rent records; connect parties; coordinate requests, repairs, and visits; deliver requested communications and documents; support subscriptions and payment workflows; answer support and rights requests; record agreement acceptance; investigate abuse; maintain security; and satisfy applicable legal duties. We do not use tenancy records to make automated eligibility decisions about housing, employment, credit, or insurance.

Who can receive information

Your property team and authorized household participants can see information within their permitted workspace. Professionals can see information made available for opportunities and their jobs; avoid placing private resident details in a publicly described job. Quotes, schedules, work messages, completion evidence, and reviews are visible to the parties and audiences shown in the feature. Internal team members may access limited records for support, security, administration, or legal duties under role-based controls. Service providers supporting hosting, authentication, database/storage, and payments process information needed for those functions. Current infrastructure includes Supabase, DigitalOcean hosting, and Stripe when a payment or billing feature is used. We may disclose information when legally required, to protect people and systems, or in a business transfer with appropriate safeguards and notice where required. We do not sell personal information or share it for cross-context behavioral advertising, and the current site includes no optional advertising or analytics trackers.

Payments

Stripe receives payment and connected-account information directly through its own flows. Tunro uses account identifiers, billing status, charge and settlement references, and related records needed for the requested workflow. Rent is paid to the landlord’s connected Stripe account, not held in a Tunro account. Do not put card numbers, banking credentials, or verification codes in Tunro messages or support requests. Stripe’s own notice explains its independent processing.

Cookies and browser storage

We use essential local storage for authentication and browser preferences, and session storage to remember whether the introduction has played in the current tab. The notice acknowledgment is stored locally for up to six months. Authentication storage may persist until sign-out, expiration, or removal through browser settings; the authentication provider manages token lifetimes. The Cookie & Storage Notice lists these purposes. We do not load optional analytics or advertising trackers. A future optional category will require an updated notice and a genuine choice before activation where required. Clearing or blocking essential storage may sign you out or reset preferences. A Global Privacy Control signal does not activate tracking; there is currently no sale, advertising sharing, or targeted-ad processing to opt out of.

Security and retention

We apply access controls, private-file restrictions, encrypted transport, validation, and additional authentication for internal team access. No service can promise absolute security. We retain information while needed for the account or requested service and, where applicable, for legitimate legal, fraud-prevention, financial, dispute, or recordkeeping needs. Archiving a record hides it from active views and does not mean it is deleted. Account closure or a deletion request may require coordination with the landlord who controls tenancy records, and some records may remain where law permits or requires. Service-provider backups and security logs follow their own retention cycles. We do not promise immediate deletion from every backup. Ask us about a specific record or retention need through the contact route below.

Your choices and privacy requests

You can edit available profile details, manage notification preferences, choose what to upload, and use available export/download controls. Request access, a copy, correction, deletion, account closure, information about recipients, or an applicable opt-out through the contact route below. You need not create an account solely to make a request. Tell us the request type and email associated with your data; do not send passwords, government ID, financial credentials, or unnecessary documents. We will verify identity proportionately, assist with lawful authorized-agent requests, respond within applicable legal time limits, and explain any permitted denial or extension. You may appeal a denial through the same contact route by selecting Appeal or complaint and identifying the earlier decision and may complain to your state attorney general or other competent regulator. We will not unlawfully discriminate against you for exercising rights. Available rights, exceptions, and deadlines depend on applicable law; we do not require a waiver of them.

Residents and landlord-controlled records

A landlord may need to retain lease, payment, maintenance, or dispute records independently of your Tunro login. A request to delete an account does not cancel rent, a lease, or a lawful recordkeeping obligation. We help route requests involving landlord-controlled data and fulfill our own legal duties. Contact your property team for corrections to a charge or a lease and contact us about platform privacy or access issues.

Children and US use

Tunro account services are intended for adults 18 or older in the United States. We do not knowingly collect information directly from children under 13 or offer child accounts. Landlords should list only the adult occupants needed for their workflow and avoid uploading information about children. Contact us if you believe a child’s information has been provided so we can assess and address it. Our US focus does not guarantee every provider stores all information only in the US; provider locations and support operations may involve other jurisdictions with appropriate contractual and legal safeguards where required.

Updates

The date and version identify this notice. We will post changes here and provide additional notice or obtain any consent required for material changes. A new use of previously collected information must have an appropriate legal basis; a policy update alone does not authorize processing that requires separate consent.

Contact Tunro

DevScape LLC

Use DevScape’s public contact forms and begin your request with “Tunro”. An account is not required. Do not send credentials or sensitive documents.