Privacy Policy
Effective on publication.
This policy explains how the Sanju Matcha prospecting workspace handles information about team members and people whose business contact details appear in shared prospect records.
Information the workspace handles
- Accounts and access. We use member email addresses, account roles, password hashes, invitations, and session records to manage access. A sign-in cookie keeps your session active for up to seven days. Invitations are valid for up to 72 hours and can be used once. Your browser can keep interface preferences for the current tab.
- Prospecting and pipeline. We process search terms and selected areas, saved business and contact information, notes, and lead assignments to support team prospecting. The workspace records who created a lead and who owns it. Authorized workspace members share these records. Administrators have additional access to manage invitations and workspace operations.
- Hosting and usage. Railway hosts the application and its stored workspace data. The app records provider request usage and selected workspace activity to operate the service and manage Google usage limits.
Google Maps and Places
When you use Discover with Google enabled, we send search terms and the selected area to Google for place search. If you open a Google map, your browser connects to Google. Google may receive your IP address and information about the search or location used to provide its services. Google handles that information under its own privacy policy. The workspace can keep Google place identifiers to link saved leads to listings. Google listing details are shown temporarily in the current hosted configuration. Members can also enter their own information or use supported independent sources for saved business details.
When you request location suggestions, the address or other text you type in the location field is sent to Google to return suggestions. The workspace does not store lists of raw suggestions. If you choose a suggestion and confirm the area, the workspace may keep Google-derived coordinates for that area for up to 29 days. Independently entered or drawn areas follow the workspace’s retention practices.
Google Privacy Policy · Google Places API policies
Retention and privacy requests
Account records, shared prospects, search history, and operational records are held in persistent workspace storage. Archiving a search keeps it in the workspace. Account and record retention depends on continued workspace use and administrative maintenance. The hosting administrator manages any backups through the hosting service. Backups may contain earlier versions of workspace records for as long as the hosting service retains those backups.
Workspace members can raise privacy questions with the workspace administrator who invited them.