Question 1

Security Exploit Bounty Program

Accepted Answer

||| Our security exploits bug bounty program is currently paused. We do not reward bug reports for now.

Responsible Disclosure

Q: Security Exploit Bounty Program

||| Our security exploits bug bounty program is currently paused. We do not reward bug reports for now. Responsible Disclosure Security is of utmost importance to Noticeable. In pursuit of the best possible security for our service, we welcome responsible disclosure of any vulnerability you find in Noticeable. Principles of responsible disclosure include, but are not limited to: Access or expose only customer data that is your own. Do not exfiltrate data from our infrastructure (including source code, data backups, configuration files). If you obtain remote access to our system, report your finding immediately. Do not attempt to pivot to other servers or elevate access. Avoid scanning techniques that are likely to cause degradation of service to other customers (e.g. by overloading the site). This includes the spamming of contact forms, support emails, etc. Keep within the guidelines of our Terms of Service . Keep details of vulnerabilities secret until Noticeable has been notified and had a reasonable amount of time to fix the vulnerability. In order to be eligible for a bounty, your submission must be accepted as valid by Noticeable. We use the following guidelines to determine the validity of requests and the reward compensation offered. Reproducibility Our engineers must be able to reproduce the security flaw from your report. Reports that include clearly written explanations and working code are more

Q: What's Noticeable EU GDPR compliance status?

The European Union General Data Protection Regulation (GDPR) is a regulation that aims at unifying EU member state data privacy regulations into a single regulation, enforced on the EU single market. This article describes the GDPR compliance status of Noticeable. | To ensure your company is GDPR-compliant, it needs to ensure its providers (i.e. Noticeable) are also GDPR compliant. Noticeable is GDPR-compliant, and strictly enforces the regulation as to protect the user data we store. The list of our providers (ie. Data Processors) is available, and kept up to date, in our Data Processing Agreement (DPA). Noticeable data processor providers have been checked to be GDPR-compliant (Cloudflare, Stripe) or certified to the EU-US Privacy Shield Framework (Firebase Authentication, Firebase Hosting, Cloud Firestore for Firebase). ||| Some believe that EU personal data can’t leave the EU for GDPR compliance is not true. Noticeable and GDPR The GDPR regulation can be reduced to 12 important points. For each point, we explain how Noticeable handles its compliance. If we did not answer your questions in this article, you can still contact us and drop us a chat or email. 1. Awareness All employees responsible for software development & infrastructure maintenance of Noticeable are fully aware of the GDPR requirements. Also, code reviews ar

Security is of utmost importance to Noticeable. In pursuit of the best possible security for our service, we welcome responsible disclosure of any vulnerability you find in Noticeable. Principles of responsible disclosure include, but are not limited to:

Access or expose only customer data that is your own.
Do not exfiltrate data from our infrastructure (including source code, data backups, configuration files).
If you obtain remote access to our system, report your finding immediately. Do not attempt to pivot to other servers or elevate access.
Avoid scanning techniques that are likely to cause degradation of service to other customers (e.g. by overloading the site). This includes the spamming of contact forms, support emails, etc.
Keep within the guidelines of our Terms of Service.
Keep details of vulnerabilities secret until Noticeable has been notified and had a reasonable amount of time to fix the vulnerability.
In order to be eligible for a bounty, your submission must be accepted as valid by Noticeable. We use the following guidelines to determine the validity of requests and the reward compensation offered.

Reproducibility

Our engineers must be able to reproduce the security flaw from your report. Reports that include clearly written explanations and working code are more

Question 2

Embedded Noticeable Timelines

Accepted Answer

Embeddable Noticeable Timelines

Noticeable Timeline pages can be embedded into a full page of your website, rather than hosting it on a subdomain. For this purpose, we allow serving Timeline content from an iframe.

Here is an example:

BigCommerce Integration Example

|| A Github repository that provides a full integration example, including support for hash-routing, is available at noticeableapp/noticeable-timeline-iframe.

Options

Timelines support options via query string parameters:

cache=false: The content is loaded from Noticeable servers, bypassing caching layers. This ensures data freshness at the cost of higher response times.
footer=false: Hide the Timeline footer.
header=false: Hide the Timeline header.

To apply options, append them to your timeline URL:

https://updates.noticeable.io?footer=false&header=false

Question 3

What's Noticeable EU GDPR compliance status?

Accepted Answer

The European Union General Data Protection Regulation (GDPR) is a regulation that aims at unifying EU member state data privacy regulations into a single regulation, enforced on the EU single market. This article describes the GDPR compliance status of Noticeable.

| To ensure your company is GDPR-compliant, it needs to ensure its providers (i.e. Noticeable) are also GDPR compliant. Noticeable is GDPR-compliant, and strictly enforces the regulation as to protect the user data we store. The list of our providers (ie. Data Processors) is available, and kept up to date, in our Data Processing Agreement (DPA).

Noticeable data processor providers have been checked to be GDPR-compliant (Cloudflare, Stripe) or certified to the EU-US Privacy Shield Framework (Firebase Authentication, Firebase Hosting, Cloud Firestore for Firebase).

||| Some believe that EU personal data can’t leave the EU for GDPR compliance is not true.

Noticeable and GDPR

The GDPR regulation can be reduced to 12 important points. For each point, we explain how Noticeable handles its compliance. If we did not answer your questions in this article, you can still contact us and drop us a chat or email.

1. Awareness

All employees responsible for software development & infrastructure maintenance of Noticeable are fully aware of the GDPR requirements.

Also, code reviews ar

Question 4

Posts Segmentation

Accepted Answer

Posts Segmentation

Noticeable allows keeping your users in the loop about your product. Thanks to the Plug & Play Widget, users are notified about new changes in the right context and at the right time. However, what if you schedule a maintenance for your product in France and you want to publish an update to users who are located in this country only? That's where user segmentation comes to the rescue :)

| Segmentation is a seemingly simple but extremely powerful mechanism to filter posts based on your own conditions.

Defining Segments

When you publish a post, you may define segmentation filters (enter a value and press enter):

Then, on the page that includes the Noticeable Widget you simply need to configure the Widget with the desired segments based on information you have.

You can do it statically (multiple segments must be separated with a comma) :

or dynamically:

document.addEventListener('noticeable-widget-created', function(e) {
    e.target.setSegments(['Country:France']);
});

It's just that easy!

Let's say you publish a post with segment "Country:France" and the Widget on your pages is configured to include segment "Country:France" for user A but not for user

Question 5

How to format Noticeable posts?

Accepted Answer

Noticeable posts are formatted with Markdown. Markdown is an easy-to-use syntax to format texts. You can use Markdown to insert bold texts, titles, images, and even YouTube or Vimeo videos.

This article sums up the Markdown syntax that is available to you in Noticeable Posts.

Formatting text

Bold text

Markdown code: **This is a bold** text section. Example: This is a bold text section.

Italic text

Markdown code: _This is an italic_ text section. Example: This is an italic text section.

Underlined text

Markdown code: ++This is an underlined++ text section. Example: This is an underlined text section.

Strikethrough text

Markdown code: ~~This is a strikethrough~~ text section. Example: ~~This is a strikethrough~~ text section.

Inserting titles

H1 title (huge)

Markdown code: # Huge title

H2 title (large)

Markdown code: ## Large title

H3 title (medium)

Markdown code: ### Medium title

H4 title (regular)

Markdown code: #### Regular title

H5 title (small)

Markdown code: ##### Small title

H6 title (tiny)

Markdown code: ###### Tiny title

Delimitating texts

Horizontal line

Markdown code: ---

Example:

Inserting lists

Bullet list

Markdown code: * Item Example:

Noticeable allows using lists
List may be bullet-points

Numbered list

Markdown code: 1. Item Example:

Noticeable allows using lists
Lists may be numbered

Inserting code

Inline code (single line)

Question 6

Serving content under your own domain

Accepted Answer

Serving content under your own domain

By default, all content is served from the domain noticeable.io. This includes the API, Timeline, and Widget. In some corporate environments with egress traffic filtering, this may be an issue. For this purpose, Noticeable allows serving all content under your own domain or subdomain.

Noticeable Timeline

Timelines are publicly accessible via an URL that includes an opaque identifier. Although this has the benefit to make your timeline unlikely guessable, it makes it hard to remember.

You can customize the URL to a more professional and easy to remember one such as updates.acme.com or acme.news. If you’d like to do so, the setup is as simple as follows:

Open a project from your dashboard.
Select Timeline in the sub-menu.
Enter your custom domain in the dedicated field and save the form.
Follow DNS configuration instructions that appear.

The configuration instructions will ask to add 3 records with your DNS provider:

a CNAME record that is used to check domain ownership
two A records for redirecting traffic to our servers from your custom domain.

The setup is fully automated but may require up to 48 hours due to DNS propagation and SSL certificate generation.

|| A records are used in order to support apex d

Frequently Read Articles

Browse All Categories