Privacy notice
FixSignal minimizes collection. The public radar can be browsed without an account. A watchlist is stored in your own browser using local storage and is not sent to FixSignal.
Who controls this service
FixSignal is operated by Nazar Adamovych, 31 Queens Way Apt 10, Camillus, NY 13031. Privacy questions and requests may be sent to support@getfixsignal.com.
Access requests
If you submit the access form, FixSignal collects the name, work email, company, trade, service area and product goal you provide, plus submission time and campaign attribution such as UTM parameters, advertising click identifiers, the referring page and first landing path. First-touch attribution is kept in session storage while you move between FixSignal pages, then included only if you submit the form. This data is used to respond, configure access, improve the product and understand which campaigns produce relevant business requests. The server also compares the selected trade and service area with the current City snapshot so it can distinguish a live-coverage review, zero current matches, an area outside live coverage or a request that needs manual review. It is not sold as a consumer lead.
Public property records
FixSignal processes public City of Syracuse property-code records. The public product intentionally excludes owner names, owner home/mailing addresses and inspector identifiers from its public API and interface. See the data source page for the exact field policy.
Analytics and device data
Vercel Web Analytics and Speed Insights may process page paths, referrer information, browser or device characteristics, approximate location derived by the provider and performance measurements. FixSignal also records limited first-party funnel events—such as opening the radar, selecting a plan or starting the coverage form—in Vercel Analytics and structured runtime logs. These events include placement and campaign dimensions, but not the name, email, company or text entered into the access form. FixSignal uses these signals to understand traffic, diagnose performance and measure access requests. A completed access-request event may also include the selected service lane, coverage outcome, current grouped-match count and lookback window, but not the submitted service-area text. Campaign values that are not safe measurement dimensions are logged only as `other`. Do not include sensitive personal information in campaign URL parameters.
Service providers
Vercel hosts the service, Upstash provides the Redis data store used for opaque access grants, rate limits, delivery preferences and idempotency records, Resend delivers transactional email, Hostinger provides the monitored support mailbox, and Stripe processes subscription billing when paid access is enabled. FixSignal does not receive or store complete card numbers. Each provider processes only the data needed for its function under its own terms.
Customer account access
When paid access is enabled, FixSignal uses the email and customer/subscription status held by Stripe to verify entitlement. A requested sign-in email contains a single-use link that expires after 15 minutes. The link grant is stored with an opaque nonce and Stripe customer reference, then deleted atomically when used. A signed, HttpOnly customer-session cookie can remain for up to 30 days, but every protected account read or change rechecks the subscription with Stripe. FixSignal stores selected trade and Syracuse territory views in subscription metadata; it does not put them in the browser session token. A completed Checkout reference is retained as a one-way hash for up to 30 days solely to prevent reuse of the account claim flow.
Delivery preferences and stop requests
A coverage request does not itself start a morning digest. If you later activate email or Telegram pilot delivery, you can request a stop through the delivery-control page, by replying STOP or by emailing support. A signed stop link can save the selected channel immediately using a one-way recipient identifier; the preference store does not receive the recipient's email address. If a signed link is unavailable, the manual form sends the delivery email, optional company and selected channel to the monitored support inbox so an operator can match the configured recipient. Runtime logs record only the channel, method and request outcome, not the submitted address or company.
Founding-pilot reviews
A configured pilot may receive a signed, expiring scorecard link during its review window. The URL carries an operator-assigned opaque pilot ID, not the recipient's email or company. The scorecard collects counts of records reviewed and considered relevant, usefulness, a time-saved range, willingness to pay, a reason category, optional comments and optional permission for follow-up. The full response and opaque pilot ID are delivered to the monitored support inbox. Runtime logs contain only aggregate answer fields and do not contain the pilot ID or comment. Submitting feedback does not authorize publication of a testimonial.
Retention and requests
Access-request data is retained for up to 12 months after the last interaction unless a longer period is required for an active customer, dispute or legal obligation. To request access, correction or deletion, email support@getfixsignal.com.
Security
No internet service is perfectly secure. FixSignal validates input, limits field lengths, uses server-side adapters for secrets, rate-limits account-link requests, requires one-time grants for passwordless access and does not put payment credentials in application code.