Who we are
Dealguard is a HubSpot app built and operated by Anurag Ojha, a solo developer based in India. If you have a question about this policy or about your data, email support@dowelry.com.
This policy covers the Dealguard app (including its settings page and deal card inside HubSpot) and this website.
Information we access in HubSpot
When you install Dealguard, your HubSpot account grants the app these OAuth scopes:
oauth— to complete install and keep the connection workingcrm.objects.deals.readandcrm.objects.deals.write— to read deals and, when a rule fails, move a deal back to the previous stagecrm.objects.contacts.readandcrm.objects.companies.read— to see whether a deal has associated contacts or companiescrm.objects.owners.read— to read deal-owner information, including looking up a name to show in the appcrm.schemas.deals.read— to read deal pipelines, stages, and property definitions so you can pick them when you create a rule
In practice, when a deal changes stage (or when the deal card loads), we read that deal's properties — such as name, amount, close date, pipeline, stage, owner, and any other deal properties your rules reference. We also read the deal's stage history, and we count associated line items and collect the HubSpot IDs of associated contacts and companies. We do not pull contact or company profiles, email addresses, or line-item catalogues into our database.
If a rule fails, we write back to your HubSpot account: we update the deal's stage, and we create a note (and, unless you turn that option off, a task for the deal owner) on the deal explaining why the move was blocked.
HubSpot also sends us webhook events when a deal stage changes and when the app is uninstalled. Those events include identifiers such as your portal ID, the deal ID, the stages involved, and sometimes the user who made the change.
Information we store
The app is hosted on Railway. Account data is stored in a PostgreSQL database there. For each installed HubSpot portal we store:
- Your HubSpot portal ID, OAuth access and refresh tokens, token expiry, plan and trial end date, the email address of the HubSpot user who installed the app (from HubSpot's token information), and install and update times. A HubSpot user ID may also be stored if we receive one.
- The rules you configure, including the name, pipeline, stage, rule type, and the settings for that rule (for example, which properties are required).
- A violation log of blocked moves. A log row includes the deal ID, deal name, owner ID, rule name, pipeline and stage IDs, a short explanation, the time of the event, and any recorded resolution.
- Optional bypass entries you add (a user or integration identifier and an optional label).
- Your alert settings: whether the app creates a task for the deal owner, whether email alerts are on, the email addresses that receive them, whether they arrive for every blocked move or as a daily summary, and your HubSpot account's time zone and domain (used to time the summary and link to deals), and the ID of the last owner task we created for each deal (so a repeated block updates that task instead of creating a new one).
- While the daily summary is on, a short list of the day's blocked moves (deal ID and name, owner name, stage, and what was missing). We delete it after 3 days.
- A small cache of a deal's last known stage, and short-lived internal records used so the app does not react to stage changes it made itself.
- Temporary job-queue records used to process webhook events.
We do not store the contents of your contacts, companies, or line items. Notes and tasks live in your HubSpot account; we keep the explanation text in the violation log.
How we use this information
We use it only to operate Dealguard: to authenticate the app, evaluate your rules, move a deal back when a rule fails, add the note or task, show status on the settings page and deal card, and keep the violation log. We do not use your CRM data to train models, to advertise, or to build profiles of your customers.
Hosting and service providers
The application and database run on Railway. Railway's staff and infrastructure may process data as needed to host the service. HubSpot, as the platform where your CRM already lives, receives the reads and writes described above when the app runs in your portal.
Emails from Dealguard (email alerts about blocked moves, and beta invites) are delivered by Resend. Resend receives each email's recipient address and its content (for an alert, the deal name, owner name, stage, and what was missing) so it can deliver it.
Railway and Resend may process data in the United States or in other countries where they operate. If you install the app from India or elsewhere, your data may therefore be transferred outside your country in order to provide the service.
This website
This website has no accounts, no forms that collect personal data, and no advertising or analytics cookies. If you email us, we will see whatever you include in that message. Our host may keep standard server logs (such as IP address, time, and the page requested) for a limited period, for security and operations.
Sharing, selling, and legal requests
We do not sell your data. We do not share it with advertisers or data brokers. We share data only with the hosting provider described above, with HubSpot as needed to run the app in your portal, with Polar to bill a paid plan, with Slack if you add a Slack webhook (to post your alerts there), with Resend to deliver email alerts and beta invites, or if we are required to do so by law. We may also disclose information if you ask us to (for example, when helping you debug an issue you reported).
Billing
Paid plans are sold through Polar, our merchant of record. Polar collects your payment details; we never see your card. We store your Polar customer and subscription IDs, the plan, and billing status. Slack webhook URLs you add are stored encrypted.
If we invite you to the lifetime beta by email address or portal ID, we keep that invite entry (the email address or portal ID, a short note, when we emailed you the install link, and when it was used) until we remove it.
Retention
We keep the account, rules, logs, and related records for as long as Dealguard remains installed in your HubSpot portal. We do not currently run a separate automatic deletion schedule for violation logs while the app is installed.
Deletion on uninstall or by request
When you uninstall the app, we delete your account record. We learn about the uninstall from HubSpot's app lifecycle events, from a signed uninstall webhook, or, as a fallback, when HubSpot stops accepting your portal's access token (we wait 24 hours, then delete). Rules, violation logs, bypass entries, stage cache rows, Slack settings, alert settings (including email-alert recipients), the daily-summary list, and internal action records for that account are deleted with it. If you had a paid subscription, we cancel it so you are not billed again.
We keep one record per HubSpot portal ID noting that the portal has used its free trial, so the trial can't be restarted by reinstalling. It contains only the portal ID and the dates.
We do not store HubSpot contact records. When HubSpot sends a contact privacy deletion request, there is nothing of that contact's to delete; we acknowledge the request.
You can also email support@dowelry.com and ask us to delete your data. We will delete the records we hold for your portal, then confirm by email. Temporary hosting logs may remain for a short time according to our host's ordinary practices.
Security
The app is served over HTTPS. Incoming HubSpot webhook and signed app requests are checked against HubSpot's request signature before we act on them. OAuth tokens are stored in our database and used only to call HubSpot on your behalf. No security practice is perfect; please contact us if you believe there has been a problem.
Children
Dealguard is a business tool for HubSpot customers. It is not directed at children, and we do not knowingly collect personal information from children.
Changes
We may update this policy as the app changes. The “Last updated” date at the top of this page will change when we do. If a change is material, we will also try to note it in the app or by email if we have a contact address for your account.
Contact
Anurag Ojha — support@dowelry.com.