This is St. Tech, Hawaii. Humanity matters here. I'm Marsha Joyner, and we are navigating the journey. Navigating the journey is dedicated to exploring the options and choices in life. Today, August 9, we will explore a journey that no one should ever have had to experience. August 9, 1945 marked the day of triumph and tragedy. The triumph of the wars ending that ushered in the tragedy that would become the nuclear age. August 9, 1945, that's the pan-time, but we get this all mixed up. But anyway, it was a busy day in the history of World War II. The United States dropped a nuclear bomb on Japan, devastating the city of Nagasaki. The Soviet Union followed through with an agreement that they made early in the war, and they declared war on Japan. August 8, August 8 in Washington, President Truman, was the first step that many Americans hoped would mean that we would have peace in this world more. The President signed the United Nations Charter, thus completing the American ratification of the document. In doing so, the United States became the first nation to complete ratification.  About 420,000 people died. And who knows how many continued to die after that one day. That includes a group of people that most of us don't talk about, the Korean people who had been drafted into the Japanese military and forced to work as Japanese during the war. The mayor of Nagasaki wrote, and I quote, decades have passed since that day. Now the atomic bomb survivors are advancing into old age and their memories are fading into the midst of it. The question of how to inform our young people about the horrors of war, the threat of nuclear weapons, and the importance of peace. Therefore, it is a matter of pressing concern. The citizens of Nagasaki pray that this miserable experience will never be repeated on Earth. We also consider it our duty to ensure that the experience is not forgotten, but passed on to future generations. We must tell this story. We must tell it in every generation. Not about winning or losing, but about the catastrophe of the conflict, the devastation of the deaths and destruction, the inscapable suffering of war as well as people who died that day. Some were just living their lives as young people. So now we tell the story. And we tell it here in Hawaii every year since 1991. The Nagasaki Peace Bill is a gift from the people of the city of Honolulu, to the city of Honolulu, by the survivors of the atomic bombing in Nagasaki. Recognizing the true steps to peace must begin with acknowledgement of harmful actions in the past. Survivors in Nagasaki wished to make a gesture of reconciliation to the people of the city and county of Honolulu, which sustained a military attack on December 7th. Here, we have a little replica of the bill, which was given to me by the people, by the Habapasha of Nagasaki, because, along with my guests today, we have made sure that the bill has been wrong twice a year, every year since 1991. Francis and Val Biglielmo, who have both passed this year, worked with the Congress Against Atomic and Hydrogen Bomb Committee in Nagasaki. The Nagasaki Prefecture Members Association, they were the victims of this horrible, horrible condition, and they raised the money to create the statue and make the bill. They gave a bill to every city that the Japanese bombed, and every bill was different, of course, but that was their way of acknowledging what they did. And it was through these mutual efforts that a group of people managed to have this beautiful bill here on the grounds of Honolulu Hall. Now, we'll get into the weeds. Of course, you know I was going to talk about the weeds. Right? Fosse did not want anything to do with the bill, nothing, because he had been a Marine in the war. He was still fighting the war. So the fact that the people of Nagasaki gave us the bill, and the people of Hiroshima gave the city a bill, he put them in storage, didn't want anything to do with it. So it was Francis and Val working with hundreds of people to get them out of story and find a place for them. So the temple in Japan, what used to be Japan Town, said we'll put it on our property. And so we managed to have... The Hiroshima bill. That's the Hiroshima bill. We managed to have some really super people in the city council at the time, and they overrode Fosse's upset. So that's why the bill... At the time, there were no buildings down there. And the bill was placed in this valley, beautiful valley. And Walter Ozawa said that because Nagasaki sits in a valley with the mountains on both sides, he thought it was appropriate that it be in this valley. So that is the story of the bell. Now, my friend Joanne. Joanne Tachibana and I have been together on this bell thing since 1991. Joanne was at the city for 40 years. 41. Oh my God. How do you put up with those? She was in council services, right? Off of the city clerk with service to city council. She has seen city council come and go. And mayors. And mayors. And mayors, yes. We were not going to talk about that. I promised he would. We weren't going to talk about it. So Joanne, talk, talk, talk, talk. Tell me about Joanne. I think I know Joanne. So tell me all about Joanne. Well, thank you for the opportunity to share our story because working together on peace measures, you have been an inspiration to not only me, but the many people you encounter by your example and being, you know, marching with Dr. Monson's king.  And she does wonderful things for, she finds interesting facts. And we have been inspired by Lodec, right? But I grew up in a very small town on the Big Island. And I was involved with International Affairs as a high school student.  And their philosophy was peace, culture, and education, which really tied into what I believed in. Also that, you know, the United Nations is a highly respected organization by people of Hawaii and was embraced in that with the volunteer group. I've been volunteering with that since the 1990s, as you mentioned. And then we've encountered each other and became co-ordinators and partners in every peace adventure that we could find. And I have been... Yes. Thank you. Listen to this. Yes. Oh. Yeah, I can hear them in your microphone. Oh. Oh. That would be a little rough. Yes. Yeah, okay, got it. Now, you talked about interesting little facts. Mm-hmm. Yes. The one little fact... That's my inspiration. Yes. And that is... Harry Truman. Yes, absolutely. As we began celebrating Nagasaki, which is a forgotten celebration, because all the community remembers Hiroshima because that's first. And then, all of a sudden, nobody thinks about Nagasaki. So we were really thrilled that we were the ones to carry that torch. And then, in Congress 8, we did... Look what I found.  Never again, never again. Then on August 8th, President signs that Charlie, she talks about United Nations and, wow, we're going to go to peace. And then, unbeknownst to the world, he bombs Nagasaki. And that shattered many people's hopes. And so we tried to embrace that the United Nations existed in 1945, but President Schumann still kept one more step to continue the war. It is astounding, yes. And when I tell that story, most people say, oh, that didn't happen. I don't believe that. Yes. I've had lots of people that go have to go Google August 8th to see what happened. Yeah. Now, of course, because some of it is Japan time and some of it is American time, sometimes it reads August 9th that the bombing and the signing are all on the same day. Ah, yes. So it had to decide. It sounds more traumatic than 8th and 9th. Yes. Yeah. I've often wondered, because he came late to the Manhattan Project, I often wonder if it had already been planned even before he came, you know, and it was already in place. The bomb was already in Tinian and the plane was already taken off when he signed. So I'm not making excuses for him. I just wonder if he even knew. I think as president, he had some knowledge, but not actually realizing what devastation was going to cause. But Dr. Glenn Pater did research later on, interviewed President Truman and asked about how considerable was it to have known you had killed hundreds of thousands of people and he was shocked by the response because he said that he slept well every night because it ended the travesty of the war. So, you know, he never regretted his move. Well, but the Japanese sued for peace, whatever, that's a strange phrase, but that's the legal phrase. Oh. They sued for peace after the firebombing of Tokyo in May. We're in August. So ending the war, they could have ended the war when the Japanese asked for it. Could we not have ended the war? Earlier? I'm sure. So that reason I'm saying that is that was the plan, we are going to bomb whether, no matter what, okay? Because all to move that bomb, from the mainland on the ship across the island to Tinian, and for anybody that doesn't know where Tinian is, it's one of those little islands next to Guam and Saipan. There's Guam, Saipan, Tinian, and Rhoda. So to move that takes a lot of people, a lot of bombs, a lot of ships and airplanes to do that. So it's not like it was a minute's notice. That's why I wonder if it had already been in place. And it was, I don't know. Yeah. Just looking at the logistics of this thing. Right. So when we go to break, we have a minute, we go to break, and then I want to talk about the sunflower. Oh, yes. Sounds great. This is Think Tech Hawaii, raising public awareness. You're watching Think Tech Hawaii, which streams live on thinktechhoaee.com, uploads to YouTube, and broadcasts on cable OC16 and O'Lello 54. Great content for Hawaii from Think Tech. We're back. And I'm talking with my dear friend, Joanne Tachibana. One of those interesting little moments in our history. We were part of the crowd, part of the, for the film First Battle, which was a long time ago, and I was the old Hawaiian tutu with the straw hat. And Joanne, of course, is the pretty Japanese woman. That was one of those moments. Yes. So now we, let me see. I've got all my sunflower here. Tell us about the history, the reason that we use, we commemorate the sunflower along with the Nagasaki. Thank you. Yes, we've been, it was, SGI Buddhist, the president, Daisaku Ikeda, you know, always talked about anti-nuclear things because his teacher talked about that. And David Krieger is the nuclear foundation president, and they collaborate together and put, choose hope. And when we got this, when I got the book, he talked about what important the sunflowers were. They were very symbolic because sunflowers, at the end of World War II, they scattered sunflower seeds into the earth that was all devastated by nuclear devastation, and because sunflowers detoxed the ground. So it's so amazing. And just saying them, it gives me chicken skin because, and the sunflowers gave hope. And that's why the book was called Choose Hope. So since then, we have used sunflowers as symbols of hope and anti-nuclear war. So that's been, that's why, and we gave today to the council, we gave them sunflower bookmarks to symbolize our work. Oh, this is an open hand. Okay. Can you see this? I don't know. This is me. Is that okay? I can't tell. But anyway, it's helpful. This is for you. It's helpful. Thank you. Oh, beautiful. Yes, thank you. Yes, Choose Hope. Thank you. Yes. Can I just read? Oh, I'm sorry. The sunflower. Quote, sunflowers instead of missiles in the soil would ensure peace for the future generations. U.S. Secretary of Defense, William Perry. Quote, sunflower symbolize a world free of nuclear weapons. After Ukraine gave up its last nuclear warhead, the defense ministers of the United States, Russia, and Ukraine met on a former Ukrainian missile base on June 4th, 1996. They celebrated by scattering sunflower seeds and planting sunflowers, which can remove toxins, including nuclear waste from soil and water. Taking from the book entitled Choose Hope by David Krieger and Dr. Daisaku Ikeda. Thank you. So what we need to do is to buy sunflowers and take them out to Barbara's point where it was so polluted. Is it? Okay. Yes. Where's the sunflowers? Ukraine is so polluted out there. When the military moved out, they left it, didn't take care of it, they just left it polluted. So... Well, that's maybe a project we can take on. That's a project we can take care of. We can plant sunflowers. So let's... We'll make it our project. That's a sunflower project. Maybe the 75th. Yes, yes. Today we talked with the Council General about planting now, it's a 72nd anniversary, so we're planting now for the 75th. So I think this project will have blooming sunflowers. That would be wonderful. Well, that's very hopeful. That's great. Yes. We had this Council General of Japan this morning at the ceremony of the City Council, which would be lovely. And the City Council honored us for all those years of work with the bell and the fact that this is the 72nd anniversary of the bombing. And it's one of those things that if tragic as it is, as horrible as it is, we must, we must keep remembering, we must talk about it. I'm sorry that we can't have music because of the copyright issues. But when I was in Nagasaki for August 9th, everywhere we went, streets were full and you could hear the music, the bells were nagasaki, everywhere. And it just filled the streets just so lovely. So every year when they celebrate, we always have the music, the bells, and nagasaki. But the Royal Hawaiian Band. The Royal Hawaiian Band. Absolutely. So, hello. So we'll plan for that. We'll plan for that. We will plan for that. Yes. Well, we're going to grow sunflowers in the neighborhoods and down there. Oh, that sounds wonderful. I think we're really delighted that we're making plans already. Is he going to leave us? Well, he said that, you know, they give two-year terms, so his two years is coming up, but sometimes they extend it to a third. And when we were talking with Bishop, we thought we could, if he's gone, then we should invite him to come. Come? This is his idea, yes. So he was delighted at that thought. So, yes. Yes. And he's been very involved. The Council General, when he arrived two years ago, it was a few days before our celebration of the Nagasaki Ballet to the Hall. And he came down, and he immediately jumped in. And, you know, he was so delighted about the fact that we remain in Nagasaki because not many places commemorate Nagasaki. It's one of the forgotten celebrations. When, you know, they make all kind of excuses about the cloudy and there was another site and all that kind of nonsense. When we were in Nagasaki, in fact, the Hibakusha invited me first class. They gave me a peace prize over there. Beautiful. While we were there at Ground Zero, and I'm turning around looking at Ground Zero, you know, thrilled at that three there. And in the background, I could see across the river this huge sign that said Misubishi. Wow.  Only about... This was not a second thought. This was planned, because Misubishi was building ships and planes and trucks and everything. That's a Japanese thought. And I thought, oh, okay. I get it. I understand. It is a wonderful city, beautiful city for anybody that doesn't know about tonight, go home and read Madam Butterfly or play the music or go to YouTube because that is where Madam Butterfly takes place. Beautiful woman, Japanese woman falls in love naturally with a sailor. What can I say? He was a lieutenant and his ship was the Abraham Lincoln, can you imagine? And so anyway, you've got to go take YouTube or Netflix or whatever and watch it and you get to see and get a sense of... And that was in 1900. And you're like, well, were they telling us something? That the United States arrives on the Abraham Lincoln and then of course... Now we're not going to spoil it by telling you the ending. Okay. We're not going to tell you the ending. But that is what Nagasaki was mainly known for was the opera, Madam Butterfly. And that's where it came onto the scene and maybe that... Maybe, just maybe, maybe that's so pretty. The music is so lovely that people don't want to think about the bombing. I don't know, I'm making it. Oh, forget it. You talk about bombing of Japan, I know some young people a question that said why didn't we ever bomb Germany when they were doing so many cruel things to the Jewish people? But it always raises a question about American choices of why we did Asia rather than in Europe. Well, the excuse is the bomb wasn't ready. That's the excuse. But now the whole thing is very racist. But our language is racist. When we talk about the war in Europe it's always Hitler, always Hitler, not the German people. It's Hitler. When we talk about the war in the Pacific it's Japanese, the Japanese. You know Yoshie.  So it was all the language. The German prisoners of war could go into the officers' club on base where they were prisoners of war but the black pilots couldn't. So it's all, yes. Right across the floor it was all racist. And so that is the answer. The technical answer is the bomb wasn't ready.  You know, they make excuses for it. So we really don't want to keep repeating itself but that was quite a devastating the choices they made. Well Joanne, it's been a pleasure spending time with you as always. Let's hope we don't have to wait until next year to do this. Oh yes, thank you. Every year, every August 9th. Yes, absolutely, absolutely. Thank you again for spending the time with me. Well it's a pleasure and as always I walk the path of peace because you're one of my mentors and models. Thank you darling. I love you. Bye, see you next week.


Your privacy policy is something that you need to have on your dropshipping stores whether you're dropshipping on Shopify, Wix, WooCommerce or any other host that lets you create your own website. This is a video that you have to watch in order to learn how to create your own privacy policies which is good for your own protection. So even if you have no idea what these things are or if you've heard about it but you're not sure how to go about it in this video I'm going to simplify the whole process for you and provide you with the best templates to use for your stores. Quick intro and let's go. Welcome back and let's get right to it. I know that this is not the most interesting lesson that you can learn for your e-commerce stores but it is a must. You're serious about your business, you don't want to get any wrong lawsuits or anything that you did wrong on your website, you didn't tell the customer exactly what his privacy policy is, what you're doing with the cookies, what you're doing with their privacy information and in this video I'm going to break that whole down for you. So here I'm going to introduce the best privacy policy generators but we're not only going to talk about privacy policies but also the rest of the policy pages that you need in your legal pages on your website. So we're going to go over all of that starting right now. One second before we get started if you haven't done so yet do not forget to subscribe to our YouTube channel to always stay updated and learn about the next step for your e-commerce business. Go to our YouTube channel, subscribe and don't stop learning but also while you're learning don't also forget to take action. One has to come with the other. Now before I start remember that everything that I'm going over in this video you can also learn about it in the blog article which I'll leave a link to right below this video in the description but I always like to throw in extra value into these videos so of course stay tuned especially if you're the type that likes to watch. So privacy generators, why do we even need them? A privacy policy is a legal document that discloses what personal data our websites collect from users from anyone who's viewing our website and how we process that information and what we do with that data, what we do with that information. Even if you have a Shopify store or a Wix store and you're not really doing anything with the customer's information there are still things that are going on in the background from the host, from Shopify or Wix or whoever it may be and you need to know about these things because these things need to be written in your privacy policy pages, in your legal pages and if you go to any website, any brand they all have policy pages whether it's on the header menu on the top or on the footer menu on the bottom. This is something that every website has every business needs to have for their own protection and of course for the reader's protection. So we've got privacy policies and we're also going to throw in shipping policies, return policies, terms of service and frequently asked questions. These are all very important pages for you to have but we're going to start with the most important the privacy policy. So what do we need to include in the privacy policy in our Shopify stores? And when I say Shopify, of course, if you're on Wix, it's also good there. If you're on WooCommerce or any other host that allows you to host your online store and have your own domain name and customize your whole website. I'm not talking about marketplaces like if you're drop shipping on eBay or Facebook Marketplace or Amazon, they all have their privacy policies done for you. But on these websites, where it's fully customizable for you, you have to do it on your own. First, the things that we need to include in our privacy policies, how your website collects personal data, how your website stores the personal data and what your customer's privacy rights are or your online shoppers or the viewers who didn't even purchase anything from your website. All of this information needs to be inside. So what needs to be in there? For example, the name, the username, the phone number, the customer's email address, their shipping address, their credit card details, their billing addresses, what are you going to do with all that information? You need to disclose exactly what you are doing and this will be a part of your privacy policy. Now guys, do not be afraid, we've got ready made templates. Just let me get to it, but you need to understand the importance of it first. So let's keep going.  So those are some of the things that you have to include in your privacy policy. What are our customers privacy rights? Our customers rights is for them to know exactly how we can edit or delete their personal information, how to opt out of cookies and other tracking tools, we need to provide them with that information and contact information for if our store users would want to acquire their privacy rights, you're going to have to be able to send it to them. Now granted, I've been doing this for a while and no customers ever reached out to me and asked me for their privacy rights. But as long as you have it up there, no one is going to ask you for it. Now besides that, we all live in different places around the world. And with that, we all have different rules. So you need to also check locally, what are the institutional laws that you have in your country in regards to your customer's privacy. Now in most cases, you may not learn anything new here since everything will be included, but that's also something that you should know. Now here's how to help you with how to comply with all of the countries around the world. And this is something that you all need to know. Bear with me guys. Once again, I know it's not the most interesting topic, but you have to know this for your own protection. So stay with me and let's continue. The European Union and the United Kingdom both have this thing called the GDPR. That stands for the General Data Protection Regulation. And as long as your privacy policy complies with the GDPR, then you won't have any problems. You won't have any issues as it will be relevant for most countries around the world. And here's the info that we need to provide in our privacy policy to make sure that it is GDPR compliant. The contact details of our Shopify business or wherever we have our selling channel, the contact details of our data protection officers, details, categories of personal information we collect and use. This one is important how we should lawfully process each type of personal information. So what we're doing with the information that we're getting are guarantee when transferring personal data outside the EU outside of Europe or outside the UK and how users can modify and change their personal information like their contact details and so forth. All of this is important to have inside your privacy policy. And of course, I'm soon going to show you how you can generate these really easily for your websites. Now in the United States, there is a federal privacy law called the California Online Privacy Protection Act and also the children's online privacy protection rule. So of course, we need to comply with those things if we are dropshipping to California. California has different laws than most of other states in the United States. There's also some products that you will try to dropship to them. And you'll notice that shipping carriers will not allow that type of product to be imported into California. And what this means is that websites are simply not allowed to collect personal data, personal information from children under the age of 13. So children under that age should not be shopping online and should not be using their parents credit cards in the first place. But we will want to avoid selling dangerous items online so that children will not simply not be able to buy them, you know, take their parents credit cards, purchase that item, and then will be held accountable for selling these products for children under the age of 13. So since we're not allowed to collect data on children under the age of 13, without, of course, their parents consent, and we can't really control the age group who enters our website, just make sure that you're not selling anything dangerous, which you shouldn't be doing in the first place. And that way you'll be able to avoid any trouble coming from children who are shopping online. Now Canada also has a regulation called the Personal Information Protection and Electronics Documents Act. This regulation is very similar to the GDPA that I went over a few minutes ago. You can of course go over it in our blog article. And you can also of course go to Canada's government website and read all about that. But once again, it's very similar to GDPA. So if you are good with the GDPA, you will also be good with Canada. So now that you have a good basic understanding of what the privacy policy is, what should be included in it. Now let's see what are the best privacy policy generators that we can use to quickly whip up a good privacy policy for our website and not have to hire lawyers and spend a lot of money to do that. But you do need to know what it is. You do, you do need to have the basic information, most of which I just passed on to you and continue learning, which is exactly what I'm about to teach. So we've got 10 policy generators. All of these websites can create your policies, your privacy policies for you. But once again, I told you that I'm not only going to be showing privacy policies, I'm also going to show you how to create your return policies, your terms of service, your shipping policies, and your frequently asked questions, because this is all important things to have, not only for your own protection, but also to help you increase your sales conversion rates, get more sales, and have less customers reach out to us and have them simply purchase more since they're already getting the answers that they're looking for from these legal pages. So let's start from the top. The top 10 privacy policy generators. The first is Shopify's privacy policy generator. They have one themselves. The second is Autodesk where we have ready made templates for all of the policies that you need. And that is exactly what I'm going to show you in a couple of minutes. The third is Termly. Fourth is privacy policies. The fifth is privacy policy generator. This is of course the name of the websites that can actually do it for you. The sixth is terms feed. Seventh is get terms. Eighth is UBenda. Ninth is Firebase app. And 10th is shift for shop. Now you can check out all of them once again in the blog article. You can also click on any of them to go straight to that section and read about them. As you see right here, you've got a nice screenshot. You've got a description. You've got their key features and what they do for you. But I'm only going to talk about the top two Shopify's privacy policy generator and Autodesk. Because this is pretty much everything that you need. You only need one of them, but I will show you both. The rest is for you to read and figure out for yourself, decide for yourself, which is the best angle for your store. Shopify's privacy policy generator. Let's click on the link and head over straight to that page. So as you see right here, Shopify today can create a privacy policy for you. Now this isn't as copy and paste as it seems, but it is also very much like that. You're simply going to get a template where you can copy that, create a page on your Shopify store and paste the information there. But there is still information that's going to be unique to your website, which you will have to change. So it's not simply, okay, I got the policy right here, somebody generated for me, copy paste, create that page on my website, put it on the heading or footer menu and that is it. It's not that simple, but it almost is. So let's check it out on Shopify. What you have to do is simply scroll down a bit, click, I'll skip the Shopify trial for now, just create my policy and then enter your company information. Once you fill in all of the info, click send me my privacy policy and they will send it to your email address. Now you can do the same for other policies that you may need. So as you see right here, I'm going to scroll down a little bit more. And here I've also got a refund policy and a terms of service policy. So I'm getting three policies for the price of zero, because it's absolutely free. So here, for example, I can click on get a refund policy and the same as before, I'm going to click on, I'll skip the Shopify trial for now, just create my policy, enter my information, click, send me my return policy and it'll get sent to my email box. But once again, there is information that you will have to fill out inside those policies.  So as you see right here, you've got a link to each and every one of them privacy policy about us frequently asked questions, shipping policy returns and refunds and terms of service. That is six ready made policies and more than what you need to take care of the legal aspects of your website. And of course, cover your own but especially with the privacy policy. But the other policies around here like about us helps the customer connect to who you are, helps them identify with your brand and get to know your story. So that of course is a good thing to have to increase the customer's confidence in your brand in your business in your website. Then you've got the frequent ask questions, which simply saves a whole bunch of questions sent to your inbox from customers who wanted to purchase. But now they have a question that they want to ask first, so they're going to ask it. And hopefully you will answer them quickly in time for them to come back to your website and purchase with frequently asked questions, you can simply nail all these questions and answers down and give the customers the answers that they're looking for before they even have the chance to ask it. And that, of course, increases your sales conversion rates. Next, you've got the shipping policy. Your customers want to know if I purchased from this guy's website, how fast are they going to ship it to me and the returns and refunds after I purchased from their website. And I want to return the product. Can I even do that? And how does that work? These two things are very important to have. Sometimes the buyer may not purchase from your website just because you didn't specify how fast you can ship it out or just because you didn't specify if there are returns, what is the process and how they can get refunds. Many customers are looking for this information before they purchase, and some of them may not even get to the stage where they're going to reach out to you and ask you about that. They're simply not going to purchase. So this is something, of course, that you want to have on your website. Next, you've got the terms of service. Of course, what are the terms of the service? What do I owe you? What do you owe me? How does all that work? That is also something that's already ready for you. So let's take it from the top, the privacy policy. And as you see, I got taken to a page, a privacy policy page. And here you can see all of the information that we need inside our privacy policy. So what comes next? What am I doing with all this information? All you have to do now, take all of this information. Okay, highlight all of it and right click and copy. Now I'm going to head to Shopify. So to my Shopify dashboard under online store, I'm going to click on pages. And here I'm going to create a page for every policy. Now, as you see here, I already have my privacy policy about us and so forth. But let's say you don't have any policies yet. So what you're going to do on the right side is click on add page. And I'm going to call this page, of course, privacy policy and simply paste all that information from the Autodesk website. And as you see, everything got pasted pretty well, all of the spacing, all of the bold, everything looks pretty good. The only thing that you need to do here is fill out the brackets with the right information. And this is where you need to come in. This is where it needs to be unique to every website. So here, this privacy policy describes how insert business name or website address. So in my example, doggy dog club collects uses and discloses your personal information when you visit or make purchases from the site, the site which is doggy dog club. And then you've got the rest of your privacy policy. So just be on the lookout for those brackets and enter in the right information that is suitable for your business. When you're done, you're simply going to click on save, and that page will get created for you. Then you'll see it as a part of the pages on your online store. And then the next step is to go to the navigation menu. And here in the footer menu, you can add those policies, you can add those pages, you can also do it on the main menu, you can put it anywhere you want. But I like to have it on the footer. Some people like to have it on the header. Sometimes you can have some things in the header like your shipping policies, your return policies, things that are very important for people to know. And the privacy policy terms of service and all of that can be on the footer menu. So what you're going to do here on the navigation menu is click on the footer or on the main menu. Okay, and then you can edit that menu. So I can say, okay, well, as you guys can see, I already have all of my privacy and all of my policy pages set up here. But if let's say this is empty, right, the footer menu is empty, I'm going to click on add menu item. And on the name, I'm going to give it a name. So privacy policy, and then link link to what word you want to link this to. So of course, it's under pages and privacy policy. So what I did was I just added it to my menu, I'm just going to click here on add, but I already have it here. So it's just going to create a duplicate. But that is how to add those pages to your footer menu to your header menu, and so forth. Now what you want to do is follow up with the rest of the pages. So you've got your about us, we're going to click on that, copy all of the text, head back to Shopify, online store pages, create a new page, call it about us, paste the information, fill in the brackets, click on save. And that page will get created for you back to the navigation menu. Go to the menu that you want to add it to click on add menu item, give it a name, you're creating a link now, and then link to where so pages about us rinse and repeat until you finish creating all of your pages. Now once you have everything here generated for you, it'll make your job much, much, much easier. Now of course, there are things like I mentioned that you will need to fill out for yourself, especially in the frequently asked questions, ask questions that are relevant to your category, to your niche, to your store, to your brand. And of course, shipping policy, returns and refunds that depends on the suppliers that you're working with. But here you have all of the ready made templates. And this is everything that you need to create wonderful legal pages for your Shopify store for your Wix store, for anywhere else that you're dropshipping that is not a marketplace that already has ready made policies there inside. If you have any questions, comments or suggestions, let me know in the comments section below and I will personally answer them. And do not forget to subscribe to our YouTube channel to always learn about the next step in growing, expanding and multiplying your e-commerce businesses. Thank you for watching and good luck with your privacy policies.


I Can interpret it any way I want Hey Dan into the mute, sorry So that did clear everything up. Sorry about that. I needed to cycle Resources getting contested and Fun stuff like that right so Since I haven't had time to bug folks did everyone already sign up for Scribe No, so If I could get a couple scribes we have a We're gonna kick off our use case Exploration again, and we have a special guest today. Dr. Roy has joined us and I'm right is here to continue some of the discussion that Mark shared with us and As soon as we get Two scribes ascribing we can get started I can be one of them. That's Mark Great. Thank you mark. Okay. I need one more anyone else want to join mark and Think up your notes today. All right. Well in the sake of time. I'm gonna put my name down and join Mark and Allow us to get get started. Um, all right, so Before we You know dive into the use case with dr. Roy I'd like to You know give the opportunity to To have check-ins from any of the SIGs and working groups Anything in SIG off or the policy working group that Anyone has to share so mark, maybe you could introduce dr. Roy and You know connect the dots from the discussion that you Share with us and and what we have today Sure, be glad to do that. Thank you The NIS big data working group has been cranking along since this summer of 2013 this is not a standards body per se the Output is three technical reports of which we've produced one another one is in review at NIS It'll probably come out in the next five or six weeks Maybe before that We haven't got around to publish in our papers, but we're working on that aren't we are not Our knob and I co-chair the security and privacy subgroup of that big data working group and In that role our knob is the primary guy that covers all the crypto aspects of that so while we've worked on the the models together and Basically hammered out the drafts together and helped adjudicate the content we got from other third parties He's really the primary contributor to our backgrounding on blockchain crypto aspects of Data at rest and what the role of some of those things might be and some of the emerging big data Technologies, so he's really the better of the two of us to present those aspects of it He also had some experience previously in the cloud security group Maybe you'll want to mention that our knob when you when you kick that off Over to you buddy Thanks, Mark. Can you hear me? Yeah? Thank you Okay, so I really got scared when you said the use cases because what I'm going to talk about is not as much a use case But an overview of the document that you're going to talk about is that okay? That's great. Yeah for us. We're considering the ingest that we're doing in understanding of You know what's going on in the ecosystems broadly characterizes use cases But yeah, that's fine Right, so but before I dive in this is my first time to this meeting and Thanks for inviting me by the way But can you give me a very short overview of what this working group does so that maybe I can tailor my presentation better You bet. I'll give you our elevator pitch. So You know the safe working group exists You know in the the the cloud native space We are a proposed working group for the that's cncf There are very few of those so there's you know infrastructure and see I And you know a couple other serverless That in the actual cncf and the you know cloud native You know overarching ecosystem there are very few of these working groups if you go down like into Kubernetes there You know is a extensive ecosystem of SIGs and special industries groups and and working groups that are operating there and You know what we're focused on in the safe working group is you know safety in You know this this cloud ecosystem where you have the operator the administrator you know the developer the end-user and We're trying to You know build understanding and and shared vocabulary around how we you know Make sure that there's secure access and you know operational safety in place that all of those parties in this new cloud ecosystem That everyone has a clear sense of what's going on there I see thanks then for that overview and it seems like I'll be preaching to the choir so you know much of what much of what I would say my team in a juvenile to you and and You know as as as you talked about your group It seems like many of the metaphors that we use in the big data working group might just carry over to Your group and we would like like to hear Maybe now maybe later You know how these things are that we talk about in our documents are relevant to you guys So I would like to share a presentation on the screen Let me try to Big green button that says share screen at the bottom here screen. Okay. Okay. Can you see this? Good Okay, so what I'm going to talk about is the security and privacy of big data It's a missed perspective. That is the perspective of the documents that we produced in our working group And Mark has contributed a lot to this document So we start off with We started off this working group with a lot of discussion on what is big data? So this was back in 2013 and You know, they were very diverse opinions on what constitutes big data. I'm sure the answer is Not canonicalized even now But this is the definition we came up with in our document. It may not be perfect, but it was a consensus So it goes like big data consists of extensive data sets in the characteristics of volume variety velocity and our variability That require a scalable architecture for efficient storage manipulation and analysis and this definition is there in Part one of our documents Of course security and privacy are important for big data. You all know that so I don't have to go through the slide essentially it says that it's very important because It causes damage to company reputation when it's debris and that can be evaluated in dollars So the big data working group started out with five subgroups definitions and taxonomies use use cases and requirements security and privacy reference architecture standard throat map The subgroups have kind of spread out From 2013 to now. So we may have more deliverables than subgroup and this one the definitions are a bit nebulous but the deliverables are what you see on the right one through seven and Number four is the big data security and privacy document, which I'm going to talk about So we released our version one three years ago and the NIST SP 1500-4 is our document and It's available on this site that I gave a long link to in the slide Version two draft as Mark said is it's a NIST review phase public comments were received in September 21st and The public comments version is also available on the web. So given that background I'll go into some of the characteristics that we identify in the document that are Seemingly different for big data compared to what was before So we spent a lot of time understanding, you know, what is emergent about the security and privacy of big data given it principal characteristics So it seemed that there were two aspects one is due to scaling and This you can attribute to the volume and velocity characteristics of big data and it has to do with Many things that I'll I'll cover those in the next slide The other more foundational aspect is mixing and this is the notion that One of the characteristics of a very important characteristics of big data is that you get data from diverse endpoints and a huge amount of data and some of that data May not be completely accurate itself. So you get this mixing characteristics Which can be attributed loosely to the variety and veracity characteristics of big data and that causes emergent problems for security and privacy So to go into some amount of detail. So on the left is Water different due to scaling on the right water different due to mixing. So the scaling can be scaling problem can be summarized as you know, how do you retarget your existing systems due to the infrastructural shift because of big data so the infrastructural shift is due to various things like distributed computing platforms like Hadoop Non-relational data stores, etc. So paradigm shift in infrastructural thinking has required Is still requiring new solutions of security and privacy the other is a more foundational aspect the mixing aspect and Here the problem is to control the visibility of data while enabling utility So what is this about? So here the principal questions are, you know, how do you balance privacy and utility? So you get a lot of data but and to be useful all that data needs to be used but then you also run into these privacy aspects where you combine different sorts of data about different individuals and you Get a bigger picture that may not be quite apparent from individual data sets alone How do you enable analytics and governance on encrypted data and then finally how do you reconcile? Authentication and anonymity which on the face of it seems to be a conflict So these aspects are all described in section two of our documents We then go into some amount of depth regarding how do you characterize different? Different security and privacy Aspects that arise due to these principal aspects of big data. So There are five V words that were identified volume velocity variety veracity volatility and What I give in this flat This slide on the next one are examples of security and privacy Concerns that arise due to especially due to each of these characteristics So for example the variety characteristics of big data is Is Is apparent where you know traditional encryption schemes which render Data into Into a random collection of bits that hinders organization of data based on semantics Then volume of big data Requires that you store them in multi-tier data storages so that is a lot of back and forth of data between different storages and All of this communication requires threat models To identify, you know, is the communication secure or not? Is the data being handled properly or not? So these are complex and evolving issues and Then the velocity aspect is that is the retargeting that I talked about So data is coming at a very fast pace How do you retarget traditional security mechanisms to support this? so veracity has to do with the provenance as Mark talked about last time. So this is keeping track and ensuring integrity of the ownership source than other method of individual data And how do you take care of that given the complex movement of data between nodes entities and geographical boundaries? Volatility of data is another big aspect So indefinitely persistent data requires evolving S&P considerations because the ownership may change Merges and acquisitions and so on like who takes ownership and responsibility of keeping the data safe So this is These were characteristics of big data Enforcing new requirements in security and privacy We then in section four Try to classify security and privacy topics. We have two kinds of classification one is cross domain and cross infrastructure and Trying to look at the type of property That each S&P requirement is so some properties of privacy properties you want to keep data secret or safe confidential Provenance properties you want to keep the data accurate You want to identify who owns the data and so on System health has to do with are there security vulnerabilities in the infrastructure itself can somebody exploit that how do you keep the health of the system safe? And then some of these have to do with public policy aspect. So these are things like, you know, what is right? And what is wrong to do with data? From a policy point of view and then their Operational classification of S&P topics. So this has to do with the particular infrastructure that we have in place today So there are devices There are identities and you have to manage access to them You have to go on the use and access of data You have to manage infrastructure and also you have to You know risk analyze an account for each of these aspects Are there any questions so far? Sorry. I just went on No, this is really good Thanks, man. Okay, so So we covered How the characteristics of big data Define new emergent S&P consideration and We classified S&P concerns for different types of systems a centerpiece of our working group is a is a reference architecture and That becomes especially important for security and privacy The reason is security and privacy does not compose What do I mean? So let's say we have two systems system a and system B and We have completely analyzed them So we have we have seen what the end points of system a are what then points of system B are They have data inflows and outflows We have complete accountability for each of them and We have let's say we have guaranteed that, you know, it they they satisfy some security requirements right, but When we put system a and system B together Then suddenly it may turn out that security properties are no longer satisfied And that's because there may be a PI's and system B which leaked data from system a So they made together they may have unknown Dataflow patterns that Were not analyzed when they were in isolation so combined systems can have an unexpected data flow They can destructively interfere So it's very important the point of this is it's very important to think of S&P from an architectural standpoint like think of the system as a whole rather than modular in parts It's also important to look at each module Individually, but then when combining we have to ensure additional property. So there is a need for architectural thinking and That's where it becomes important that we refer to this big data reference architecture so mark might have already talked about this but This is also described in one of the documents in our working group. I think number six And it and it conceptualizes big data systems as these boxes We have data providers and data consumers There is an application provider which sits in the middle of that and it provides different collection and access Access capabilities the framework provider is the underlying infrastructure which which Gives processing and platforms and the structure and there is a system or Orchestrator at the top who is orchestrating all this movement And you can see that there is a security and privacy Fabric all around the system. So what does that mean when to signify it signifies that? this fabric is all around the system and you cannot think of it in isolation so We have to think of security and privacy at each of the interfaces Between the boxes as well as internally to the box. That's what we at least preliminary Did in the version of one of our document in section five of the document you can find some of the security aspect That we talked about like for example in the interface between data provider and application provider You have to do endpoint input validation On the other end from going from big data application provider to data consumer There's some sorts of privacy preserving data analytics and dissemination in the framework provider you have need for key management securing data storage and transaction laws and so on and In section three of our document we also talk about a bunch of That's right. I have a question on architecture before you move on to the next section So it's a bit of a meta question my apologies So when when you were saying reference architecture did you the group there Go and actual actually, you know build this out or you know this to you know laid out some of the architectural definition of What a typical system Is it looks like? So a combination of both so this this was a lot of discussions actually it consumed a year and a half. I would say So we started with a lot of existing architectures Like there was an architecture from IBM there was an architecture from other places We actually have a document in our working group that goes through each of these proprietary or public architecture and then the group shifted through those architectures So what were the principal characteristics that we were looking for and this is the architecture that Evolved out of all the So it took a lot of time to evolve, right? Yeah, it had been evolving even till like last year So I don't think in a we haven't have changed it in a in the last year, but That's what the amount of evolution that it went through Got it. And so what did you end up doing in terms of the the technical code part of this? Yeah, what? I did not get your question. Sorry. So the the the code component What what what purpose does that end up serving for your group? The reference architecture itself So we try to describe everything with respect to the reference architecture even in the security and privacy Document so we try to identify how each of our concepts each of our Classifications each of the technologies that we identify how do they fit into the reference architectures? So that's why it it constitutes a linkage piece an arbitration point where Which defines how we go through the document great the reason why I'm asking is this is an area where? you know we sort of cut it back away from going down this path just because you know taking and You know coalescing all those things across the cloud ecosystem you know seen daunting and You know possibly impractical So good good context that you know, yeah, it does take an incredible amount of time to go and capture and distill that down Yeah, I understand your point so cloud security lands had this huge reference architecture with like 300 boxes right so but What we opted for? Well, one of the reasons is big data systems are so diverse It's not as homogenous an entity as a cloud, right? So when we describe big data systems, you know big data systems are everywhere you have health care you have a fundamental physics You have aviation you have transportation you have so many use cases and each of those use cases Can identify at least something that you know may not fit readily into this architecture, but It it is actually one of the reasons why our reference architecture is so succinct Instead of going into You know, 300 little pieces of details, right, right Since because it has to homogenize and inherently in homogenous Collection of use cases, right? Great. Thank you for sharing. Sure Okay, so we collected all these use cases many of these are actually from mark and you might have talked about some of you But overall They were they were like five big buckets retail marketing health care cyber security government and industry of big data So with that I would like to dive into some of the cryptographic aspects that we talked about Document so these are emerging cryptographic technologies and the recommendation from This document is to be aware of these technologies and to be aware of risk-benefit Analysis of you know choosing some of these technologies over others So this table is divided into various facets, so I talk about specific Cryptographic technologies on the left These are emergent Some of these are in limited deployment, but most of it is in is in research states and all of these technologies provide different kinds of features while Affording visibility to controlled entities. So what do I mean by that? The first example is how do you outsource computation securely? So an example is suppose you want to send all your sensitive data to the cloud photos medical records and so on You can send everything encrypted, but the cloud can't help you much after that So you can't Find out for example how much you spent on movies last month if everything you sent to the cloud was encrypted with your own So fully homomorphic encryption is a crypto technology Which enables you to do just that so you encrypt your data and then the cloud can do Analogous computation called homomorphic computation, which is which is a transformation of the actual computation and then The the the amazing thing about this is that it only operates on Piper text It never has to decrypt the data So all Piper text all process type attacks are all random sequence of bits to the cloud And then the cloud can send you your processed encrypted data and only you can decrypt it So this is great because you know the only can only The user can decrypt the process data. There is an end-to-end security So you you get to pick your key and so on We can also control visibility like who we give access to based on encryption technology so this is traditionally done by role-based access control or Some other types of access control by systems like operating systems So these usually restrict access to data, but the data is still in plain text So in particular if you hack the system you get access to the data and When you want to send the data in transit then the security is kind of ad hoc depends on system to system So now the question we ask is can we encrypt it in such a way that we do not have to go through all this So decryption is only possible by entities allowed by the policy So this is kind of you know technologically enforced rather than system enforced Well, of course you can hack keys, but This is a much smaller attack. So Q a key can be a few kilobytes and you can have Very special protective mechanism to protect small keys rather than you know gigabytes of data And then encrypted data can be moved around as well as kept at rest the handling is uniform so So many of you might already know examples of this so The starting point is public key encryption so How public key encryption works is that there is a certificate authority It signs for certificates of public key and then You know, you can show Let's say Alice and Bob are trying to communicate Then Bob can show his science certificate of public key then Alice can Use that public key to encrypt data And only Bob can decrypt it. So this is just a plain public key encryption Going one level higher. There's something called identity based encryption So here the idea is that there is no science certificate of public key You can just use the identity Of some person And there is a master public key just one master public key And you just use that master public key and the identity of the person you want to encrypt to And that's all you need to encrypt your data. Any other person cannot With the even using the same master public key cannot decrypt your data So in this scenario Alice can use The master public key and just the identity like maybe email address of Bob or George To encrypt the data and only Bob or George can decrypt their respective side of it So taking this to the extreme we have policy based encryption So here the policy can be a complex predicate. So which is indicated as pie here so This is one simple scenario where there is a There is a hospital and let's say somebody can see a patient's data only if he or she is a doctor or a nurse who also works in ICU So it this is a more complex policy predicate than just identification So what policy based encryption does is It enables an encryptor to encrypt to a policy Rather than some identity. So you can encrypt to a policy of your choice. It can be complex and then Only people who satisfy that policy will be able to decrypt And nobody else Finally, we also talk about blockchain So we avoid the financial aspects of blockchain in this document So we we don't know how how important that is But there are many technological aspects of blockchain which can be very useful in the security and privacy space especially things like asset and ownership management transaction logging for audit and transparency bidding for auctions and contract management and so on So the high level recommendations are as follows. So which technology to use among all these cryptographic technologies is It involves a lot of risk benefit analysis We have to consider sensitivity of the data cost of rates and cost of security security systems When doing this analysis, so I give an example where You know, there are three different cost benefit analysis So let's say we want to run the task of Running software on encrypted data at rest There are three possibilities So let's say we just do What is traditionally done which is decrypt the data in the cloud And run software so you your data is encrypted at rest But you can decrypt it and then just run plain software So what are the pros of that a very very fast execution? Problem is if the server is hacked decryption keys leaked all the data is exposed The second better option is Run the software on the decrypt the data inside a hardware security module So there are many hardware security modules In the market today prominent ones are like in the last years or just arms on So this is a little less fast than Then just doing computation on plain data But it's still practical But there are some problems. We have not been solved at this actually yet And these are to do with side channel attacks And these attacks are kind of, you know, you can You can see the patterns of memory addresses and so on And you can infer something about something secret The final Completely secure solution is, you know, you just use fully homomorphic encryption The pros there is it's cryptographically secure. There are no side channel attacks It's secure against all the vulnerabilities of the last solution It works even if you completely breach the server But the disadvantage is that it's very slow at this point except for limited operation But so just to conclude, you know, there are four things that I want to Take you away Think of security and privacy at the time of architecting the overall system Not as an afterthought which is Which is Which is the way many systems are designed today, unfortunately In security and privacy Systems do not compose. So you have to reanalyze security and privacy When you add new features or join new systems There's a lot of cryptography that is emergent You just have to stay tuned and patient at this point But it will enable many remarkable operations in the future And finally, it's very important to read the document And we hope that you have feedback for us that's useful Um, we should be able to document that. Thank you Great. Thank you, dr. Roy So I'd like to open the floor to any questions You know a request, uh, either to yourself dr. Roy or mark Um, it'd be fantastic if in The meeting notes we could link to not only dr. Roy's presentation But if we could, you know, provide links to The documents, I believe, uh, you know mark you touch on some of these in the Issues in our github repo But you know for those that are, uh, you know Following along, uh, if we can point them to A way to go deeper in this that'd be fantastic Yeah, I have a question about Combination of The way that changes The access control, right? We we see both that you can By combination you can deanonymize data. So data that was previously anonymized and that maybe doesn't need strong access control Suddenly by combining that You you you have the need for stronger access control and also the the reverse Where you have data that gets aggregated. So the the access control doesn't have to be as secure, right? Was there any thought on that in your Right. So we test on this in the variety aspect Of big data Requiring new thoughts on architect and secure systems and you bring up a very good point where architectural thinking is very very necessary Not only at the level of a single organization, but as a whole Of you know, what is going on? throughout the internet because As you said, you can aggregate data from various endpoints And suddenly you have a much clearer picture of Of sensitive data than before so It's unclear at this point like how you can So, you know technologies like differential privacy They have a privacy budget which is that You always leak some amount of information even if you aggregate and If you do that too many times Then the privacy budget is lost, which means that Over time you get clearer and clearer more and more accurate Picture of the sensitive data So this is kind of inevitable. So Other than like completely restricting access to the data It is not clear how to stop this leak of information Where does anonymity So, you know in order to guarantee Some degree of privacy, you know, we Tend to lean towards systems that You know identify the the players You mentioned anonymity at some point, you know, how are you dealing with anonymity and trying to solve Are you always trying to solve for anonymity? So for the next For our document, we just, you know, describe what the problem is It's not a solution document, but in the research community There are technical aspects too. So I talked about, you know, how do you reconcile Authentication and anonymity Right, so that is a technical question that the research community has been looking at so There's there are primitives called group signatures. For example, what does group signature mean? It means that You have a group of people And anybody can sign a method, but you won't know who signed it So you can still authenticate that person But you will not know beyond the group structure Who that person is or entity is So you could say, you know, give them the same signing key, right But that is not desirable because later on there might be an arbitration process where Where you want some amount of non-repudiation you want to call that person responsible If a legal case comes up, for example So So that's why this this kind of Primitive is far more sophisticated than just giving out the same signature keys to everybody so This system in fact allocates a trusted arbiter Who has some more information so that he can look at the signature and identify who signed it But without going through this arbiter, nobody can find out who signed So that is one of the technologies that addresses Reconciling authentication and anonymity And you can think of it as In an iot context as well Like there are different iot devices. You don't want to specifically pinpoint which device it came from. Maybe that's very personal But if there is a glass breaking scenario you want to know Mm-hmm. Yeah, the concept of uh, you know trusted arbiter. I think will Uh come in handy, you know as as we model things out. Yeah Yeah, one of the approaches that uh It came up and as Arnav said, we don't really get very prescriptive but We talk about trying to treat pii and what pii is Uh varies depending on the domain, you know, it could be a floating point number depending on the scenario, right? but If you have a domain that you can consult to understand the meaning of the thing You might want to tag that data throughout a system and that includes when you federate the data so the the persistence of Some people call this metadata, but really, you know, just carrying other data along with it in some kind of structured framework so that you can Do traceability and provenance so you can understand when it's been violated So that's kind of the fundamental principle and doing PCI compliance or Being HIPAA compliant, which is you know, something most of the big companies were in Have to do on a regular basis But the problem is there for everybody really because If you think of pii is just an instance of Really really important data in some domain Then that's a that's an issue we all face at some level So from a security point of view, you want to know that those That you can expose Where that data has been used if you need to and who's touched it and To authenticate the people who've done the touching and that includes Machines and that's why uh, I don't know if you were there Dan when you were trying to get booted up Um, I was touching on this issue of authenticating these low-cost smart home devices No It's an interesting use case and stop me if I already mentioned it to this group But uh anybody on this call we have them at home already I've been Alexa Like smart uh the smart switches tie do it. Yeah So the smart switches are mostly uh going to cloud services overseas Written by who knows who in fact In fact the error messages that come back are are in chinese Usually you see the chinese stuff at the top and then So this is an interesting problem. We have a cloud service from amazon doing the driving A local iot device i.e. Alexa on your home network probably on a single segment Uh collecting data for amazon But going out to these other cloud services to direct traffic out to these devices and If you like blow this into a neighborhood or utility scenario It's an interesting problem, which kind of is part of the rationale why we Uh, we're we're glad in retrospect that we stayed away from the More expansive cloud specific model because this is more realistic. I think this multiple be multiple cloud multiple entity multiple developer communities even so It's more of a I guess a case study than a use case, but It it certainly is a realistic one at least in my house Absolutely and you can drop you know drop a uh, you know 3g chip in there and you know easily backchannel some other, uh, you know data data source Good. Well, uh, let's keep on topic.  We've got five minutes here, uh to to wrap up Um, you know any other questions for for dr. Roy? All right, so thank you dr. Roy for for sharing that this has been insightful um, look forward to uh integrating and capturing these in um in our our notes and Uh, you know mark. I I I added uh, you know to my uh rolling agenda A check-in uh from the the NIST big data working group You know if there's nothing to report, uh, you know, uh, please You know just feel free to ignore but uh, you know would love To have you share at the beginning of our meetings Anything that the any contacts or any information that that uh, this group would would find relevant I really appreciate the the perspectives that you're bringing Sure that uh, just uh, let me do that since you invited me and I'll make it short in in light of our time. We I introduced uh, this was me dominating the last conversation we had In that group we were trying to understand how to uh, do traceability for ethical requirements that are put out in organizations and It's a big data problem because often these things are authored by um People outside the organization So or inside it who who the developers are not connected to so to some extent it's a traceability challenge it's also a problem of Where do the natural language artifacts belong? And and what do you do with them in in the architecture of the systems you're building? So Whether it's a cloud native, uh issue. It's certainly one that We're wrestling with and if you think about, um Some of the uses for algorithms that are being Contemplated or have already been deployed sooner or later. We're all going to be in the position of having to explain algorithms and Why they are recommending one thing or another to To users and so we're trying to figure out what the implications of all that are and if we can make any contributions Nice Yeah, it's a that's a big area that I'm happy to Hear you're trying to get out in front of uh, because uh, not a lot of folks are getting out in front of that and that's barreling forward I'm afraid I'm going to be in the position of that poor Volkswagen engineer who ended up getting blamed for it All right, right exactly Yeah, that's the um, you know, that's a great perspective of of how this that ends up playing out and uh, You know the individuals that that get the real hit, uh for for, you know, bigger decisions like that Um, so, you know coming up. I've got uh, Jerry, uh, who unfortunately couldn't join the states. She had a sick kid to take care um, is going to be joining us uh for an overview uh of Uh, you know some of the the security infrastructure that uh, you know, she's been working on at cyber arc that, uh, you know overlaps the The kubernetes and cloud foundry Deployments of cloud native infrastructure. Uh, so looking forward to that. Uh, I think uh next week we'll have adp lined up and then june 1st I am cancelling the meeting. I'm going to be on the road and um In berlin, uh, so uh, you know a couple weeks. We'll give you a uh, friday off to Uh, enjoy friday things All right. Thanks everybody. Thanks for joining us. Uh, see you next week You love everybody. Thank you. Bye. Thank you


My name is Chad. I'm a student at a university in New York. I just moved to a studio apartment and needed some furniture. I found a guy on Craigslist that wanted to desperately get rid of his things at super cheap prices, so I went to check it out. He sold things in bulk to get rid of as much things as possible.  Some of it I gave away and some I kept. An old wooden box caught my attention. It was locked and out of curiosity. I kept it. I had to force open the lid with a screwdriver, and inside, I found some old pictures. The word, bitter root, was handwritten on the backs of all of them. There was also a tin can that contained a reel of film that I later learned from my friend Dario, a film student, was 8mm film. The film was pretty damaged so I just kept it on my bookshelf as decoration, but I couldn't get the images of the pictures out of my head. I had to figure out a way to watch that film. With help from Dario, we got an old 8mm projector in good working condition on E-Day. The films kept in several spots so we put it together with a special tape and then watched it. The first 6 seconds of the film didn't have any footage, it was just a white screen. That didn't really catch my attention considering that this was filmed a long time ago. Then the next clip was footage of what looked like the woods. Everything seemed normal at first, like if someone was just filming around to test the camera. It was like this for about 45 seconds, until the next clip which was still footage in the woods. There was what looked like an old mini castle. It then twitched to the next clip of what looked like a man wearing a long cloak walking towards the building. It was filmed from far away like if the film were wasp eyeing on the man. The film were later managed to get inside the building. The first 30 seconds of the film was just stirring inside the building and then again showing the next clip of the man in a room. Although, it was in the ordinary room. The room was very dirty, and then the man was sitting on a chair at the table in the bowl. He was stirring it, like a witch stirring a cauldron. In the ground next to him was a bag that was about 5-6 feet long. The man was poking it with a long stick. The scariest part of this was that the bag was moving. Moving like if there was a body inside. The next clip was footage of touring around, but not around the house instead, around the room. The man was calm at this point, but the things that I saw on the footage that were in the room made me choke on vomit. There was what looked a lot like old rotting bodies that you could see in these glass little boxes or chambers. The clip changed and went back to the woods again and showed the man walking in a far distance. The film were was slowly walking towards the man. The clip changed again, but the scenery didn't. Like it was another shot.  He then tossed the bag in the little ravine and slowly walked away. After the man was gone, the filmer walked slowly towards the ravine and saw the bag. It actually was in the bag. It was an object wrapped in a piece of cloth. The filmer picked up the cloth and unfolded it to reveal the object inside of it. What we found on the clip was disturbing. The object was what looked like a very misshaped head that lost horribly battered and beaten. After seeing this, the next clip showed the filmer running away as fast as they could. And then the film ended. Me and Dario had shivers crawling up and down our spines and I vomited in my mouth.  We contacted Chris, the guy who sold the stuff to us, about what he had sold us. But we didn't get any response back. This footage will be a mystery to me until I get an explanation.