Compliance controls

What the software enforces. Informed by regulatory research; not legal advice. Your brokerage can tighten these policies.

• Brokerage identification. Drafts are checked for your brokerage's name; approval appends it with the office phone where missing (N.J.A.C. 11:5-6.1).
• Required legends. "In New Jersey, real estate commissions are negotiable" and the licensure legend are appended on approval when absent; "sold" is flagged until title transfers.
• Broker approval log. Where your brokerage requires it, content and corrections wait for the broker of record; every decision stores approver, role, time and a hash of the exact content.
• Fair housing. Protected-class, school-quality, crime and "type of buyer" language fails the check and blocks approval (Fair Housing Act, NJ LAD).
• No MLS data without a licence. Comparable sales and expired-listing data appear only from a configured, signed vendor source; none is configured in this build.
• Consent ledger. Per-contact consent by channel. Texting drafts require prior express written consent; the product never infers it and never sends.
• No owner cold outreach. Owners from FSBO or expired sources are never suggested for calls or texts; eligibility is limited to mail or inbound response.
• CAN-SPAM. E-mail drafts are checked for a postal address and opt-out language.
• Reviews. Review requests use one identical template; no incentives or gating; testimonials are stored verbatim and never AI-edited (FTC rule 2024).
• RESPA. Introductions to lenders and title companies are checked for fee, gift or credit language and flagged as relationship-only.
• Platform terms. Zillow, Realtor.com, Homes.com, Redfin and the NJ licensee search are never fetched; robots.txt is honoured everywhere else.
• AI-assist disclosure. Appended per brokerage policy, ahead of pending New Jersey legislation.