Privacy Policy

Average Rent ("we", "us", "our") is operated by Work4Coins LLC. This policy explains what data we collect, how we use it, and your rights.

Information We Collect

Email address and name: when you request a city, subscribe to updates, or contact us.
Search address: the address you enter when requesting apartment data. We use this to find nearby properties.
Rent requests and saved preferences: your search location, budget, bedroom choice, move-in dates, request status, and notification choices. We use these to prepare your report and resume your request.
Resident content: notes, images, and reports that you submit. We use these to display your contributions and review reported content.
Usage data: standard analytics data (pages visited, browser type) collected via Google Analytics.
Website activity: signed-in visit dates and experiment records, including a browser identifier, page path, referrer host, bot score, and interaction events. We use these to measure page changes and protect the service.

How We Use Your Data

To find and track apartment pricing in your requested areas.
To send you email updates about price changes (if you opt in).
To improve the service and fix bugs.

We Do Not Sell Your Data

We will never sell, rent, or share your personal information with third parties for marketing purposes.

Third-Party Services

We use the following third-party services to operate Average Rent:

Cloudflare: hosting, CDN, database, uploaded-image storage, and private document storage (Cloudflare Pages, D1, and R2). Our application stores Gmail connection records, encrypted credentials, encrypted message content, and search records in Cloudflare D1.
Google Gmail API: mailbox authorization, message delivery, reply retrieval, and reply notifications for the Gmail connection you authorize.
Google Places API: to find apartment complexes near your address.
Google Analytics: website usage analytics and browser identifiers.
Forward Email: transactional email delivery.
Whop: payment processing for Pro subscriptions.

Plugin Review Accounts

We provide a separate restricted account for plugin reviewers. We store its username, synthetic account identity, salted password hash, access expiry, and session information. We do not store the reviewer password in the application database. The account can read rent data and manage its own application connections.

We store a digest of the network address to limit reviewer sign-in attempts. Daily maintenance removes rate-limit records after they are at least 24 hours old. We can revoke the reviewer account and its connections.

Reviewer sessions last at most 12 hours. They also end when the reviewer account expires or we revoke access.

Google Sign-In

If you use Google sign-in, we receive your Google account identifier and verified email address. We store the identifier to connect your Google account to your Average Rent account. We use your email address to identify your account and your session cookie to keep you signed in.

We do not store your Google password. Website sign-in does not store Google access or refresh tokens. Temporary sign-in records expire after ten minutes. We remove expired records during sign-in and daily maintenance. We keep the account identifier while you use the connection. You can request deletion through the contact address below.

Gmail Correspondence

Automatic Gmail correspondence is not available to the public yet. We use a restricted owner test to check sending and reply import. The following rules apply to that test and to the service when it opens. It requires Pro and Gmail permissions separate from Google sign-in. You must grant send and read permissions for automatic negotiation. We store encrypted access and refresh tokens for your connected mailbox. Tenant containers and the local model do not receive these credentials.

Google data we access

When you connect Gmail, we receive your Google account identifier, connected email address, granted permissions, and access and refresh tokens. For campaign messages, we access recipients, senders, subjects, message and conversation identifiers, reply-reference headers, dates, and message text. Supported attachments can provide text, unit details, rent quotes, and recurring fees. We also receive mailbox history identifiers and notification dates to check for replies.

How we use Google data

Before launch, you review the selected buildings, saved search limits, and planned requests. You authorize outreach and local reply processing through separate controls. The application can then send requests, counteroffers, and reminders within those limits. You choose the final offer. You sign the lease and make any deposit or payment.

Gmail read permission covers your whole mailbox. Average Rent reads matched campaign conversations and checks the delivery of sent messages. We check reply headers to link replies to your saved campaigns. During history recovery, we check a bounded set of headers from campaign contacts. A sender or subject alone does not establish a property match.

How we store and protect Google data

Our application server keeps mailbox credentials and imported message content encrypted in Cloudflare D1. We store message identifiers, dates, delivery status, and campaign links to organize your search and prevent duplicate sends. Account ownership checks restrict access to your records. We use HTTPS for the website and Google API requests. Our VPS processes only the bounded reply data needed for a model request, after you authorize local processing.

Imported replies and data derived from them expire no later than 30 days after the Gmail message date. We show the configured period before you request read access. A later import, model result, or review does not extend it. Outbound message text expires after the same period from creation. Expired email evidence is removed from reports, savings, recommendations, and exports.

We read supported HTML replies as plain text. In matched conversations, we can read plain text, HTML, and searchable PDF attachments within size limits. We store readable attachment text with the encrypted reply. File bytes stay in memory for processing. We do not store them. Attachment text and derived data expire with the source message.

The approved local model path processes each reply in a fresh, temporary process on our VPS. Renters share the model weights. They do not share conversation history or a persistent prompt cache. The process ends after completion, failure, cancellation, or timeout. We do not claim that server memory is securely overwritten. The model receives no Gmail credentials, signing documents, or payment authority. The application checks its results before using them.

Google delivers outbound messages to the recipients in your authorized campaign. Those recipients receive the message text and your sender address. Cloudflare processes stored connection and campaign records to host the application. Our VPS hosting infrastructure processes bounded reply data for the local model service. We do not send mailbox credentials to the model. We do not give landlords your mailbox contents or private search budget.

We use email data for your selected search. We do not sell it, use it for advertising, train general models with it, or add it to a shared property database. This release does not transfer your Gmail data to ChatGPT or another external model. Staff may read specific messages only with your explicit permission, for a necessary security investigation, or when law requires it.

Average Rent’s use of Google Workspace API data follows the Google API Services User Data Policy, including its Limited Use requirements.

If reply headers cannot be read, we pause sending. Unmatched reply review uses message and conversation IDs, a reason, and dates. These review records contain no body and expire after the configured period. Owner test tools can use send-only permission. Those tools are separate from customer negotiation.

Stop processing or delete saved data

Stopping outreach cancels future messages and follow-ups. Disconnecting Gmail blocks new sends, imports, and model work. It removes usable local credentials. If Google revocation fails, we keep an encrypted cleanup record until revocation finishes. Retained replies and reports keep their original expiry. Disconnecting does not delete your messages in Gmail.

Deleting a search removes its saved email and negotiation data. Account deletion also removes owned negotiation records. Private storage and provider failures stay in a cleanup queue until they finish. An unresolved delivery receipt or opt-out record can retain the minimum state needed to prevent a duplicate or prohibited send. It does not retain the message body. Billing allowances and legally required brokerage records follow their separate rules.

Cloudflare database recovery copies can remain for up to 30 additional days after active deletion. We keep a separate, private deletion record for 35 days, or until pending cleanup finishes. It contains action details and record IDs. It contains no message, mailbox address, token, or attachment. We apply these records and source expiry before reopening a restored database. We do not make longer-lived backups of Gmail content.

We cannot remove copies held by Gmail, recipients, or you after download. To request account deletion or report a cleanup issue, contact support@average-rent.com. Email and local model policy version: email-model-2026-10-06.v1.

Texas Locating Agreements

Texas brokerage outreach requires an effective agreement with the configured licensed partner. We store the approved document version, document hash, named parties, signature evidence, server dates, and audit records. The full approved agreement states the service and cancellation terms. Signing does not grant Gmail access or start outreach.

Your authenticated account can download its signed copy after Pro expires. Withdrawal stops future locating outreach. Brokerage agreement and referral records follow a separate retention policy with a minimum of four years. Deleting Gmail data or a search does not remove these records. We send agreement-copy links to the verified account email through our account email service.

Data API and Connected Applications

We use your account email to link Data API access. Customer account emails require verification. Restricted reviewer accounts use a synthetic identity. We store API key hashes, account allowances, usage counts, and application authorization records. We use these records to control access, enforce limits, and support your account.

If you connect ChatGPT or another application, we send the requested rent results, source links, observation dates, and account usage to that application. Cloudflare processes these records for hosting and storage. Whop processes Data API subscription payments.

If you allow identity and email permissions when you connect an application, we also send your stable account identifier, account email, and email verification status to that application. A reviewer account's synthetic email is unverified. We store your authorization, account email, and verification status with the connection to provide these permissions.

We store monthly usage records for up to 14 months. Authorization codes expire after five minutes. Access tokens expire after one hour. Refresh tokens expire after 30 days. Our daily maintenance task removes expired authorization codes and token records. It removes connections created more than 30 days ago when they have no remaining tokens, and clients created more than 30 days ago when they have no remaining connections. We keep account and billing records while needed to provide the service or meet applicable obligations.

We do not store chat transcripts or search inputs in our API usage records. Application logs record tool names, response times, and error status without credentials. Infrastructure providers may process connection metadata under their own service policies.

You can revoke API keys and disconnect applications from your Data API account. You can request account deletion through the contact address below.

Website Records and Browser Storage

Our retention task removes website experiment assignments and interaction records that are more than 120 days old. Saved searches, rent requests, signed-in visit records, and resident content do not have an automatic time-based deletion rule in the application. You can request removal through the contact address below. You can delete your resident notes and attached images through their controls.

The rent-request form saves your name, email, search address, coordinates, move-in dates, budget, preferences, request status, and report access link in this browser's local storage. This lets you return to the request. The saved copy has no automatic expiry. It stays until you clear it, clear the site's browser storage, or replace it with another request.

Close open rent-request tabs before you clear the saved copy. Clearing this browser copy does not delete the request stored by Average Rent. Use the contact address below to request removal of server records.

Cookies

We use a session cookie (ar_session) to keep you logged in. This cookie is HTTP-only and secure. Normal account sessions expire after 30 days; reviewer sessions use the shorter limit stated above. We use the _arx cookie to assign website experiments and measure interactions. It expires after 90 days. We also use Google Analytics cookies to measure website use. You can remove cookies through your browser's site-data settings. Removing the session cookie signs you out.

Your Rights

You can unsubscribe from emails at any time using the link in any email we send. To request deletion of your data, contact us at support@average-rent.com.

Contact

Questions about this policy? Reach us at support@average-rent.com or visit our contact page.