Skip to content

lp: update privacy policy#1462

Merged
jobenjada merged 2 commits intomainfrom
lp/privacy-updated
Oct 25, 2023
Merged

lp: update privacy policy#1462
jobenjada merged 2 commits intomainfrom
lp/privacy-updated

Conversation

@jobenjada
Copy link
Copy Markdown
Member

update privacy policy

@vercel
Copy link
Copy Markdown

vercel bot commented Oct 25, 2023

The latest updates on your projects. Learn more about Vercel for Git ↗︎

2 Ignored Deployments
Name Status Preview Comments Updated (UTC)
formbricks-cloud ⬜️ Ignored (Inspect) Visit Preview Oct 25, 2023 1:39pm
formbricks-com ⬜️ Ignored (Inspect) Visit Preview Oct 25, 2023 1:39pm

@github-actions
Copy link
Copy Markdown
Contributor

github-actions bot commented Oct 25, 2023

Hey there and thank you for opening this pull request! 👋🏼

We require pull request titles to follow the Conventional Commits specification and it looks like your proposed title needs to be adjusted.

Details:

Unknown release type "lp" found in pull request title "lp: update privacy policy". 

Available types:
 - feat: A new feature
 - fix: A bug fix
 - docs: Documentation only changes
 - style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
 - refactor: A code change that neither fixes a bug nor adds a feature
 - perf: A code change that improves performance
 - test: Adding missing tests or correcting existing tests
 - build: Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm)
 - ci: Changes to our CI configuration files and scripts (example scopes: Travis, Circle, BrowserStack, SauceLabs)
 - chore: Other changes that don't modify src or test files
 - revert: Reverts a previous commit

@jobenjada jobenjada changed the title update privacy policy lp: update privacy policy Oct 25, 2023
@jobenjada jobenjada enabled auto-merge October 25, 2023 13:39
@review-agent-prime
Copy link
Copy Markdown
Contributor

The changes made in the PR are generally good, improving the clarity and completeness of the privacy policy. However, there are a few areas that could be improved:

  1. In the "Data we collect" section, the term "Service" is capitalized inconsistently. It would be better to stick to one style for consistency.
-This is the information we collect from **Website visitors** and **Researchers** as long as you are using our Service:
+This is the information we collect from **Website visitors** and **Researchers** as long as you are using our service:
  1. In the "How we use your data" section, the list of reasons for data collection could be made more concise and clear.
- Provide and improve our Service.
- Email you essential updates and offers (only if you're interested).
- Ensure our product works smoothly and fix any issues.
- Respond to legal situations and prevent fraud.
- Let you engage with our Service's interactive features.
- Support you when you need help.
- Track how our Service is used.
- Handle technical problems.
- Manage our relationship with you, including billing.
- Inform you about account changes or renewals.
- Share news and offers about our other services (only if you've shown interest).
- Use data in ways we explain when you provide it.
- Other reasons, but only with your agreement.
+ We use your data to:
+ - Provide and improve our service.
+ - Send essential updates and offers (only if you've opted in).
+ - Ensure smooth product functionality and fix issues.
+ - Respond to legal requirements and prevent fraud.
+ - Enable interaction with our service's features.
+ - Provide customer support.
+ - Analyse service usage.
+ - Handle technical issues.
+ - Manage our relationship with you, including billing.
+ - Notify you about account changes or renewals.
+ - Share news and offers about our other services (only if you've opted in).
+ - Use data in ways we explain when you provide it.
+ - Other reasons, but only with your agreement.
  1. In the "Data Subprocessors" section, the term "Service" is capitalized inconsistently. It would be better to stick to one style for consistency.
-We only share your information with our Service providers who help us operate our business, in which case those third parties are also required to comply with the GDPR framework. We worked hard to reduce the number of subprocessors to a minimum and keep your information within the EU. This is a list of the subprocessors we are working with:
+We only share your information with our service providers who help us operate our business, in which case those third parties are also required to comply with the GDPR framework. We worked hard to reduce the number of subprocessors to a minimum and keep your information within the EU. This is a list of the subprocessors we are working with:
  1. In the "Cookies" section, the term "Service" is capitalized inconsistently. It would be better to stick to one style for consistency.
-We only use cookies when you are logged into our Service. You can allow, eliminate, or block cookies within your browser. If you block all cookies, some websites will not work properly anymore.
+We only use cookies when you are logged into our service. You can allow, eliminate, or block cookies within your browser. If you block all cookies, some websites will not work properly anymore.
  1. In the "Data Transfers" section, the term "Service" is capitalized inconsistently. It would be better to stick to one style for consistency.
-Formbricks is based in the EU and all form and user data is stored in Germany, EU. Only billing information processed by Stripe Inc. and anonymized personal data neccessary to provide this Service may be transfered overseas.
+Formbricks is based in the EU and all form and user data is stored in Germany, EU. Only billing information processed by Stripe Inc. and anonymized personal data necessary to provide this service may be transferred overseas.
  1. In the "Users Acceptance Of These Terms" section, the term "Service" is capitalized inconsistently. It would be better to stick to one style for consistency.
-By using Formbricks, Researchers signify their acceptance of this policy. If Researchers do not agree to this policy, they should not use Formbricks. Researchers continued use of Formbricks following the posting of changes to this policy will be deemed their acceptance of those changes.
+By using Formbricks, researchers signify their acceptance of this policy. If researchers do not agree to this policy, they should not use Formbricks. Researchers' continued use of Formbricks following the posting of changes to this policy will be deemed their acceptance of those changes.
  1. There are a few spelling errors that should be corrected:
-We take your data privacy serious.
+We take your data privacy seriously.

-We take on considerable additional effort to collect as little data as neccessary and handle it safely and securely.
+We take on considerable additional effort to collect as little data as necessary and handle it safely and securely.

-Only billing information processed by Stripe Inc. and anonymized personal data neccessary to provide this Service may be transfered overseas.
+Only billing information processed by Stripe Inc. and anonymized personal data necessary to provide this service may be transferred overseas.
  1. The "Contact" section could be formatted better for readability:
-Please use the following contact information for privacy inquiries:
-[email protected]
-
-Formbricks GmbH<br/>
-Kuhnkestr. 6<br/>
-24118 Kiel<br/>
+For privacy inquiries, please contact us at:
+
+Email: [email protected]
+Address: Formbricks GmbH, Kuhnkestr. 6, 24118 Kiel

@jobenjada jobenjada added this pull request to the merge queue Oct 25, 2023
Merged via the queue into main with commit e0dce53 Oct 25, 2023
@jobenjada jobenjada deleted the lp/privacy-updated branch October 25, 2023 13:53
Dhruwang added a commit that referenced this pull request Mar 13, 2026
…bscribers

- Remove "email follow-ups" from the trial features list in SelectPlanCard
  since follow-ups are not actually unlocked during the trial period (#1462)
- Redirect users with existing non-free subscriptions away from the trial
  plan page so they cannot access it during onboarding (#1461)

Co-Authored-By: Claude Sonnet 4.6 <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant